From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jesse Hathaway <jesse@mbuki-mvuki.org>,
Christoph Hellwig <hch@lst.de>,
Florian Weimer <fweimer@redhat.com>,
Aleksa Sarai <cyphar@cyphar.com>,
linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
stable@vger.kernel.org,
Linux regressions mailing list <regressions@lists.linux.dev>,
giuseppe@scrivano.org
Subject: Re: [PATCH] attr: block mode changes of symlinks
Date: Fri, 20 Oct 2023 16:25:17 +0200 [thread overview]
Message-ID: <2023102034-atlas-obligate-46bb@gregkh> (raw)
In-Reply-To: <20231020-allgegenwart-torbogen-33dc58e9a7aa@brauner>
On Fri, Oct 20, 2023 at 01:01:44PM +0200, Christian Brauner wrote:
> The other option to consider would be to revert the backport of the attr
> changes to stable kernels. I'm not sure what Greg's stance on this is
> but given that crun versions in -testing already include that fix that
> means all future Debian releases will already have a fixed crun version.
I will be glad to revert a change in a stable tree that is also reverted
in Linus's tree, but to just "delay" a change getting into the tree,
that's not ok (either the change is good or not.)
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-20 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 18:34 [PATCH] attr: block mode changes of symlinks Jesse Hathaway
2023-10-18 18:40 ` Greg KH
2023-10-18 18:49 ` Jesse Hathaway
2023-10-18 19:09 ` Greg KH
2023-10-20 8:34 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-20 11:01 ` Christian Brauner
2023-10-20 13:26 ` Giuseppe Scrivano
2023-10-20 14:25 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-12 9:56 Christian Brauner
2023-07-12 16:21 ` Greg KH
2023-07-12 17:58 ` Christian Brauner
2023-07-12 16:24 ` Linus Torvalds
2023-07-12 17:56 ` Christian Brauner
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=2023102034-atlas-obligate-46bb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=cyphar@cyphar.com \
--cc=fweimer@redhat.com \
--cc=giuseppe@scrivano.org \
--cc=hch@lst.de \
--cc=jesse@mbuki-mvuki.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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 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.