All of lore.kernel.org
 help / color / mirror / Atom feed
From: "poester" <poester@internetbrands.com>
To: gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org, Phil O <kernel@linuxace.com>
Subject: Re: Linux 6.1.56
Date: Thu, 12 Oct 2023 09:54:40 -0700	[thread overview]
Message-ID: <20231012165439.137237-2-kernel@linuxace.com> (raw)
In-Reply-To: <2023100635-pushchair-predator-9ae3@gregkh>

Since rolling out 6.1.56 we have been experiencing file corruption
over NFSv3.  We bisected it down to

 f16fd0b11f0f NFS: Fix error handling for O_DIRECT write scheduling

But that doesn't cleanly revert so we ended up reverting all NFS
changes from 6.1.56 and the corruption no longer occurs.  Namely:

 edd1f0614510 NFS: More fixes for nfs_direct_write_reschedule_io()
 d4729af1c73c NFS: Use the correct commit info in nfs_join_page_group()
 1f49386d6779 NFS: More O_DIRECT accounting fixes for error paths
 4d98038e5bd9 NFS: Fix O_DIRECT locking issues
 f16fd0b11f0f NFS: Fix error handling for O_DIRECT write scheduling

The test case is fairly easily reproduced for us:

 dd if=testfile of=testfile2 oflag=direct; md5sum testfile*

shows a different md5sum between the two files on 6.1.56+ kernels.
Interestingly, on 6.5.7 this problem does not occur even though it
contains the same O_DIRECT patch as f16fd0b11f0f.

We opened a bugzilla on this:

 https://bugzilla.kernel.org/show_bug.cgi?id=217999

But this seems like a critical issue to us which should likely be
addressed in 6.1.58.

Thanks,
Phil

  parent reply	other threads:[~2023-10-12 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 12:59 Linux 6.1.56 Greg Kroah-Hartman
2023-10-06 12:59 ` Greg Kroah-Hartman
2023-10-12 16:54 ` poester [this message]
2023-10-12 17:49   ` Greg KH

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=20231012165439.137237-2-kernel@linuxace.com \
    --to=poester@internetbrands.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@linuxace.com \
    --cc=stable@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.