Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "Bilge Aydin" <b.aydin@samsung.com>
To: <stable@vger.kernel.org>
Subject: [APS-24624] Missing patch in K5.15 against kernel panic
Date: Tue, 10 Dec 2024 14:23:35 +0100	[thread overview]
Message-ID: <0bd701db4b06$b7cbdf00$27639d00$@samsung.com> (raw)
In-Reply-To: CGME20241210132338eucas1p2228b89f17ab46f90075c07806765a5aa@eucas1p2.samsung.com

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?

I would appreciate highly your response and any support.


Kind regards / Mit freundlichen Grüßen

-Confidential-
Bilge Aydin
Project Manager
Phone:: +49-89-45578-1055 · Mobile:: +49-160-8855875 · Email: b.aydin@samsung.com 
Samsung Semiconductor Europe GmbH
Einsteinstrasse 174, 81677 München, Deutschland
Jurisdiction and registered Munich / Germany, HRB Nr. 253778
Managing Director: Dermot Ryan

www.samsung.com/semiconductor/solutions/automotive




This communication (including any attachments) contains information which may be confidential and/or privileged. It is for the exclusive use of the intended recipient(s) so, if you have received this communication in error, please do not distribute, copy or use this communication or its contents but notify the sender immediately and then destroy any copies of it. Due to the nature of the Internet, the sender is unable to ensure the integrity of this message. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of the company the sender works for.

 





       reply	other threads:[~2024-12-10 13:23 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 ` Bilge Aydin [this message]
2024-12-10 13:33   ` [APS-24624] Missing patch in K5.15 against kernel panic Greg KH
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='0bd701db4b06$b7cbdf00$27639d00$@samsung.com' \
    --to=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