From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Bug 215975 - NFSD stops serving clients
Date: Sat, 21 May 2022 12:27:42 +0200 [thread overview]
Message-ID: <156f1150-e0d6-0ead-bdbf-58eb0049db26@leemhuis.info> (raw)
Hi, this is your Linux kernel regression tracker speaking.
About a week ago a regression was reported to bugzilla.kernel.org that
seems to be handled there already. Nevertheless, I'd like to add to the
tracking to ensure it's not forgotten.
#regzbot introduced: v5.12..v5.13
#regzbot from: Ho Ming Shun <cyph1984@gmail.com>
#regzbot title: NFSD stops serving clients
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215975
See the ticket for details, there were a few replies already.
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/
Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replied to), as the kernel's
documentation call for; above page explains why this is important for
tracked regressions.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
next reply other threads:[~2022-05-21 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 10:27 Thorsten Leemhuis [this message]
2022-06-20 7:26 ` Bug 215975 - NFSD stops serving clients #forregzbot Thorsten Leemhuis
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=156f1150-e0d6-0ead-bdbf-58eb0049db26@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--subject='Re: Bug 215975 - NFSD stops serving clients' \
/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
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).