From: Jason Gunthorpe <jgg@nvidia.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Yishai Hadas <yishaih@nvidia.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-mm@kvack.org, axboe@kernel.dk, hch@lst.de,
alex.williamson@redhat.com, leonro@nvidia.com, maorg@nvidia.com
Subject: Re: [PATCH] lib/scatterlist: Fix to merge contiguous pages into the last SG properly
Date: Thu, 5 Jan 2023 16:25:47 -0400 [thread overview]
Message-ID: <Y7cySyZKh+R49/BO@nvidia.com> (raw)
In-Reply-To: <81470f28-2bcf-b3cc-4824-6e45343dbd77@deltatee.com>
On Thu, Jan 05, 2023 at 01:23:52PM -0700, Logan Gunthorpe wrote:
>
>
> On 2023-01-05 13:06, Jason Gunthorpe wrote:
> > On Thu, Jan 05, 2023 at 01:23:39PM +0200, Yishai Hadas wrote:
> >> When sg_alloc_append_table_from_pages() calls to pages_are_mergeable()
> >> in its 'sgt_append->prv' flow to check whether it can merge contiguous
> >> pages into the last SG, it passes the page arguments in the wrong order.
> >>
> >> The first parameter should be the next candidate page to be merged to
> >> the last page and not the opposite.
> >>
> >> The current code leads to a corrupted SG which resulted in OOPs and
> >> unexpected errors when non-contiguous pages are merged wrongly.
> >>
> >> Fix to pass the page parameters in the right order.
> >>
> >> Fixes: 1567b49d1a40 ("lib/scatterlist: add check when merging zone device pages")
> >> Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
> >> ---
> >> lib/scatterlist.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > rdma is pretty much the only user of this API and this bug is causing
> > bad data corruption, so I'm going to take it to the rdma tree and send
> > it tomorrow.
> >
> > Which raises the question why the original patch was done at all,
> > nothing ever inputs pgmap pages into this function?
>
> It was done solely because you had suggested it was necessary.
>
> https://lore.kernel.org/all/20210929224653.GZ964074@nvidia.com/
Yes, but that was when I was expecting this would work with
FOLL_LONGTERM and PUP..
Jason
prev parent reply other threads:[~2023-01-05 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 11:23 Yishai Hadas
2023-01-05 13:36 ` Jason Gunthorpe
2023-01-05 16:48 ` Yishai Hadas
2023-01-05 20:06 ` Jason Gunthorpe
2023-01-05 20:21 ` Keith Busch
2023-01-05 20:23 ` Jason Gunthorpe
2023-01-05 20:23 ` Logan Gunthorpe
2023-01-05 20:25 ` Jason Gunthorpe [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=Y7cySyZKh+R49/BO@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=leonro@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=maorg@nvidia.com \
--cc=yishaih@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox