* backport of dma_virt_ops related fixes to 5.10.y kernels
@ 2021-02-19 9:55 Krishnamraju Eraparaju
2021-02-19 10:39 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Krishnamraju Eraparaju @ 2021-02-19 9:55 UTC (permalink / raw)
To: sashal, gregkh, stable
Cc: Bernard Metzler, Christoph Hellwig, bharat, krishna2
Hi All,
Below commits needs to be backported to 5.10.y kernels to avoid NULL
pointer deref panic(while trying to access 'numa_node' from NULL
'dma_device'), @ Line:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/nvme/host/rdma.c?h=v5.10.17#n863)
commit:22dd4c707673129ed17e803b4bf68a567b2731db
commit:8ecfca68dc4cbee1272a0161e3f2fb9387dc6930
The panic is observed at nvme host(provider/transport being SoftiWARP),
while perfroming "nvme discover".
Hence, please backport the below patch series to '5.10.y' kernel.
"https://lore.kernel.org/linux-iommu/20201106181941.1878556-1-hch@lst.de/"
Thanks,
Krishnamraju.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: backport of dma_virt_ops related fixes to 5.10.y kernels
2021-02-19 9:55 backport of dma_virt_ops related fixes to 5.10.y kernels Krishnamraju Eraparaju
@ 2021-02-19 10:39 ` Greg KH
2021-02-19 18:38 ` Krishnamraju Eraparaju
0 siblings, 1 reply; 4+ messages in thread
From: Greg KH @ 2021-02-19 10:39 UTC (permalink / raw)
To: Krishnamraju Eraparaju
Cc: sashal, stable, Bernard Metzler, Christoph Hellwig, bharat
On Fri, Feb 19, 2021 at 03:25:12PM +0530, Krishnamraju Eraparaju wrote:
> Hi All,
>
> Below commits needs to be backported to 5.10.y kernels to avoid NULL
> pointer deref panic(while trying to access 'numa_node' from NULL
> 'dma_device'), @ Line:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/nvme/host/rdma.c?h=v5.10.17#n863)
>
> commit:22dd4c707673129ed17e803b4bf68a567b2731db
> commit:8ecfca68dc4cbee1272a0161e3f2fb9387dc6930
So just these 2 commits? In which order?
> The panic is observed at nvme host(provider/transport being SoftiWARP),
> while perfroming "nvme discover".
>
> Hence, please backport the below patch series to '5.10.y' kernel.
> "https://lore.kernel.org/linux-iommu/20201106181941.1878556-1-hch@lst.de/"
What are the git commit ids of these patches in Linus's tree and have
you tested them to ensure that they work? Why this 10 patch series and
not the 2 above? Or is this a different request?
confused,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: backport of dma_virt_ops related fixes to 5.10.y kernels
2021-02-19 10:39 ` Greg KH
@ 2021-02-19 18:38 ` Krishnamraju Eraparaju
2021-02-24 8:17 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Krishnamraju Eraparaju @ 2021-02-19 18:38 UTC (permalink / raw)
To: Greg KH; +Cc: sashal, stable, Bernard Metzler, Christoph Hellwig, bharat
On Friday, February 02/19/21, 2021 at 11:39:04 +0100, Greg KH wrote:
> On Fri, Feb 19, 2021 at 03:25:12PM +0530, Krishnamraju Eraparaju wrote:
> > Hi All,
> >
> > Below commits needs to be backported to 5.10.y kernels to avoid NULL
> > pointer deref panic(while trying to access 'numa_node' from NULL
> > 'dma_device'), @ Line:
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/nvme/host/rdma.c?h=v5.10.17#n863)
> >
> > commit:22dd4c707673129ed17e803b4bf68a567b2731db
> > commit:8ecfca68dc4cbee1272a0161e3f2fb9387dc6930
>
> So just these 2 commits? In which order?
>
> > The panic is observed at nvme host(provider/transport being SoftiWARP),
> > while perfroming "nvme discover".
> >
> > Hence, please backport the below patch series to '5.10.y' kernel.
> > "https://lore.kernel.org/linux-iommu/20201106181941.1878556-1-hch@lst.de/"
>
> What are the git commit ids of these patches in Linus's tree and have
> you tested them to ensure that they work? Why this 10 patch series and
> not the 2 above? Or is this a different request?
>
> confused,
Hi Greg,
Sorry for the confusion, I didn't know that I can request for the
backport of selected patches in a patch series.
As I don't have much background & testing feasability of other patches,
I request you to backport only below two patches(same order as below):
commit#1:8ecfca68dc4cbee1272a0161e3f2fb9387dc6930
RDMA: Lift ibdev_to_node from rds to common code
author: Christoph Hellwig <hch@lst.de>
commit#2:22dd4c707673129ed17e803b4bf68a567b2731db
nvme-rdma: Use ibdev_to_node instead of dereferencing ->dma_device
author: Christoph Hellwig <hch@lst.de>
And I belive these two patches has no dependency with other patches in
the series. I've tested, it's working fine.
Thanks,
Krishnamraju.
>
> greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: backport of dma_virt_ops related fixes to 5.10.y kernels
2021-02-19 18:38 ` Krishnamraju Eraparaju
@ 2021-02-24 8:17 ` Greg KH
0 siblings, 0 replies; 4+ messages in thread
From: Greg KH @ 2021-02-24 8:17 UTC (permalink / raw)
To: Krishnamraju Eraparaju
Cc: sashal, stable, Bernard Metzler, Christoph Hellwig, bharat
On Sat, Feb 20, 2021 at 12:08:25AM +0530, Krishnamraju Eraparaju wrote:
> On Friday, February 02/19/21, 2021 at 11:39:04 +0100, Greg KH wrote:
> > On Fri, Feb 19, 2021 at 03:25:12PM +0530, Krishnamraju Eraparaju wrote:
> > > Hi All,
> > >
> > > Below commits needs to be backported to 5.10.y kernels to avoid NULL
> > > pointer deref panic(while trying to access 'numa_node' from NULL
> > > 'dma_device'), @ Line:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/nvme/host/rdma.c?h=v5.10.17#n863)
> > >
> > > commit:22dd4c707673129ed17e803b4bf68a567b2731db
> > > commit:8ecfca68dc4cbee1272a0161e3f2fb9387dc6930
> >
> > So just these 2 commits? In which order?
> >
> > > The panic is observed at nvme host(provider/transport being SoftiWARP),
> > > while perfroming "nvme discover".
> > >
> > > Hence, please backport the below patch series to '5.10.y' kernel.
> > > "https://lore.kernel.org/linux-iommu/20201106181941.1878556-1-hch@lst.de/"
> >
> > What are the git commit ids of these patches in Linus's tree and have
> > you tested them to ensure that they work? Why this 10 patch series and
> > not the 2 above? Or is this a different request?
> >
> > confused,
> Hi Greg,
>
> Sorry for the confusion, I didn't know that I can request for the
> backport of selected patches in a patch series.
> As I don't have much background & testing feasability of other patches,
> I request you to backport only below two patches(same order as below):
>
> commit#1:8ecfca68dc4cbee1272a0161e3f2fb9387dc6930
> RDMA: Lift ibdev_to_node from rds to common code
> author: Christoph Hellwig <hch@lst.de>
>
> commit#2:22dd4c707673129ed17e803b4bf68a567b2731db
> nvme-rdma: Use ibdev_to_node instead of dereferencing ->dma_device
> author: Christoph Hellwig <hch@lst.de>
>
> And I belive these two patches has no dependency with other patches in
> the series. I've tested, it's working fine.
Now queued up, thanks.
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-02-24 8:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-19 9:55 backport of dma_virt_ops related fixes to 5.10.y kernels Krishnamraju Eraparaju
2021-02-19 10:39 ` Greg KH
2021-02-19 18:38 ` Krishnamraju Eraparaju
2021-02-24 8:17 ` Greg KH
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.