From: Christoph Hellwig <hch@lst.de>
To: trondmy@kernel.org, anna@kernel.org
Cc: chuck.lever@oracle.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] nfs: pass explicit offset/count to trace events
Date: Thu, 11 Jul 2024 09:18:09 +0200 [thread overview]
Message-ID: <20240711071809.GA8753@lst.de> (raw)
In-Reply-To: <20240711071703.65793-1-hch@lst.de>
On Thu, Jul 11, 2024 at 09:17:02AM +0200, Christoph Hellwig wrote:
> lead to kernel crashes. E.g. when running xfstests generic/065 with
> all nfs trace points enabled.
Sorry, this should read generic/095.
next prev parent reply other threads:[~2024-07-11 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 7:17 [PATCH 1/2] nfs: pass explicit offset/count to trace events Christoph Hellwig
2024-07-11 7:17 ` [PATCH 2/2] nfs: split nfs_read_folio Christoph Hellwig
2024-07-14 13:29 ` Sagi Grimberg
2024-07-11 7:18 ` Christoph Hellwig [this message]
2024-07-14 13:28 ` [PATCH 1/2] nfs: pass explicit offset/count to trace events Sagi Grimberg
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=20240711071809.GA8753@lst.de \
--to=hch@lst.de \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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