From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Afi0 <capyenglishlite@gmail.com>,
Sami Tolvanen <samitolvanen@google.com>
Cc: linux-modules@vger.kernel.org, mcgrof@kernel.org,
dmitry.torokhov@gmail.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] module: decompress: check return value of module_extend_max_pages()
Date: Wed, 20 May 2026 23:33:40 +0200 [thread overview]
Message-ID: <bb4daac1-ee1b-405d-a07a-4b951945d664@kernel.org> (raw)
In-Reply-To: <CAEABq7e5NT0c58gG=fqFK-RmfrgUDA-8jXnmMMQZHMNu4hea5Q@mail.gmail.com>
Le 20/05/2026 à 18:05, Afi0 a écrit :
> Thanks for the correction. Updated commit message
Please follow kernel rules:
- Mails in plain text, not Mime
- Patches as part of core text, no attachment
- Your real name, not Afi0 <capyenglishlite@gmail.com>
- No top-posting
See:
-
https://docs.kernel.org/process/submitting-patches.html#use-trimmed-interleaved-replies-in-email-discussions
-
https://docs.kernel.org/process/submitting-patches.html#no-mime-no-links-no-compression-no-attachments-just-plain-text
Christophe
>
> On Wed, May 20, 2026 at 3:13 PM Sami Tolvanen <samitolvanen@google.com
> <mailto:samitolvanen@google.com>> wrote:
>
> On Tue, May 19, 2026 at 9:11 PM Afi0 <capyenglishlite@gmail.com
> <mailto:capyenglishlite@gmail.com>> wrote:
> >
> > Hi,
> >
> > You are right, the commit message overstates the impact. The
> actual result is an immediate kernel oops, not an OOB write into
> adjacent slab objects. The fix is still correct - checking the
> return value avoids the oops. Shall I send a v3 with a corrected
> commit message?
>
> Yes, please send v3.
>
> Sami
>
next prev parent reply other threads:[~2026-05-20 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 14:32 [PATCH v2] module: decompress: check return value of module_extend_max_pages() Andrii Kuchmenko
2026-05-18 16:21 ` Christophe Leroy (CS GROUP)
2026-05-19 14:56 ` Christophe Leroy (CS GROUP)
2026-05-19 21:23 ` Sami Tolvanen
[not found] ` <CAEABq7f3agKZqrBiu+UwXHY44mTcK360ryg-i0w=wEc_Lv+T0A@mail.gmail.com>
2026-05-20 15:12 ` Sami Tolvanen
2026-05-20 16:05 ` Afi0
2026-05-20 21:33 ` Christophe Leroy (CS GROUP) [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-18 12:18 Andrii Kuchmenko
2026-05-18 12:57 ` 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=bb4daac1-ee1b-405d-a07a-4b951945d664@kernel.org \
--to=chleroy@kernel.org \
--cc=capyenglishlite@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=samitolvanen@google.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