From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Anthony Iliopoulos <ailiop@suse.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
stable@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH STABLE 5.10 5.11] swap: fix swapfile page to sector mapping
Date: Thu, 4 Mar 2021 17:58:49 +0100 [thread overview]
Message-ID: <YEERyfs8QSB5lGVz@kroah.com> (raw)
In-Reply-To: <YEELCJkGx78SP34d@technoir>
On Thu, Mar 04, 2021 at 05:30:00PM +0100, Anthony Iliopoulos wrote:
> On Thu, Mar 04, 2021 at 04:16:26PM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Mar 04, 2021 at 04:08:24PM +0100, Anthony Iliopoulos wrote:
> > > commit caf6912f3f4af7232340d500a4a2008f81b93f14 upstream.
> >
> > No, this does not look like that commit.
> >
> > Why can I not just take caf6912f3f4a ("swap: fix swapfile read/write
> > offset") directly for 5.10 and 5.11? WHat has changed to prevent that?
>
> You're right of course, the upstream fix applies even on v5.4 so you
> could just take it directly for those branches if this is preferable.
But, that commit says it fixes 48d15436fde6 ("mm: remove get_swap_bio"),
which is NOT what you are saying here in these patches.
So which is it? Is there a problem in 5.11 and older kernels
(48d15436fde6 ("mm: remove get_swap_bio") showed up in 5.12-rc1), that
requires this fix, or is there nothing needed to be backported?
As a note, I've been running swapfiles on 5.11 and earlier just fine for
a very long time now, so is this really an issue?
confused,
greg k-h
next prev parent reply other threads:[~2021-03-04 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 15:08 [PATCH STABLE ONLY] swap: fix swapfile page to sector mapping Anthony Iliopoulos
2021-03-04 15:08 ` [PATCH STABLE 4.14 4.19] " Anthony Iliopoulos
2021-03-04 15:08 ` [PATCH STABLE 4.4] " Anthony Iliopoulos
2021-03-04 15:08 ` [PATCH STABLE 4.9] " Anthony Iliopoulos
2021-03-04 15:08 ` [PATCH STABLE 5.10 5.11] " Anthony Iliopoulos
2021-03-04 15:16 ` Greg Kroah-Hartman
2021-03-04 16:30 ` Anthony Iliopoulos
2021-03-04 16:58 ` Greg Kroah-Hartman [this message]
2021-03-04 21:17 ` Anthony Iliopoulos
2021-03-05 8:27 ` Greg Kroah-Hartman
2021-03-04 15:08 ` [PATCH STABLE 5.4] " Anthony Iliopoulos
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=YEERyfs8QSB5lGVz@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ailiop@suse.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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 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.