From: Matthew Wilcox <willy@infradead.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH] iomap: Fix writepage tracepoint pgoff
Date: Wed, 4 Mar 2020 07:34:00 -0800 [thread overview]
Message-ID: <20200304153400.GG29971@bombadil.infradead.org> (raw)
In-Reply-To: <20200304152515.GA23148@infradead.org>
On Wed, Mar 04, 2020 at 07:25:15AM -0800, Christoph Hellwig wrote:
> On Wed, Mar 04, 2020 at 06:22:59AM -0800, Matthew Wilcox wrote:
> > From: Matthew Wilcox (Oracle) <willy@infradead.org>
> >
> > page_offset() confusingly returns the number of bytes from the
> > beginning of the file and not the pgoff, which the tracepoint claims
> > to be returning. We're already returning the number of bytes from the
> > beginning of the file in the 'offset' parameter, so correct the pgoff
> > to be what was apparently intended.
> >
> > Fixes: 0b1b213fcf3a ("xfs: event tracing support")
> > Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
>
> I wonder if tracing the byte offset and just changing the name
> might be more useful. But I agree that we should fix it one way or
> another.
I covered that -- "We're already returning the number of bytes from the
beginning of the file in the 'offset' parameter, so correct the pgoff
to be what was apparently intended."
I mean, we could just delete the pgoff instead. Apparently nobody's
using it, or they would surely have noticed.
next prev parent reply other threads:[~2020-03-04 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 14:22 [PATCH] iomap: Fix writepage tracepoint pgoff Matthew Wilcox
2020-03-04 15:25 ` Christoph Hellwig
2020-03-04 15:34 ` Matthew Wilcox [this message]
2020-03-04 15:36 ` Christoph Hellwig
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=20200304153400.GG29971@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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 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).