From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: Eryu Guan <eguan@redhat.com>, Brian Foster <bfoster@redhat.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/3] xfs: Fix off-by-in in loop termination in xfs_find_get_desired_pgoff()
Date: Tue, 23 May 2017 08:30:18 -0700 [thread overview]
Message-ID: <20170523153018.GP4519@birch.djwong.org> (raw)
In-Reply-To: <20170523085044.GA1119@quack2.suse.cz>
On Tue, May 23, 2017 at 10:50:44AM +0200, Jan Kara wrote:
> On Tue 23-05-17 11:21:23, Eryu Guan wrote:
> > On Mon, May 22, 2017 at 01:50:47PM -0400, Brian Foster wrote:
> > > On Thu, May 18, 2017 at 12:48:49PM +0200, Jan Kara wrote:
> > > > There is an off-by-one error in loop termination conditions in
> > > > xfs_find_get_desired_pgoff() since 'end' may index a page beyond end of
> > > > desired range if 'endoff' is page aligned. It doesn't have any visible
> > > > effects but still it is good to fix it.
> > > >
> > > > Signed-off-by: Jan Kara <jack@suse.cz>
> > > > ---
> > > > fs/xfs/xfs_file.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
> > > > index f371812e20c6..3714b5736fd3 100644
> > > > --- a/fs/xfs/xfs_file.c
> > > > +++ b/fs/xfs/xfs_file.c
> > > > @@ -1043,7 +1043,7 @@ xfs_find_get_desired_pgoff(
> > > >
> > > > index = startoff >> PAGE_SHIFT;
> > > > endoff = XFS_FSB_TO_B(mp, map->br_startoff + map->br_blockcount);
> > > > - end = endoff >> PAGE_SHIFT;
> > > > + end = (endoff - 1) >> PAGE_SHIFT;
> > >
> > > Hmm.. I think this messes with the want count for the pagevec_lookup().
> > > E.g.:
> > >
> > > # xfs_io -fc "truncate 0" -c "falloc 0 16k" -c "pwrite 0 16k" -c "seek -h 0" /mnt/file
> > > wrote 16384/16384 bytes at offset 0
> > > 16 KiB, 4 ops; 0.0000 sec (200.321 MiB/sec and 51282.0513 ops/sec)
> > > Whence Result
> > > HOLE 12288
> >
> > I think the root cause is that the calculation for 'want' is wrong, it
> > has an off-by-one bug too. I sent a patch[1] to fix it, with my patch
> > applied on top of Jan's patchset, your test case passed (report HOLE at
> > 16k). Can you please take a look if it's a correct fix? Thanks!
>
> Yes, I've messed that up. It is a bug introduced by my series as Brian
> properly noticed. Thanks guys for noticing and fixing it! Darrick, should I
> fold in Eryu's fix and send v4 of the series or will you just pick up
> Eryu's fix?
FWIW it looked like a separate problem to me as well. It appears to me
that I could merge Eryu's patch immediately prior to Jan's series; is
that ok with everyone?
--D
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-23 15:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 10:48 [PATCH 0/3 v3] xfs: Fix SEEK_HOLE implementation Jan Kara
2017-05-18 10:48 ` [PATCH 1/3] xfs: Fix missed holes in " Jan Kara
2017-05-22 17:50 ` Brian Foster
2017-05-18 10:48 ` [PATCH 2/3] xfs: Fix off-by-in in loop termination in xfs_find_get_desired_pgoff() Jan Kara
2017-05-22 17:50 ` Brian Foster
2017-05-23 3:21 ` Eryu Guan
2017-05-23 8:50 ` Jan Kara
2017-05-23 11:08 ` Eryu Guan
2017-05-23 12:17 ` Brian Foster
2017-05-23 13:05 ` Eryu Guan
2017-05-23 17:37 ` Darrick J. Wong
2017-05-23 15:30 ` Darrick J. Wong [this message]
2017-05-23 16:00 ` Brian Foster
2017-05-18 10:48 ` [PATCH 3/3] xfs: Move handling of missing page into one place " Jan Kara
2017-05-22 17:50 ` Brian Foster
2017-05-19 0:06 ` [PATCH 0/3 v3] xfs: Fix SEEK_HOLE implementation Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2017-05-17 12:10 [PATCH 0/3 v2] " Jan Kara
2017-05-17 12:10 ` [PATCH 2/3] xfs: Fix off-by-in in loop termination in xfs_find_get_desired_pgoff() Jan Kara
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=20170523153018.GP4519@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.com \
--cc=eguan@redhat.com \
--cc=jack@suse.cz \
--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).