On Thu 10-04-14 10:22:54, Matthew Wilcox wrote:
> On Wed, Apr 09, 2014 at 11:52:54AM +0200, Jan Kara wrote:
> > > - if ((sbi->s_mount_opt ^ old_mount_opt) & EXT2_MOUNT_XIP) {
> > > + if ((sbi->s_mount_opt ^ old_opts.s_mount_opt) & EXT2_MOUNT_XIP) {
> > > ext2_msg(sb, KERN_WARNING, "warning: refusing change of "
> > > "xip flag with busy inodes while remounting");
> > > - sbi->s_mount_opt &= ~EXT2_MOUNT_XIP;
> > > - sbi->s_mount_opt |= old_mount_opt & EXT2_MOUNT_XIP;
> > > + sbi->s_mount_opt ^= EXT2_MOUNT_XIP;
> > Although this is correct, it was easier to see that the previous code is
> > correct so I'd prefer if you kept it that way.
>
> Depends how you think about it. I think of foo ^= bar as 'toggle the
> bar bit in foo'. So I read the code as 'If the mount bit is incorrect,
> print an error and toggle the bit'. I think you're reading the old code
> as 'If the new mount bit differs from the old mount bit, make sure the
> new mount bit is the same as the old mount bit'.
Yeah, since it's pretty obvious what the code should do, one can figure
out it is correct relatively quickly. But it's something that wasn't
obvious to me at the first sight. If you really prefer your way, I can live
with that...
Honza
--
Jan Kara <jack@xxxxxxx>
SUSE Labs, CR
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>