From: Greg KH <gregkh@linuxfoundation.org>
To: Anthony Brennan <a2brenna@hatguy.io>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2] netfs: Fix missing xas_retry() calls in xarray iteration
Date: Sat, 23 Dec 2023 09:44:29 +0100 [thread overview]
Message-ID: <2023122338-cape-deplored-05a8@gregkh> (raw)
In-Reply-To: <20231222195152.GB8982@hatguy.io>
On Fri, Dec 22, 2023 at 02:51:52PM -0500, Anthony Brennan wrote:
> On Fri, Dec 22, 2023 at 07:26:23AM +0100, Greg KH wrote:
> > On Thu, Dec 21, 2023 at 08:32:29PM -0500, Anthony Brennan wrote:
> > > To be applied to linux-5.15.y.
> > >
> > > commit 59d0d52c30d4991ac4b329f049cc37118e00f5b0 upstream
> >
> > That is not this commit at all :(
> >
>
> Thank you for your time.
>
> >From what I can tell, the upstream commit merged by Linus includes two
> unrelated sets of changes: handling xas_retry, and fixes to "dodgy
> maths". I discarded the fixes to dodgy maths for two reasons, first the
> commit log says they solve a theoretical potential problem and the
> guidelines for submissions to the stable kernel say to avoid such
> patches, and second, I lack the expertise to be confident those fixes
> are correct when working with pages and not folios.
>
> Unsure what I should have done here.
Submit a real patch for the normal tree and then we can backport the
same commit id to a stable tree. You can't backport a merge commit as
obviously that doesn't make sense in an older tree.
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-23 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 1:32 [PATCH v2] netfs: Fix missing xas_retry() calls in xarray iteration Anthony Brennan
2023-12-22 6:26 ` Greg KH
2023-12-22 19:51 ` Anthony Brennan
2023-12-23 8:44 ` Greg KH [this message]
2023-12-30 11:41 ` Greg KH
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=2023122338-cape-deplored-05a8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a2brenna@hatguy.io \
--cc=stable@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