lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20130804013658.GD19781@thunk.org> Date: Sat, 3 Aug 2013 21:36:58 -0400 From: Theodore Ts'o <tytso@....edu> To: Piotr Sarna <p.sarna@...tner.samsung.com> Cc: adilger.kernel@...ger.ca, linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org, b.zolnierkie@...sung.com, Kyungmin Park <kyungmin.park@...sung.com> Subject: Re: [PATCH 1/2] ext4: fix handling of nodelalloc parameter On Fri, Aug 02, 2013 at 02:03:46PM +0200, Piotr Sarna wrote: > Commit 26092bf ("ext4: use a table-driven handler for mount options") > introduced buggy handling of nodelalloc parameter in mount command. > > After explicitly using delalloc or nodelalloc parameter in mount command, > MOPT_EXPLICIT flag is set. After that, a test ensures that "data=journal" > and "delalloc" parameters are not simultaneously activated. > Unluckily, the mentioned test reports a bug in both situations: > - "data=journal,delalloc" > - "data=journal,nodelalloc" > whereas the second one is perfectly legal and acceptable. > > A simple solution to this problem is in setting EXPLICIT_DELALLOC flag > properly. This patch ensures that EXPLICIT_DELALLOC flag is set only > if "delalloc" parameter was used, and not set in case of "nodelalloc". Thanks for this bug report and patch. There is an even simpler way of fixing this doesn't involve adding an additional check in the code, though. Just make the following change the table entry: {Opt_nodelalloc, EXT4_MOUNT_DELALLOC, - MOPT_EXT4_ONLY | MOPT_CLEAR | MOPT_EXPLICIT}, + MOPT_EXT4_ONLY | MOPT_CLEAR}, I'll send out a patch which does this... - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists