From: Ming Lei <ming.lei@redhat.com>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] block: fix get_max_segment_size() overflow on 32bit arch
Date: Wed, 8 Jan 2020 10:38:22 +0800 [thread overview]
Message-ID: <20200108023822.GB28075@ming.t460p> (raw)
In-Reply-To: <BYAPR04MB581614236B3088415240723AE73E0@BYAPR04MB5816.namprd04.prod.outlook.com>
On Wed, Jan 08, 2020 at 02:06:25AM +0000, Damien Le Moal wrote:
> On 2020/01/08 10:25, Ming Lei wrote:
> > Commit 429120f3df2d starts to take account of segment's start dma address
> > when computing max segment size, and data type of 'unsigned long'
> > is used to do that. However, the segment mask may be 0xffffffff, so
> > the figured out segment size may be overflowed because DMA address can
> > be 64bit on 32bit arch.
> >
> > Fixes the issue by using 'unsigned long long' to compute max segment
> > size.
> >
> > Fixes: 429120f3df2d ("block: fix splitting segments on boundary masks")
> > Reported-by: Guenter Roeck <linux@roeck-us.net>
> > Tested-by: Guenter Roeck <linux@roeck-us.net>
> > Signed-off-by: Ming Lei <ming.lei@redhat.com>
> > ---
> > block/blk-merge.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/block/blk-merge.c b/block/blk-merge.c
> > index 347782a24a35..b0fcc72594cb 100644
> > --- a/block/blk-merge.c
> > +++ b/block/blk-merge.c
> > @@ -159,12 +159,12 @@ static inline unsigned get_max_io_size(struct request_queue *q,
> >
> > static inline unsigned get_max_segment_size(const struct request_queue *q,
> > struct page *start_page,
> > - unsigned long offset)
> > + unsigned long long offset)
> > {
> > unsigned long mask = queue_segment_boundary(q);
> >
> > offset = mask & (page_to_phys(start_page) + offset);
>
> Shouldn't mask be an unsigned long long too for this to give the
> expected correct result ?
queue_segment_boundary() always returns 'unsigned long', so far not
see issue related with that.
Thanks,
Ming
prev parent reply other threads:[~2020-01-08 2:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 1:25 [PATCH] block: fix get_max_segment_size() overflow on 32bit arch Ming Lei
2020-01-08 2:06 ` Damien Le Moal
2020-01-08 2:34 ` Jens Axboe
2020-01-08 2:38 ` Damien Le Moal
2020-01-08 2:47 ` Ming Lei
2020-01-08 2:59 ` Guenter Roeck
2020-01-08 3:02 ` Damien Le Moal
2020-01-08 2:38 ` Ming Lei [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=20200108023822.GB28075@ming.t460p \
--to=ming.lei@redhat.com \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux@roeck-us.net \
/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