From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Sukruth Sridharan (he/him)" <susridharan@purestorage.com>
Cc: Linux Network File System <linux-nfs@vger.kernel.org>,
Linux RDMA <linux-rdma@vger.kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>
Subject: Re: Hung task panic as part of NFS RDMA Disconnect due to possible bug on 6.2.0-34-generic client
Date: Thu, 30 Nov 2023 19:17:20 +0700 [thread overview]
Message-ID: <9f53447e-191a-4e95-9f36-33f7eff82ee7@gmail.com> (raw)
In-Reply-To: <CAMyEAb9aAMwKByOx38VJP1+N0+d12sDF5FiEx-aCMdOnEF_sww@mail.gmail.com>
On 11/30/23 19:15, Sukruth Sridharan (he/him) wrote:
> The issue has been seen once in the past few weeks.
> Unfortunately, we're yet to see a repro of the same.
> We will try to repro it on the latest kernel.
> Curious if there's any improvements gone in that you suspect would
> have resolved the issue?
>
Please don't top-post; reply inline with appropriate context instead.
Sorry, I don't know about that question.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-11-30 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMyEAb9XbL55taNXD_MrTxJz62s6ByDWiK8m1Nxj1_G3pg-M6A@mail.gmail.com>
2023-11-30 7:36 ` Hung task panic as part of NFS RDMA Disconnect due to possible bug on 6.2.0-34-generic client Bagas Sanjaya
2023-11-30 12:15 ` Sukruth Sridharan (he/him)
2023-11-30 12:17 ` Bagas Sanjaya [this message]
2023-11-30 12:23 ` Sukruth Sridharan (he/him)
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=9f53447e-191a-4e95-9f36-33f7eff82ee7@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=leonro@nvidia.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=neilb@suse.de \
--cc=saeedm@nvidia.com \
--cc=susridharan@purestorage.com \
--cc=tom@talpey.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