From: Mike Snitzer <snitzer@kernel.org>
To: Anna Schumaker <anna.schumaker@oracle.com>
Cc: Anna Schumaker <anna@kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org
Subject: Re: [GIT PULL v2] NFS LOCALIO O_DIRECT changes for Linux 6.18
Date: Tue, 30 Sep 2025 17:30:27 -0400 [thread overview]
Message-ID: <aNxL88GmEzJ5hsHl@kernel.org> (raw)
In-Reply-To: <2951eea3-772b-4a1a-9169-3d9a3c0661c5@oracle.com>
On Tue, Sep 30, 2025 at 04:53:49PM -0400, Anna Schumaker wrote:
> Hi Mike,
>
> On 9/30/25 3:32 PM, Mike Snitzer wrote:
> > Hi Anna,
> >
> > Given that my NFS LOCALIO O_DIRECT changes depend on NFSD changes
> > which will be included in the NFSD pull request for 6.18, I figured it
> > worth proposing a post-NFSD-merge pull request for your consideration
> > as the best way forward logistically (to ensure linux-next coverage,
> > you could pull this in _before_ Chuck sends his pull to Linus).
>
> I've applied your patches with the one NFSD patch acked-by Chuck and pushed
> it out to my linux-next for a few days of wider testing. I agree with Chuck
> that the remaining fixes can go in through an -rc once they're ready.
Perfect, thanks for the update.
Note that there will be merge conflicts that both linux-next and Linus
will need to resolve. Due to these nfsd-next commits:
c926f0298d3cd NFSD: Relocate the fh_want_write() and fh_drop_write() helpers
c1f203e46c55a NFSD: Move the fh_getattr() helper
2ee3a75e42081 nfsd: discard nfsd_file_get_local()
$ git checkout -b merge-conflict-test cel/nfsd-next
branch 'merge-conflict-test' set up to track 'cel/nfsd-next'.
Switched to a new branch 'merge-conflict-test'
$ git merge anna-nfs/linux-next
Auto-merging fs/nfsd/filecache.c
Auto-merging fs/nfsd/filecache.h
Auto-merging fs/nfsd/localio.c
Auto-merging fs/nfsd/vfs.h
CONFLICT (content): Merge conflict in fs/nfsd/vfs.h
Auto-merging include/linux/nfslocalio.h
Auto-merging include/linux/sunrpc/svc_xprt.h
Auto-merging include/linux/sunrpc/xdr.h
Auto-merging net/sunrpc/svc.c
Auto-merging net/sunrpc/svc_xprt.c
Automatic merge failed; fix conflicts and then commit the result.
Resolving the fs/nfsd/vfs.h conflict is really easy (just remove the
marked region), the problem is that the test merge I just did caused
this hunk to get dropped on the floor:
diff --git a/fs/nfsd/nfsfh.c b/fs/nfsd/nfsfh.c
index 062cfc18d8c6..0bc2608a80b0 100644
--- a/fs/nfsd/nfsfh.c
+++ b/fs/nfsd/nfsfh.c
@@ -698,8 +698,12 @@ __be32 fh_getattr(const struct svc_fh *fhp, struct kstat *stat)
.mnt = fhp->fh_export->ex_path.mnt,
.dentry = fhp->fh_dentry,
};
+ struct inode *inode = d_inode(p.dentry);
u32 request_mask = STATX_BASIC_STATS;
+ if (S_ISREG(inode->i_mode))
+ request_mask |= (STATX_DIOALIGN | STATX_DIO_READ_ALIGN);
+
if (fhp->fh_maxsize == NFS4_FHSIZE)
request_mask |= (STATX_BTIME | STATX_CHANGE_COOKIE);
Might be a good idea to resolve the conflict in a branch for
linux-next and Linus to reference?
Thanks,
Mike
next prev parent reply other threads:[~2025-09-30 21:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 15:41 [PATCH v9 0/7] NFS DIRECT: align misaligned DIO for LOCALIO Mike Snitzer
2025-09-15 15:41 ` [PATCH v9 1/7] nfs/localio: make trace_nfs_local_open_fh more useful Mike Snitzer
2025-09-15 15:41 ` [PATCH v9 2/7] nfs/localio: avoid issuing misaligned IO using O_DIRECT Mike Snitzer
2025-09-15 15:41 ` [PATCH v9 3/7] nfs/localio: refactor iocb and iov_iter_bvec initialization Mike Snitzer
2025-09-15 15:41 ` [PATCH v9 4/7] nfs/localio: refactor iocb initialization further Mike Snitzer
2025-09-15 15:41 ` SYNCFrom cb702c86aa12e5477e1e4aca0c1384a821f2afef Mon Sep 17 00:00:00 2001 Mike Snitzer
2025-09-15 15:47 ` [PATCH v9 5/7] nfs/localio: add proper O_DIRECT support for READ and WRITE Mike Snitzer
2025-09-15 15:41 ` [PATCH v9 6/7] nfs/localio: add tracepoints for misaligned DIO READ and WRITE support Mike Snitzer
2025-09-15 15:41 ` [PATCH v9 7/7] NFS: add basic STATX_DIOALIGN and STATX_DIO_READ_ALIGN support Mike Snitzer
[not found] ` <aMiMpYAcHV8bYU4W@kernel.org>
[not found] ` <aNLfroQ8Ti1Vh5wh@kernel.org>
[not found] ` <aNQqUprZ3DuJhMe4@kernel.org>
[not found] ` <aNgSOM9EzMS_Q6bR@kernel.org>
2025-09-30 16:26 ` [GIT PULL] NFS LOCALIO O_DIRECT changes for Linux 6.18 Mike Snitzer
2025-09-30 17:15 ` Chuck Lever
2025-09-30 17:35 ` Mike Snitzer
2025-09-30 17:59 ` Chuck Lever
2025-09-30 19:32 ` [GIT PULL v2] " Mike Snitzer
2025-09-30 20:53 ` Anna Schumaker
2025-09-30 21:30 ` Mike Snitzer [this message]
2025-10-01 16:04 ` Mike Snitzer
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=aNxL88GmEzJ5hsHl@kernel.org \
--to=snitzer@kernel.org \
--cc=anna.schumaker@oracle.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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 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.