Linux NFS development
 help / color / mirror / Atom feed
From: dai.ngo@oracle.com
To: Mike Galbraith <efault@gmx.de>, Chuck Lever III <chuck.lever@oracle.com>
Cc: 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: Sun, 8 Jan 2023 22:34:40 -0800	[thread overview]
Message-ID: <cd171f89-e1c1-d8d5-4bf5-ce22036baef4@oracle.com> (raw)
In-Reply-To: <5a18fd0de4b1d0498905e786b31f9610be76cc13.camel@gmx.de>


On 1/8/23 6:41 PM, Mike Galbraith wrote:
> On Sun, 2023-01-08 at 16:50 -0800, dai.ngo@oracle.com wrote:
>> Hi Mike,
> Greetings,
>
>> Could you give the v2 patch a try? I will send you the location
>> to upload the core, if it happens, in a private email.
> V2 cured it.  I also verified that virgin rc3 still does spew/brick.

Thank you much Mike!

-Dai


  reply	other threads:[~2023-01-09  6:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <65ed34338c69cb034295f2c9cbe0af684d65d30f.camel@gmx.de>
2022-12-21  9:56 ` regression: nfs mount (even idle) eventually hangs server 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 [this message]
2023-01-05 14:14 ` summary: " 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=cd171f89-e1c1-d8d5-4bf5-ce22036baef4@oracle.com \
    --to=dai.ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=efault@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox