linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: regression: nfs mount (even idle) eventually hangs server #forregzbot
Date: Thu, 22 Dec 2022 12:19:57 +0100	[thread overview]
Message-ID: <0bee316d-8b9c-055b-4fdc-0abd151799d7@leemhuis.info> (raw)
In-Reply-To: <65ed34338c69cb034295f2c9cbe0af684d65d30f.camel@gmx.de>

[Note: this mail contains only information for Linux kernel regression
tracking. Mails like these contain '#forregzbot' in the subject to make
then easy to spot and filter out. The author also tried to remove most
or all individuals from the list of recipients to spare them the hassle.]

On 21.12.22 09:59, Mike Galbraith wrote:
> scenario: /home/mikeg of desktop box mounted by lappy, lappy sitting
> idle with user mikeg not even logged in.  Reclaim inducing activity on
> desktop box eventually leads to spew below.  I've hung the box three
> times in two days, twice with light client side activity, and below
> with none, ie with the mount point allegedly merely existing. Sans nfs
> mount, box seems perfectly fine. 6.1 didn't reproduce either, so it
> would appear to be a merge window bug.

Thanks for the report. To be sure below issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
tracking bot:

#regzbot ^introduced v5.19..v6.0
#regzbot title nfs: mount (even idle) eventually hangs server
#regzbot ignore-activity

From later in the thread it seems it unclear when it's started, for
tracking just go with Chuck's assumption

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.

  parent reply	other threads:[~2022-12-22 11:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21  8:59 regression: nfs mount (even idle) eventually hangs server Mike Galbraith
2022-12-21  9:56 ` Mike Galbraith
2022-12-22  3:42   ` Mike Galbraith
2022-12-22  4:14     ` Mike Galbraith
2022-12-22  4:28       ` Chuck Lever III
2022-12-22  4:44         ` Mike Galbraith
2022-12-22 13:30           ` Mike Galbraith
2022-12-22 14:21             ` Chuck Lever III
2022-12-23  4:41               ` Mike Galbraith
2022-12-23  6:28                 ` Mike Galbraith
2022-12-23 12:02                   ` dai.ngo
2022-12-23 13:05                     ` Mike Galbraith
2023-01-09  0:50                       ` dai.ngo
2023-01-09  2:41                         ` Mike Galbraith
2023-01-09  6:34                           ` dai.ngo
2022-12-22 11:19 ` Thorsten Leemhuis [this message]
2023-02-17 12:45   ` regression: nfs mount (even idle) eventually hangs server #forregzbot Linux regression tracking #update (Thorsten Leemhuis)
2023-01-05 14:14 ` summary: regression: nfs mount (even idle) eventually hangs server Mike Galbraith

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=0bee316d-8b9c-055b-4fdc-0abd151799d7@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-kernel@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).