From: Mike Snitzer <snitzer@kernel.org>
To: Anna Schumaker <anna@kernel.org>
Cc: Trond Myklebust <trondmy@kernel.org>, linux-nfs@vger.kernel.org
Subject: Re: NFS/localio: fix nfs_local_dio_misaligned tracepoint
Date: Wed, 12 Aug 2026 18:13:24 -0400 [thread overview]
Message-ID: <anzwBIacMU73oYn_@kernel.org> (raw)
In-Reply-To: <9a005347-837e-4a0b-b2a7-972f3cb59052@app.fastmail.com>
On Tue, Jul 21, 2026 at 09:56:33AM -0400, Anna Schumaker wrote:
> Hi Mike,
>
> On Wed, Jul 8, 2026, at 5:36 PM, Mike Snitzer wrote:
> > The intended focus of nfs_local_iters_setup_dio()'s call to
> > trace_nfs_local_dio_misaligned() is on the middle segment being
> > misaligned, yet the @offset passed in was local_dio->start_len.
> > It would appear this was a cut-n-paste bug from the preceding
> > nfs_local_iter_setup() call that passes local_dio->start_len.
> >
> > Fix this by passing the @offset as local_dio->middle_offset and
> > calculate the start segment's offset rather than assume.
> >
> > Example traces, before this fix:
> >
> > python3-32744 [006] .l... 132946.352360:
> > nfs_local_dio_write: fileid=00:33:1286 fhandle=0xf1f7c10b
> > offset=1048759 count=1048576 mem_align=4 offset_align=512
> > start=1048759+329 middle=1049088+1048064 end=2097152+183
> >
> > python3-32744 [006] .l... 132946.352360:
> > nfs_local_dio_misaligned: fileid=00:33:1286 fhandle=0xf1f7c10b
> > offset=329 count=1048064 mem_align=4 offset_align=512
> > start=329+329 middle=1049088+1048064 end=2097152+183
> >
> > After this fix:
> >
> > python3-32744 [006] .l... 132946.352360:
> > nfs_local_dio_write: fileid=00:33:1286 fhandle=0xf1f7c10b
> > offset=1048759 count=1048576 mem_align=4 offset_align=512
> > start=1048759+329 middle=1049088+1048064 end=2097152+183
> >
> > python3-32744 [006] .l... 132946.352360:
> > nfs_local_dio_misaligned: fileid=00:33:1286 fhandle=0xf1f7c10b
> > offset=1049088 count=1048064 mem_align=4 offset_align=512
> > start=1048759+329 middle=1049088+1048064 end=2097152+183
> >
> > Cc: stable@vger.kernel.org
>
> Do you have a fixes tag for this commit?
>
> Thanks,
> Anna
Sorry, I somehow missed this until now. Looks to be:
Fixes: 6a218b9c3183e ("nfs/localio: do not issue misaligned DIO out-of-order")
prev parent reply other threads:[~2026-08-12 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 21:36 [PATCH] NFS/localio: fix nfs_local_dio_misaligned tracepoint Mike Snitzer
2026-07-21 13:56 ` Anna Schumaker
2026-08-12 22:13 ` Mike Snitzer [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=anzwBIacMU73oYn_@kernel.org \
--to=snitzer@kernel.org \
--cc=anna@kernel.org \
--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