All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Daniel Gomez <da.gomez@samsung.com>
Cc: Zorro Lang <zlang@redhat.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"fstests@vger.kernel.org" <fstests@vger.kernel.org>,
	"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [Bug report]: fstests g/388 crash on ext4, BUG: kernel NULL pointer dereference, address: 0000000000000000
Date: Mon, 15 Jul 2024 10:24:03 -0400	[thread overview]
Message-ID: <20240715142403.GA70013@mit.edu> (raw)
In-Reply-To: <ejaxnieh5h6bfeocb7gwtonirthjvpgoveqvmfnb5ebqk33uxs@4lvgdocvt55c>

On Mon, Jul 15, 2024 at 08:01:54AM +0000, Daniel Gomez wrote:
> 
> My guess is that '-o acl,user_xattr' [1] options are now included in
> the scratch device and they were not before. This is what patch 4
> fixes. f2fs, tmpfs, reiserfs, gfs2 and ext* will be affected as well
> with their respective default mount options.

At least for ext4, acl and user_xattr are enabled by default:

% kvm-xfstests shell
...
root@kvm-xfstests:~# mount -t ext4 /dev/vdc /vdc
[   11.207917] EXT4-fs (vdc): recovery complete
[   11.209103] EXT4-fs (vdc): mounted filesystem 881ec32f-72a0-4b10-9a3f-a68c68f31f40 r/w with ordered data mode. Quota mode: none.
root@kvm-xfstests:~# cat /proc/fs/ext4/vdc/options 
...
user_xattr
acl
...
root@kvm-xfstests:~# 

> [1] From _common_mount_opts(). Snippet:
> 
> 	ext2|ext3|ext4|ext4dev)
> 		# acls & xattrs aren't turned on by default on ext$FOO
> 		echo "-o acl,user_xattr $EXT_MOUNT_OPTIONS"
> 		;;

Yeah, that hasn't been true for a while....

commit ea6633369458992241599c9d9ebadffaeddec164
Author: Eric Sandeen <sandeen@redhat.com>
Date:   Wed Feb 23 17:51:51 2011 -0500

    ext4: enable acls and user_xattr by default
    
    There's no good reason to require the extra step of providing
    a mount option for acl or user_xattr once the feature is configured
    on; no other filesystem that I know of requires this.

So we probably remove that bit from _common_mount_opts.  :-)

    	       	      	       	    			 - Ted

  reply	other threads:[~2024-07-15 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240714034640eucas1p20269c99db76a1958bb4207df92552896@eucas1p2.samsung.com>
2024-07-14  3:46 ` [Bug report]: fstests g/388 crash on ext4, BUG: kernel NULL pointer dereference, address: 0000000000000000 Zorro Lang
2024-07-15  4:28   ` Theodore Ts'o
2024-07-15  8:01     ` Daniel Gomez
2024-07-15 14:24       ` Theodore Ts'o [this message]
2024-07-16  6:20     ` Zorro Lang
2024-07-16 12:23       ` Daniel Gomez
2024-07-16 15:43         ` Zorro Lang
2024-07-15  8:05   ` Daniel Gomez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240715142403.GA70013@mit.edu \
    --to=tytso@mit.edu \
    --cc=da.gomez@samsung.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=zlang@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.