All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krishnamraju Eraparaju <krishna2@chelsio.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: sashal@kernel.org, stable@vger.kernel.org,
	Bernard Metzler <bmt@zurich.ibm.com>,
	Christoph Hellwig <hch@lst.de>,
	bharat@chelsio.com
Subject: Re: backport of dma_virt_ops related fixes to 5.10.y kernels
Date: Sat, 20 Feb 2021 00:08:25 +0530	[thread overview]
Message-ID: <20210219183823.GA26562@chelsio.com> (raw)
In-Reply-To: <YC+VSJEzXdWdYITx@kroah.com>

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

  reply	other threads:[~2021-02-19 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2021-02-24  8:17     ` Greg KH

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=20210219183823.GA26562@chelsio.com \
    --to=krishna2@chelsio.com \
    --cc=bharat@chelsio.com \
    --cc=bmt@zurich.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=sashal@kernel.org \
    --cc=stable@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 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.