All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Dai Ngo <dai.ngo@oracle.com>, LKML <linux-kernel@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: regression: nfs mount (even idle) eventually hangs server
Date: Fri, 23 Dec 2022 05:41:18 +0100	[thread overview]
Message-ID: <a0abf7fef412dc0de0e42cbcd75ee5dec28cb544.camel@gmx.de> (raw)
In-Reply-To: <AF3DFAF9-CF19-40AE-8B8F-31D100E00F33@oracle.com>

On Thu, 2022-12-22 at 14:21 +0000, Chuck Lever III wrote:
>
> So my question is whether you see a problem when only a1049eb47f20
> is applied, or only when all three are applied?

Seemingly the latter.

	-Mike

  reply	other threads:[~2022-12-23  4:41 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 [this message]
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 ` regression: nfs mount (even idle) eventually hangs server #forregzbot Thorsten Leemhuis
2023-02-17 12:45   ` 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=a0abf7fef412dc0de0e42cbcd75ee5dec28cb544.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.