From: Thorsten Leemhuis <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2] nfsd: fix net-namespace logic in __nfsd_file_cache_purge #forregzbot
Date: Wed, 9 Nov 2022 16:53:59 +0100 [thread overview]
Message-ID: <a6168d8c-b991-478f-ada6-46cc4068543d@leemhuis.info> (raw)
In-Reply-To: <Y2WCdDAGt1OEFzL7@pevik>
[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]
On 04.11.22 22:21, Petr Vorel wrote:
> Hi all,
>
>> If the namespace doesn't match the one in "net", then we'll continue,
>> but that doesn't cause another rhashtable_walk_next call, so it will
>> loop infinitely.
>
>> Fixes: ce502f81ba88 ("NFSD: Convert the filecache to use rhashtable")
>
> Adding this to regression tracker.
> https://linux-regtracking.leemhuis.info/tracked-regression/
>
> #regzbot ^introduced ce502f81ba88
> #regzbot ignore-activity
#regzbot fixed-by: d3aefd2b29ff5
prev parent reply other threads:[~2022-11-09 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 15:49 [PATCH v2] nfsd: fix net-namespace logic in __nfsd_file_cache_purge Jeff Layton
2022-10-31 17:10 ` Chuck Lever III
2022-10-31 18:45 ` Petr Vorel
2022-10-31 18:46 ` Jeff Layton
2022-10-31 18:47 ` Chuck Lever III
2022-10-31 19:05 ` Petr Vorel
2022-11-04 21:21 ` Petr Vorel
2022-11-09 15:53 ` 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=a6168d8c-b991-478f-ada6-46cc4068543d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-nfs@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).