From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org, Yi Zhang <yi.zhang@redhat.com>
Subject: Re: [PATCH] block: make sure that bvec length can't be overflowed
Date: Wed, 17 Apr 2019 08:48:43 +0800 [thread overview]
Message-ID: <20190417004842.GA12001@ming.t460p> (raw)
In-Reply-To: <9d0f5255-c37a-1830-7632-6f4d7158b21b@kernel.dk>
On Tue, Apr 16, 2019 at 11:03:00AM -0600, Jens Axboe wrote:
> On 4/16/19 10:46 AM, Christoph Hellwig wrote:
> > s/overflowed/overflow/ in the subject.
> >
> > Otherwise this looks good to me:
> >
> > Reviewed-by: Christoph Hellwig <hch@lst.de>
> >
> > Although this will create yet another conflict between Linus' tree
> > and the 5.2 block tree.
> >
> > Although maybe Jens still reset the tree and move the merge past this..
>
> That was my main worry too... But I'll probably just deal with it and
> redo the merge, I don't want to do two, and I don't want to have to
> deal with answering for why we get repeated conflicts in this area.
This one is a fix which should affect on loop and nvme-loop only in theory.
That is typical conflict between fix and feature(improvement).
Anyway, sorry for the a bit late fix.
>
> For the patch, I do generally prefer doing an AND with PAGE_MASK
> rather than a modulo with PAGE_SIZE. I know the compiler will take
> care of it, but still, it's more prudent imho.
OK, do it in V2.
Thanks,
Ming
next prev parent reply other threads:[~2019-04-17 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 15:38 [PATCH] block: make sure that bvec length can't be overflowed Ming Lei
2019-04-16 16:46 ` Christoph Hellwig
2019-04-16 17:03 ` Jens Axboe
2019-04-17 0:48 ` Ming Lei [this message]
2019-04-17 11:52 ` Hannes Reinecke
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=20190417004842.GA12001@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=yi.zhang@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.