From: Christoph Hellwig <hch@lst.de>
To: Nikita Dubrovskii <nikita@linux.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>,
brauner@kernel.org, viro@zeniv.linux.org.uk, axboe@kernel.dk,
djwong@kernel.org, ebiggers@google.com,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
dmabe@redhat.com
Subject: Re: [PATCH] fs: move the bdex_statx call to vfs_getattr_nosec
Date: Fri, 25 Apr 2025 15:39:54 +0200 [thread overview]
Message-ID: <20250425133954.GA6802@lst.de> (raw)
In-Reply-To: <d6dc234d922d8beda65f2a1eed1e2de6a50c978f.camel@linux.ibm.com>
On Fri, Apr 25, 2025 at 03:32:55PM +0200, Nikita Dubrovskii wrote:
> Hi all,
>
> We're seeing a boot failure on first boot in Fedora CoreOS starting
> with kernel 6.15.0-0.rc3, tracked here:
> https://github.com/coreos/fedora-coreos-tracker/issues/1936
This should be fixed by:
https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git/commit/?h=vfs.fixes&id=e079d7c4db5cba1e8a315dc93030dfb6c7b49459
prev parent reply other threads:[~2025-04-25 13:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 6:40 [PATCH] fs: move the bdex_statx call to vfs_getattr_nosec Christoph Hellwig
2025-04-17 8:01 ` Christian Brauner
2025-04-17 8:14 ` Christian Brauner
2025-04-17 16:20 ` Darrick J. Wong
2025-04-22 5:03 ` Shinichiro Kawasaki
2025-04-22 5:51 ` hch
2025-04-22 7:25 ` Christian Brauner
2025-04-22 7:27 ` hch
2025-04-22 8:15 ` Christian Brauner
2025-04-22 8:17 ` hch
2025-04-22 9:29 ` Christian Brauner
2025-04-22 14:15 ` hch
2025-04-22 15:35 ` Christian Brauner
2025-04-23 1:31 ` Shinichiro Kawasaki
2025-04-23 4:30 ` Jain, Ayush
2025-04-22 10:31 ` Shinichiro Kawasaki
2025-04-22 14:18 ` Heiko Carstens
[not found] ` <d6dc234d922d8beda65f2a1eed1e2de6a50c978f.camel@linux.ibm.com>
2025-04-25 13:39 ` Christoph Hellwig [this message]
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=20250425133954.GA6802@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=dmabe@redhat.com \
--cc=ebiggers@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nikita@linux.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).