Re: [PATCH] fix: print ext4 mountopt data_err=abort correctly

2016-03-12 Thread Theodore Ts'o
On Wed, Mar 09, 2016 at 07:30:40PM +0100, Ales Novak wrote: > If data_err=abort option is specified for an ext3/ext4 mount, > /proc/mounts does show it as "(null)". This is caused by token2str() > returning NULL for Opt_data_err_abort (due to its pattern containing > '='). > > This is perhaps more

[PATCH] fix: print ext4 mountopt data_err=abort correctly

2016-03-09 Thread Ales Novak
If data_err=abort option is specified for an ext3/ext4 mount, /proc/mounts does show it as "(null)". This is caused by token2str() returning NULL for Opt_data_err_abort (due to its pattern containing '='). This is perhaps more logical solution than the previously submitted, handling these 'data_er

[PATCH] fix: print ext4 mountopt data_err=abort correctly

2016-03-09 Thread Ales Novak
If data_err=abort option is specified for an ext3/ext4 mount, /proc/mounts does show it as "(null)". This is caused by token2str() returning NULL for Opt_data_err_abort (due to its pattern containing '='). This could be solved by many ways, this one is the conservative and former ext3 way resembli