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 14:33:18 +0100 [thread overview]
Message-ID: <2024121044-coronary-slacker-cf53@gregkh> (raw)
In-Reply-To: <0bd701db4b06$b7cbdf00$27639d00$@samsung.com>
On Tue, Dec 10, 2024 at 02:23:35PM +0100, Bilge Aydin wrote:
> Dear Linux community,
>
> I am leading a project at Samsung where we utilized your kernel 5.15 in our system. Recently we faced an important kernel panic issue whose fix must be following patch:
> https://lore.kernel.org/all/1946ef9f774851732eed78760a78ec40dbc6d178.1667591503.git.robin.murphy@arm.com/
>
> The problem for us is that this patch must be available from kernel 6.1 onwards.
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/iommu/iommu.c?h=v6.1.119
> Clear to us is that it is not integrated into K5.15 yet: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/iommu/iommu.c?h=v5.15.173
>
> On the other side we can see that this patch was already applied to Android Common Kernel android13-5.15 https://android-review.googlesource.com/q/I51dbcdc5dc536b0e69c6187b2d7ac6a2031a305b. In particular, we can see the same implementation in the recent ACK release https://android.googlesource.com/kernel/common/+/refs/tags/android13-5.15-2024-11_r2/drivers/iommu/iommu.c given on https://source.android.com/docs/core/architecture/kernel/gki-android13-5_15-release-builds
>
> Do you have any plan to adjust your implementation in drivers/iommu/iommu.c in K5.15 as present in K6.1? If not, since the issue in our project is very critical for us, may I ask you kindly to trigger the sync of K5.15 and K6.1 soon?
If you wish for a commit to be backported to the stable kernels, just
ask us, and better yet, provide a working patch to do so.
The reason we did NOT backport this specific commit is that it is marked
as a fix for a commit that shows up in the 6.1 release, so why would it
be applicable to 5.15.y at all? So why do you feel it is required in
5.15.y? (Note, we have no idea why it's in an Android kernel tree,
perhaps they have the offending commit in there as well so the backport
is required? Have you checked?)
If you need or want it applied to older kernels, please send us a
working patch and we will be glad to take it.
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-10 13:33 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 [this message]
2024-12-10 13:48 ` Bilge Aydin
2024-12-10 14:01 ` 'Greg KH'
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=2024121044-coronary-slacker-cf53@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