https://bugzilla.novell.com/show_bug.cgi?id=809737 https://bugzilla.novell.com/show_bug.cgi?id=809737#c1 --- Comment #1 from Jeff Mahoney 2013-03-15 16:59:21 EDT --- Created an attachment (id=530023) --> (http://bugzilla.novell.com/attachment.cgi?id=530023) [PATCH] loopdev: sync capacity after setting it The kernel loop driver will set the gendisk capacity of the device at LOOP_SET_STATUS64 but won't sync it to the block device until one of two conditions are met: All open file descriptors referring to the device are closed (and it will sync when re-opened) or if the LOOP_SET_CAPACITY ioctl is called to sync it. Since mount opens the device and passes it directly to the mount syscall after LOOP_SET_STATUS64 without closing and reopening it, the sizelimit argument is effectively ignroed. The capacity needs to be synced immediately for it to work as expected. This patch adds the LOOP_SET_CAPACITY call to loopctx_setup_device since the device isn't yet released to the user, so it's safe to sync the capacity immediately. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809737 https://bugzilla.novell.com/show_bug.cgi?id=809737#c3 --- Comment #3 from Jeff Mahoney 2013-03-15 17:33:37 EDT --- Incidentally, this has been fixed in the kernel in 3.9-rc1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809737 https://bugzilla.novell.com/show_bug.cgi?id=809737#c5 --- Comment #5 from Jeff Mahoney 2013-03-17 10:24:53 EDT --- This patch assumes the ioctl will be there but it was introduced in 2.6.30. I'll attach the new patch once I update it on the ML. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809737 https://bugzilla.novell.com/show_bug.cgi?id=809737#c Petr Uzel changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809737 https://bugzilla.novell.com/show_bug.cgi?id=809737#c8 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|jeffm@suse.com | --- Comment #8 from Jeff Mahoney 2013-03-25 11:25:14 EDT --- For older releases, yes. The kernel patches don't eliminate the original issue. They only eliminate the deadlock that will occur with the fix applied. We don't need the patch for 12.4, but we'll probably get it anyway when util-linux is updated. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=809737 https://bugzilla.novell.com/show_bug.cgi?id=809737#c10 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|jeffm@suse.com | --- Comment #10 from Jeff Mahoney 2013-03-27 16:46:55 EDT --- Created an attachment (id=532240) --> (http://bugzilla.novell.com/attachment.cgi?id=532240) [PATCH v2] loopdev: sync capacity after setting it Yes, I posted this to the util-linux mailing list a few minutes ago. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.