From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: shankerwangmiao@gmail.com
Cc: stable@vger.kernel.org, "Xi Ruoyao" <xry111@xry111.site>,
"Mateusz Guzik" <mjguzik@gmail.com>,
"Christian Brauner" <brauner@kernel.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kara" <jack@suse.cz>, "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/3] Backport statx(..., NULL, AT_EMPTY_PATH, ...)
Date: Wed, 18 Sep 2024 19:33:18 +0200 [thread overview]
Message-ID: <2024091801-segment-lurk-e67b@gregkh> (raw)
In-Reply-To: <20240918-statx-stable-linux-6-10-y-v1-0-8364a071074f@gmail.com>
On Wed, Sep 18, 2024 at 10:01:18PM +0800, Miao Wang via B4 Relay wrote:
> Commit 0ef625bba6fb ("vfs: support statx(..., NULL, AT_EMPTY_PATH,
> ...)") added support for passing in NULL when AT_EMPTY_PATH is given,
> improving performance when statx is used for fetching stat informantion
> from a given fd, which is especially important for 32-bit platforms.
> This commit also improved the performance when an empty string is given
> by short-circuiting the handling of such paths.
>
> This series is based on the commits in the Linus’ tree. Sligth
> modifications are applied to the context of the patches for cleanly
> applying.
>
> Tested-by: Xi Ruoyao <xry111@xry111.site>
> Signed-off-by: Miao Wang <shankerwangmiao@gmail.com>
This really looks like a brand new feature wanting to be backported, so
why does it qualify under the stable kernel rules as fixing something?
I am willing to take some kinds of "fixes performance issues" new
features when the subsystem maintainers agree and ask for it, but that
doesn't seem to be the case here, and so without their approval and
agreement that this is relevant, we can't accept them.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-18 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 14:01 [PATCH 0/3] Backport statx(..., NULL, AT_EMPTY_PATH, ...) Miao Wang via B4 Relay
2024-09-18 14:01 ` [PATCH v6.10 1/3] fs: new helper vfs_empty_path() Miao Wang via B4 Relay
2024-09-18 14:01 ` [PATCH v6.10 2/3] stat: use vfs_empty_path() helper Miao Wang via B4 Relay
2024-09-18 14:01 ` [PATCH v6.10 3/3] vfs: support statx(..., NULL, AT_EMPTY_PATH, ...) Miao Wang via B4 Relay
2024-09-18 17:33 ` Greg Kroah-Hartman [this message]
2024-09-18 17:37 ` [PATCH 0/3] Backport " Xi Ruoyao
2024-09-19 11:18 ` Greg Kroah-Hartman
2024-09-19 12:18 ` Miao Wang
2024-09-27 6:57 ` Greg Kroah-Hartman
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=2024091801-segment-lurk-e67b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=gary@garyguo.net \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=ojeda@kernel.org \
--cc=shankerwangmiao@gmail.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wedsonaf@gmail.com \
--cc=xry111@xry111.site \
/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).