From: 'Greg KH' <gregkh@linuxfoundation.org>
To: Bilge Aydin <b.aydin@samsung.com>
Cc: stable@vger.kernel.org
Subject: Re: [APS-24624] Missing patch in K5.15 against kernel panic
Date: Tue, 10 Dec 2024 15:01:54 +0100 [thread overview]
Message-ID: <2024121015-lettuce-lyrics-5dee@gregkh> (raw)
In-Reply-To: <0be801db4b0a$3fda7840$bf8f68c0$@samsung.com>
On Tue, Dec 10, 2024 at 02:48:52PM +0100, Bilge Aydin wrote:
> Hello Greg,
>
> Thank you very much for your prompt reply.
>
> "So why do you feel it is required in 5.15.y?"
> --> We have faced the issue in our K5.15 based platform. Our technical team has made an investigation and found your given patch. Afterwards we verified it by running a stress test. The result was positive and we did not face the kernel panic again.
That's great, then send us a backported patch (and the fix for that, you
did catch that one, right?)
> Since we are not OS experts, we fully respect Linux community's decisions. That's why we do not see ourselves in that high position to give any guidance and share any patch with you. During our investigation, we only recognized that the given patch was already integrated into the Android common kernel. Outgoing from that, I just want to share the indication with you.
>
> Would it be possible for you to start an internal communication within the Linux community for the synchronization of the K5.15 and K6.1 mainlines explicitly for iommu driver?
That is not how the stable kernel branches work at all, sorry. Please
read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for more information.
Also, if you need the iommu code in 6.1, then just use the 6.1.y kernel
please. There's nothing keeping you from doing that, right? That way
you get more support for more hardware and more fixes that didn't happen
to get backported to the really old 5.15.y release. Also, you will have
to move off of 5.15.y in a few years anyway, so might as well do it now
when you have a very good reason to do so.
good luck!
greg k-h
next prev parent reply other threads:[~2024-12-10 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241210132338eucas1p2228b89f17ab46f90075c07806765a5aa@eucas1p2.samsung.com>
2024-12-10 13:23 ` [APS-24624] Missing patch in K5.15 against kernel panic Bilge Aydin
2024-12-10 13:33 ` Greg KH
2024-12-10 13:48 ` Bilge Aydin
2024-12-10 14:01 ` 'Greg KH' [this message]
2024-12-10 13:34 ` 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=2024121015-lettuce-lyrics-5dee@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=b.aydin@samsung.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox