Bug 25347 - Isodumper fail to flush before verify and telling all is done.
Summary: Isodumper fail to flush before verify and telling all is done.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-23 19:11 CEST by Morgan Leijström
Modified: 2020-02-04 12:14 CET (History)
3 users (show)

See Also:
Source RPM: isodumper-1.15
CVE:
Status comment:


Attachments

Description Morgan Leijström 2019-08-23 19:11:40 CEST
Isodumper do not currently make sure write buffers are flushed before saying it is finished.  So user may pull it out before it is written (despite having been "verified" ?!

Suggestion, tip from tmb: "eject" informs the kernel that the device should be dismounted, and then the kernel flushes out the block-level writes before dismounting it. 

So before telling user it is done, issue "eject /dev/sdx" (change x)

Additionally, verifying the write can of course only be reliable after this flushing, so stick should be "ejected", then verified.

Here some trick is needed:  After ejecting the stick fdisk -l do not list it and trying to write using dd to it i get error No medium found.

(Sidenote: Launching isodumper at that moment it list the stick anyway)

So somehow /dev/sdx need be "unejected" however that is done.
Marja Van Waes 2019-08-24 22:00:25 CEST

CC: (none) => marja11, yves.brungard_mageia
Assignee: bugsquad => mageiatools

Comment 1 Thomas Backlund 2020-02-04 12:14:32 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0043.html

CC: (none) => tmb
Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.