From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Anna Schumaker <Anna.Schumaker@Netapp.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: linux-nfs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression: NULL pointer dereference after NFS_V4_2_READ_PLUS (commit 7fd461c47)
Date: Tue, 21 Feb 2023 15:24:52 +0100 [thread overview]
Message-ID: <9dda9e11-565f-8725-6d15-803a66782753@leemhuis.info> (raw)
In-Reply-To: <78806040-5725-103f-fe55-8c6d9ced6e63@linaro.org>
On 18.02.23 16:09, Krzysztof Kozlowski wrote:
> On 18/02/2023 05:42, Linux regression tracking #update (Thorsten
> Leemhuis) wrote:
>> [TLDR: This mail in primarily relevant for Linux regression tracking. A
>> change or fix related to the regression discussed in this thread was
>> posted or applied, but it did not use a Link: tag to point to the
>> report, as Linus and the documentation call for. Things happen, no
>> worries -- but now the regression tracking bot needs to be told manually
>> about the fix. See link in footer if these mails annoy you.]
>>
>> On 08.01.23 09:52, Linux kernel regression tracking (#adding) wrote:
>>> On 07.01.23 16:44, Krzysztof Kozlowski wrote:
>>>>
>>>> Bisect identified commit 7fd461c47c6c ("NFSv4.2: Change the default
>>>> KConfig value for READ_PLUS") as one leading to NULL pointer exception
>>>> when mounting NFS root on NFSv4 client:
>>> [...]
>>> Thanks for the report. To be sure the issue doesn't fall through the
>>> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
>>> tracking bot:
>>>
>>> #regzbot ^introduced 7fd461c47
>>> #regzbot title nfs: NULL pointer dereference since NFS_V4_2_READ_PLUS is
>>> enabled by default
>>> #regzbot ignore-activity
>>
>> #regzbot fix: 896e090eefedeb8a715ea19938a2791c32679
>
> I see it was posted and merged as "Revert "NFSv4.2: Change the default
> KConfig value for READ_PLUS"". It's nice to give credits to people who
> report bugs with "Reported-by" tag.
Yup. And a "Link:" with the url to the report is missing as well (Linus
wants those, automatic regression tracking needs those [IOW: if they are
missing it causes me trouble, that's why I care], and the docs explain
this as well).
That's why I asked for those two tags, but I didn't even get a reply:
https://lore.kernel.org/all/8d26e819-a3a5-7ae1-bb9e-56bacfa7f65b@leemhuis.info/
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
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.
next prev parent reply other threads:[~2023-02-21 14:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 15:44 Regression: NULL pointer dereference after NFS_V4_2_READ_PLUS (commit 7fd461c47) Krzysztof Kozlowski
2023-01-08 8:52 ` Linux kernel regression tracking (#adding)
2023-02-18 4:42 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-02-18 15:09 ` Krzysztof Kozlowski
2023-02-21 14:24 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-01-08 13:25 ` Krzysztof Kozlowski
2023-01-08 17:09 ` Trond Myklebust
2023-01-09 8:14 ` Krzysztof Kozlowski
2023-01-09 8:42 ` Krzysztof Kozlowski
2023-01-09 14:44 ` Trond Myklebust
2023-01-09 15:07 ` Chuck Lever III
2023-01-09 15:26 ` Anna Schumaker
2023-01-09 18:25 ` Chuck Lever III
2023-01-09 15:38 ` Trond Myklebust
2023-01-09 17:11 ` Chuck Lever III
2023-01-09 17:20 ` Chuck Lever III
2023-01-22 22:25 ` Anna Schumaker
2023-01-23 7:58 ` Krzysztof Kozlowski
2023-02-09 18:22 ` Anna Schumaker
2023-02-10 8:41 ` Krzysztof Kozlowski
2023-02-10 8:53 ` Krzysztof Kozlowski
2023-02-10 20:55 ` Anna Schumaker
2023-02-11 11:23 ` Krzysztof Kozlowski
2023-02-12 14:05 ` Anna Schumaker
2023-02-14 11:02 ` Krzysztof Kozlowski
2023-02-16 17:40 ` Olga Kornievskaia
2023-03-06 17:09 ` Anna Schumaker
2023-04-04 1:01 ` Olga Kornievskaia
2023-04-04 5:29 ` Krzysztof Kozlowski
2023-06-10 10:15 ` Krzysztof Kozlowski
2023-06-14 20:55 ` Anna Schumaker
2023-06-15 8:52 ` Krzysztof Kozlowski
2023-06-15 8:55 ` Krzysztof Kozlowski
2023-06-15 13:01 ` Anna Schumaker
2023-06-15 17:04 ` Anna Schumaker
2023-06-15 17:16 ` Anna Schumaker
2023-06-15 19:38 ` Anna Schumaker
2023-06-17 10:09 ` Krzysztof Kozlowski
2023-06-21 12:49 ` Anna Schumaker
2023-06-21 13:27 ` Krzysztof Kozlowski
2023-06-23 17:59 ` Anna Schumaker
2023-06-26 10:28 ` Krzysztof Kozlowski
2023-06-27 19:08 ` Anna Schumaker
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=9dda9e11-565f-8725-6d15-803a66782753@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=Anna.Schumaker@Netapp.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.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).