linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Anna Schumaker <anna@kernel.org>,
	linux-nfs@vger.kernel.org, trond.myklebust@hammerspace.com
Cc: Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH] Revert "NFSv4.2: Change the default KConfig value for READ_PLUS"
Date: Thu, 16 Feb 2023 10:34:55 +0100	[thread overview]
Message-ID: <8d26e819-a3a5-7ae1-bb9e-56bacfa7f65b@leemhuis.info> (raw)
In-Reply-To: <20230215214922.1811502-1-anna@kernel.org>

On 15.02.23 22:49, Anna Schumaker wrote:
> From: Anna Schumaker <Anna.Schumaker@Netapp.com>
> 
> This reverts commit 7fd461c47c6cfab4ca4d003790ec276209e52978.
> 
> Unfortunately, it has come to our attention that there is still a bug
> somewhere in the READ_PLUS code that can result in nfsroot systems on
> ARM to crash during boot.
> 
> Let's do the right thing and revert this change so we don't break
> people's nfsroot setups.

Many thx for taking care of this.

Do you plan to send this to Linus before he releases the final? Or
should I point him to this patch (or a later version) in my weekly
report so that he can decide himself if he wants to pick it up?

There is afaics also one small thing to improve, please add the
following tags to make things easier for future code archaeologists:

Reported-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Link:
https://lore.kernel.org/all/f591b13c-4600-e2a4-8efa-aac6ad828dd1@linaro.org/

To explain: Linus[1] and others considered proper link tags with the URL
to the report important, as they allow anyone to look into the backstory
of a fix weeks or years later. That's nothing new, the documentation[2]
for some time says to place such tags in cases like this. I care
personally (and made it a bit more explicit in the docs a while ago),
because these tags make my regression tracking efforts a whole lot
easier, as they allow my tracking bot 'regzbot' to automatically connect
reports with patches posted or committed to fix tracked regressions.

Apropos regzbot, let me tell regzbot to monitor this thread:

#regzbot ^backmonitor:
https://lore.kernel.org/all/f591b13c-4600-e2a4-8efa-aac6ad828dd1@linaro.org/

> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
> [...]

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

[1] for details, see:
https://lore.kernel.org/all/CAHk-=wjMmSZzMJ3Xnskdg4+GGz=5p5p+GSYyFBTh0f-DgvdBWg@mail.gmail.com/
https://lore.kernel.org/all/CAHk-=wgs38ZrfPvy=nOwVkVzjpM3VFU1zobP37Fwd_h9iAD5JQ@mail.gmail.com/
https://lore.kernel.org/all/CAHk-=wjxzafG-=J8oT30s7upn4RhBs6TX-uVFZ5rME+L5_DoJA@mail.gmail.com/

[2] see Documentation/process/submitting-patches.rst
(http://docs.kernel.org/process/submitting-patches.html) and
Documentation/process/5.Posting.rst
(https://docs.kernel.org/process/5.Posting.html)

--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

      reply	other threads:[~2023-02-16  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 21:49 [PATCH] Revert "NFSv4.2: Change the default KConfig value for READ_PLUS" Anna Schumaker
2023-02-16  9:34 ` Linux regression tracking (Thorsten Leemhuis) [this message]

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=8d26e819-a3a5-7ae1-bb9e-56bacfa7f65b@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=anna@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=trond.myklebust@hammerspace.com \
    /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).