From: Greg KH <gregkh@linuxfoundation.org>
To: Ben Hutchings <benh@debian.org>
Cc: stable@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 5.4,5.10 2/2] udf: Fix use of check_add_overflow() with mixed type arguments
Date: Mon, 10 Mar 2025 17:29:08 +0100 [thread overview]
Message-ID: <2025031054-kiwi-snowdrift-678b@gregkh> (raw)
In-Reply-To: <29f96d04ceac67563df0b4b17fb8a887dff3eb04.camel@debian.org>
On Mon, Feb 24, 2025 at 11:28:22PM +0100, Ben Hutchings wrote:
> On Mon, 2025-02-24 at 17:00 +0100, Ben Hutchings wrote:
> > Commit ebbe26fd54a9 "udf: Avoid excessive partition lengths"
> > introduced a use of check_add_overflow() with argument types u32,
> > size_t, and u32 *.
> >
> > This was backported to the 5.x stable branches, where in 64-bit
> > configurations it results in a build error (with older compilers) or a
> > warning. Before commit d219d2a9a92e "overflow: Allow mixed type
> > arguments", which went into Linux 6.1, mixed type arguments are not
> > supported. That cannot be backported to 5.4 or 5.10 as it would raise
> > the minimum compiler version for these kernel versions.
> [....]
>
> And for 5.15, I think it should be safe to backport commit
> d219d2a9a92e. Otherwise this patch should be applied to fix the
> warning there.
I'll take either, whch do you want us to do?
thanks,
greg k-h
next prev parent reply other threads:[~2025-03-10 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 15:57 [PATCH 5.4,4.10 1/2] perf cs-etm: Add missing variable in cs_etm__process_queues() Ben Hutchings
2025-02-24 16:00 ` [PATCH 5.4,5.10 2/2] udf: Fix use of check_add_overflow() with mixed type arguments Ben Hutchings
2025-02-24 22:28 ` Ben Hutchings
2025-03-10 16:29 ` Greg KH [this message]
2025-03-11 17:00 ` Ben Hutchings
2025-03-13 15:42 ` Greg KH
2025-02-25 16:13 ` Sasha Levin
2025-02-25 16:13 ` [PATCH 5.4,4.10 1/2] perf cs-etm: Add missing variable in cs_etm__process_queues() Sasha Levin
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=2025031054-kiwi-snowdrift-678b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=benh@debian.org \
--cc=jack@suse.cz \
--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