From: Dinh Nguyen <dinguyen@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: tony.luck@intel.com, linux-edac@vger.kernel.org,
rounakdas2025@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv5 0/4] EDAC/altera: Address sashiko reviews part 1(v5)
Date: Fri, 25 Sep 2026 10:00:33 -0500 [thread overview]
Message-ID: <48621819-9a03-4577-ac73-5cb186f8a9a7@kernel.org> (raw)
In-Reply-To: <20260925043821.GBarX6vdJ1WucqPuvN@fat_crate.local>
On 9/24/26 23:38, Borislav Petkov wrote:
> On Fri, Sep 11, 2026 at 07:06:23AM -0500, Dinh Nguyen wrote:
>> Dinh Nguyen (4):
>> EDAC/altera: Do not allow driver unbinding
>> EDAC/altera: Drop __init from ECC setup paths for re-probe safety
>> EDAC/altera: Fix code leak on dci allocation failure
>> EDAC/altera: Fix use-after-free in error paths
>
> All those are marked for stable backports but the last three are fixing error
> handling paths. Are they really that serious that you want to backport them
> everywhere? If so, which ones?
>
All patches should be applied to v6.18+. Would you like me to follow up
with a v6 that has the proper tag for v6.18+?
Dinh
prev parent reply other threads:[~2026-09-25 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 12:06 Dinh Nguyen
2026-09-11 12:06 ` [PATCHv5 1/4] EDAC/altera: Do not allow driver unbinding Dinh Nguyen
2026-09-11 12:06 ` [PATCHv5 2/4] EDAC/altera: Drop __init from ECC setup paths for re-probe safety Dinh Nguyen
2026-09-11 12:06 ` [PATCHv5 3/4] EDAC/altera: Fix code leak on dci allocation failure Dinh Nguyen
2026-09-11 12:06 ` [PATCHv5 4/4] EDAC/altera: Fix use-after-free in error paths Dinh Nguyen
2026-09-24 14:48 ` [PATCHv5 0/4] EDAC/altera: Address sashiko reviews part 1(v5) Dinh Nguyen
2026-09-25 4:32 ` Borislav Petkov
2026-09-25 4:38 ` Borislav Petkov
2026-09-25 15:00 ` Dinh Nguyen [this message]
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=48621819-9a03-4577-ac73-5cb186f8a9a7@kernel.org \
--to=dinguyen@kernel.org \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rounakdas2025@gmail.com \
--cc=tony.luck@intel.com \
/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
all inboxes | Powered by JetHome®