From: Christoph Hellwig <hch@lst.de>
To: Christian Brauner <brauner@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Revert "fs: move the bdex_statx call to vfs_getattr_nosec"
Date: Thu, 24 Apr 2025 11:04:44 +0200 [thread overview]
Message-ID: <20250424090444.GA27439@lst.de> (raw)
In-Reply-To: <20250424-patient-abgeebbt-a0a7001f040b@brauner>
On Thu, Apr 24, 2025 at 10:59:44AM +0200, Christian Brauner wrote:
> This reverts commit 777d0961ff95b26d5887fdae69900374364976f3.
>
> Now that we have fixed the original issue in devtmpfs we can revert this
> commit because the bdev_statx() call in vfs_getattr_nosec() causes
> issues with the lifetime logic of dm devices.
Umm, no. We need this patch. And the devtmpfs fixes the issue that
it caused for devtmpfs.
next prev parent reply other threads:[~2025-04-24 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 8:59 [PATCH] Revert "fs: move the bdex_statx call to vfs_getattr_nosec" Christian Brauner
2025-04-24 9:04 ` Christoph Hellwig [this message]
2025-04-24 9:22 ` Christian Brauner
2025-04-24 10:55 ` Christoph Hellwig
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=20250424090444.GA27439@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).