linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Chengen Du <chengen.du@canonical.com>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
	Anna Schumaker <anna@kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Bug 217165 - NFS cache stops working if accessed from process with PPID of 1
Date: Mon, 20 Mar 2023 13:40:33 +0100	[thread overview]
Message-ID: <16171331-8301-738e-8c1d-b48a11275ce9@leemhuis.info> (raw)
In-Reply-To: <1ee77457-3345-0f7f-a0d0-fa8eced53b8f@leemhuis.info>

[adding the author of the culprit, the NFS maintainers & list and lkml
to the list of recipients]

On 10.03.23 10:42, Linux regression tracking #adding (Thorsten Leemhuis)
wrote:
> [TLDR: Just adding a regression reported to bko to the tracking]
> 
> Hi, Thorsten here, the Linux kernel's regression tracker. I noticed a
> regression reported in bugzilla.kernel.org that likely will be handled
> there (normally the NFS developer do that),

Seems I was wrong in this case or in general, as that bug report didn't
get a single reply yet. Hence this mail to ensure the right people have
it on their radar. Or was some progress to address this made and I just
missed it?

> nevertheless I'd like to add
> to the tracking to ensure it's doesn't fall through the cracks in the end:
> 
> #regzbot introduced: 029085b8949f5d269ae
> https://bugzilla.kernel.org/show_bug.cgi?id=217165
> #regzbot title: nfs: cache stops working if accessed from process with
> PPID of 1
> #regzbot ignore-activity
> 
> See the ticket for details, there were a few replies already.

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.

#regzbot poke

       reply	other threads:[~2023-03-20 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ee77457-3345-0f7f-a0d0-fa8eced53b8f@leemhuis.info>
2023-03-20 12:40 ` Thorsten Leemhuis [this message]
2023-03-21 11:54   ` [regression] Bug 217165 - NFS cache stops working if accessed from process with PPID of 1 Linux regression tracking #update (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=16171331-8301-738e-8c1d-b48a11275ce9@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=anna@kernel.org \
    --cc=chengen.du@canonical.com \
    --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).