public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: David Wysochanski <dwysocha@redhat.com>,
	Dave Wysochanski <wysochanski@pobox.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: BUG in nfs_read_folio() when tracing is enabled
Date: Wed, 3 Jul 2024 07:18:31 -0700	[thread overview]
Message-ID: <ZoVdtyBhlaWOVW7M@infradead.org> (raw)
In-Reply-To: <EEF1CD25-B709-4B8B-BFEA-6A96748EDE85@oracle.com>

On Wed, Jul 03, 2024 at 01:40:32PM +0000, Chuck Lever III wrote:
> > Was your test running both reads and truncates on the same file in parallel?
> 
> I didn't record it in my notes, but IIRC I was running fstests.
> I'm pretty sure one or more of the fsx-based tests will do this.

Note that you don't have to truncate as in the truncate system call or
anything changing the file system.  Simply invalidating the page cache
can lead to that, and xfstests exercises that heavily in the tests that
mix buffered and direct I/O.

      reply	other threads:[~2024-07-03 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 20:45 BUG in nfs_read_folio() when tracing is enabled Chuck Lever III
2024-07-02 20:59 ` David Wysochanski
2024-07-02 21:14   ` David Wysochanski
2024-07-02 21:17   ` Chuck Lever III
2024-07-02 21:33     ` David Wysochanski
2024-07-03  5:08       ` Christoph Hellwig
2024-07-05 13:45         ` Chuck Lever III
2024-07-05 13:47           ` Christoph Hellwig
2024-07-09 15:45             ` David Wysochanski
2024-07-10  6:33               ` Christoph Hellwig
2024-07-03 13:40       ` Chuck Lever III
2024-07-03 14:18         ` Christoph Hellwig [this message]

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=ZoVdtyBhlaWOVW7M@infradead.org \
    --to=hch@infradead.org \
    --cc=chuck.lever@oracle.com \
    --cc=dwysocha@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=wysochanski@pobox.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