From: Jason Gunthorpe <jgg@ziepe.ca>
To: Nikhil V <quic_nprakash@quicinc.com>
Cc: Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
Charan Teja Kalla <quic_charante@quicinc.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu: Avoid races around default domain allocations
Date: Wed, 7 Feb 2024 10:56:56 -0400 [thread overview]
Message-ID: <20240207145656.GJ31743@ziepe.ca> (raw)
In-Reply-To: <9ba9c4fa-3fa9-c6c4-ce77-0c6cd5e23680@quicinc.com>
On Wed, Feb 07, 2024 at 07:56:25PM +0530, Nikhil V wrote:
>
>
> On 2/1/2024 9:53 PM, Jason Gunthorpe wrote:
> > On Mon, Jan 29, 2024 at 01:29:12PM +0530, Nikhil V wrote:
> >
> > > Gentle ping to have your valuable feedback. This fix is helping us
> > > downstream without which we see a bunch of kernel crashes.
> >
> > What are you expecting here? This was fixed in Linus's tree some time
> > ago now
> >
> > Are you asking for the stable team to put something weird in 6.1? I
> > don't think they generally do that?
> >
> > Jason
>
>
> Hi @Jason,
>
> Considering that the issue is reported on 6.1, which is an __LTS kernel__,
> any suggestion to fix this issue cleanly would help us a lot. Right thing
> here would have been propagating the changes from 6.6 (like for any
> stability issue), but considering the intrusiveness of them, is it even
> possible?
>
> Just to be open about reproducibility of the issue, a bunch of them are
> reported, both internally and by customers.
I think you need to talk to the stable maintainers not the iommu
upstream folks. I don't well know their policy.
Frankly, I'd suggest just proposing the necessary (and tested)
upstream patches to 6.1, however large they are, and see what Greg and
Sasha say. This is the usual working model they have, as I understand
it.
Jason
next prev parent reply other threads:[~2024-02-07 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 10:11 [PATCH 1/1] iommu: Avoid races around default domain allocations Nikhil V
2024-01-29 7:59 ` Nikhil V
2024-02-01 16:23 ` Jason Gunthorpe
2024-02-07 14:26 ` Nikhil V
2024-02-07 14:56 ` Jason Gunthorpe [this message]
2024-02-08 0:04 ` Robin Murphy
2024-02-08 1:13 ` Jason Gunthorpe
2024-02-08 1:37 ` Robin Murphy
2024-02-08 15:17 ` Nikhil V
2024-02-08 16:09 ` Jason Gunthorpe
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=20240207145656.GJ31743@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_charante@quicinc.com \
--cc=quic_nprakash@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox