linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: Anna Schumaker <anna.schumaker@oracle.com>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
	linux-nfs@vger.kernel.org, zlang@redhat.com
Subject: [for-v6.18 PATCH v2 0/3] nfs/localio: fix various new issues
Date: Wed, 26 Nov 2025 01:01:24 -0500	[thread overview]
Message-ID: <20251126060127.67773-1-snitzer@kernel.org> (raw)

Hi Anna,

Here are 3 LOCALIO fixes for issues discovered as a side-effect of
Zorro's recent bug report:
https://lore.kernel.org/linux-nfs/20251125144508.rxepvtwrubbuhzxs@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com/

(note that the "generic/751 hang on nfs" still isn't fixed but that
one is a long-standing issue that can be reproduced against stock
v6.12.53 -- whereas these 3 fixes address code introduced during
v6.18-rcX).

Sorry for the trouble, have a wonderful Thanksgiving!

Mike

v2 changes:
- patch 1/3 is the same as was posted here:
  https://lore.kernel.org/linux-nfs/aSaTC51DkxEqQkrZ@kernel.org/
- added patches 2/3 and 3/3

Mike Snitzer (3):
  nfs/localio: fix regression due to out-of-order __put_cred
  nfs/localio: remove alignment size checking in nfs_is_local_dio_possible
  nfs/localio: remove 61 byte hole from needless ____cacheline_aligned

 fs/nfs/localio.c | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

-- 
2.44.0


             reply	other threads:[~2025-11-26  6:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  6:01 Mike Snitzer [this message]
2025-11-26  6:01 ` [PATCH v2 1/3] nfs/localio: fix regression due to out-of-order __put_cred Mike Snitzer
2025-11-26  6:01 ` [PATCH v2 2/3] nfs/localio: remove alignment size checking in nfs_is_local_dio_possible Mike Snitzer
2025-11-26  6:01 ` [PATCH v2 3/3] nfs/localio: remove 61 byte hole from needless ____cacheline_aligned Mike Snitzer
2025-11-28 17:40 ` [for-v6.18 PATCH v2 0/3] nfs/localio: fix various new issues Zorro Lang

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=20251126060127.67773-1-snitzer@kernel.org \
    --to=snitzer@kernel.org \
    --cc=anna.schumaker@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.com \
    --cc=zlang@redhat.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;
as well as URLs for NNTP newsgroup(s).