Bug#654206: max_batch_time not honoured or incorrect in /proc/mounts

[Jonathan Nieder <jrnieder@gmail.com>]

reassign 670593 src:linux-2.6 3.2.15-1
reassign 654206 src:linux-2.6 2.6.32-39
found 654206 linux-2.6/3.1.6-1 , linux-2.6/3.0.0-6
merge 654206 670593
tags 654206 + patch upstream
fixed 654206 linux-2.6/3.3~rc6-1~experimental.1
quit

Hi Joshua,

Joshua Charles Campbell wrote:

> This happens on both 3.2 from backports and 3.2 in wheezy, tested on both.
> Might happen in earlier kernels too.
>
> umount /test; mount -o max_batch_time=14000 /test; grep test /proc/mounts
> produces:
> /dev/mapper/test /test ext4 rw,noatime,user_xattr,acl,commit=600,max_batch_time=0,barrier=0,journal_async_commit,stripe=768,data=writeback

Yep, min_batch_time is being reported as max_batch_time for some
reason.  Fixed by v3.3-rc1~114^2^2~5 (ext4: Report max_batch_time
option correctly, 2012-01-04).

Thanks for a clear report,
Jonathan