On Fri, 2018-03-02 at 11:29 -0500, Theodore Ts'o wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > On Fri, Mar 02, 2018 at 11:14:13AM -0500, Theodore Ts'o wrote: > > On Fri, Mar 02, 2018 at 03:20:22PM +0000, Joakim Tjernlund wrote: > > > > > > But I don't hav ext3, only ext4 in kernel: > > > # CONFIG_EXT2_FS is not set > > > # CONFIG_EXT3_FS is not set > > > CONFIG_EXT4_FS=y > > > > What version of the kernel are you using? The ext3 file system has > > been removed from the upstream kernel for quite some time, so this > > must be a kernel missing lots of security bug fixes. (E.g., an > > obsolete distribution kernel? :-) > > Never mind, the "CONFIG_EXT3_FS is not set" confused me. We still > have this for backwards compatibility with old kernel configs. > > So I'm not seeing this behavior at all. I created an ext4 file system > on /dev/cwcc/scratch, and then ran: > > # mount -t auto /dev/cwcc/scratch /mnt Seems like it only hits when mounting from fstab, I have LABEL=BOOT /boot auto noatime 1 2 Anyhow, Eric's patch solved the problem. Jocke
