From: Eryu Guan <eguan@redhat.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: fix off-by-one on max nr_pages in xfs_find_get_desired_pgoff()
Date: Tue, 23 May 2017 21:00:28 +0800 [thread overview]
Message-ID: <20170523130028.GA7250@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170523123536.GC6543@bfoster.bfoster>
On Tue, May 23, 2017 at 08:35:39AM -0400, Brian Foster wrote:
> On Sun, May 21, 2017 at 03:59:39PM +0800, Eryu Guan wrote:
> > xfs_find_get_desired_pgoff() is used to search for offset of hole or
> > data in page range [index, end] (both inclusive), and the max number
> > of pages to search should be at least one, if end == index.
> > Otherwise the only page is missed and no hole or data is found,
> > which is not correct.
> >
> > When block size is smaller than page size, this can be demonstrated
> > by preallocating a file with size smaller than page size and writing
> > data to the last block. E.g. run this xfs_io command on a 1k block
> > size XFS on x86_64 host.
> >
> > # xfs_io -fc "falloc 0 3k" -c "pwrite 2k 1k" \
> > -c "seek -d 0" /mnt/xfs/testfile
> > wrote 1024/1024 bytes at offset 2048
> > 1 KiB, 1 ops; 0.0000 sec (33.675 MiB/sec and 34482.7586 ops/sec)
> > Whence Result
> > DATA EOF
> >
>
> Ok, so this does look like a different problem.
>
> > Data at offset 2k was missed, and lseek(2) returned ENXIO.
> >
> > This is unconvered by generic/285 subtest 07 and 08 on ppc64 host,
> > where pagesize is 64k. Because a recent change to generic/285
> > reduced the preallocated file size to smaller than 64k.
> >
> > Cc: stable@vger.kernel.org # v3.7+
> > Signed-off-by: Eryu Guan <eguan@redhat.com>
>
> Could we fold this patch into Jan's patch 2 or vice versa (retaining
> Eryu's commit log and credit)?
>
> > ---
> > 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 35703a8..aefa213 100644
> > --- a/fs/xfs/xfs_file.c
> > +++ b/fs/xfs/xfs_file.c
> > @@ -1049,7 +1049,7 @@ xfs_find_get_desired_pgoff(
> > unsigned nr_pages;
> > unsigned int i;
> >
> > - want = min_t(pgoff_t, end - index, PAGEVEC_SIZE);
> > + want = min_t(pgoff_t, end - index, PAGEVEC_SIZE - 1) + 1;
>
> Kind of a nit, but could we do the following?
>
> want = min_t(pgoff_t, end - index + 1, PAGEVEC_SIZE);
>
> It seems more clear to me given that end would be inclusive after Jan's
> patch.
I thought about it too, but I searched for other places doing the same
calculation and they are all comparing (end-index) with (PAGEVEC_SIZE-1)
then plus one, e.g. mm/truncate.c::invalidate_inode_pages2_range(). I
guess it's meant to prevent (end - index + 1) from overflowing, i.e.
(end(ULONG_MAX) - index(0) + 1).
Thanks for the review!
Eryu
>
> Brian
>
> > nr_pages = pagevec_lookup(&pvec, inode->i_mapping, index,
> > want);
> > /*
> > --
> > 2.9.4
> >
> > --
> > 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 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 7:59 [PATCH] xfs: fix off-by-one on max nr_pages in xfs_find_get_desired_pgoff() Eryu Guan
2017-05-23 8:36 ` Jan Kara
2017-05-23 12:35 ` Brian Foster
2017-05-23 13:00 ` Eryu Guan [this message]
2017-05-23 13:27 ` Brian Foster
2017-05-23 15:33 ` Darrick J. Wong
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=20170523130028.GA7250@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=bfoster@redhat.com \
--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).