[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y13dtaih.fsf@gentoo.org>
Date: Fri, 27 Sep 2024 15:51:50 +0100
From: Sam James <sam@...too.org>
To: Kairui Song <ryncsn@...il.com>,Greg KH <gregkh@...uxfoundation.org>
Cc: stable@...nel.org, clm@...a.com, Matthew Wilcox <willy@...radead.org>,
axboe@...nel.dk, ct@...ingcircus.io, david@...morbit.com,
dqminh@...udflare.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-xfs@...r.kernel.org, regressions@...mhuis.info,
regressions@...ts.linux.dev, torvalds@...ux-foundation.org
Subject: Re: Known and unfixed active data loss bug in MM + XFS with large
folios since Dec 2021 (any kernel from 6.1 upwards)
Kairui Song <ryncsn@...il.com> writes:
> On Wed, Sep 25, 2024 at 1:16 AM Sam James <sam@...too.org> wrote:
>>
>> Kairui, could you send them to the stable ML to be queued if Willy is
>> fine with it?
>>
>
> Hi Sam,
Hi Kairui,
>
> Thanks for adding me to the discussion.
>
> Yes I'd like to, just not sure if people are still testing and
> checking the commits.
>
> And I haven't sent seperate fix just for stable fix before, so can
> anyone teach me, should I send only two patches for a minimal change,
> or send a whole series (with some minor clean up patch as dependency)
> for minimal conflicts? Or the stable team can just pick these up?
Please see https://www.kernel.org/doc/html/v6.11/process/stable-kernel-rules.html.
If Option 2 can't work (because of conflicts), please follow Option 3
(https://www.kernel.org/doc/html/v6.11/process/stable-kernel-rules.html#option-3).
Just explain the background and link to this thread in a cover letter
and mention it's your first time. Greg didn't bite me when I fumbled my
way around it :)
(greg, please correct me if I'm talking rubbish)
thanks,
sam
Powered by blists - more mailing lists