All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@sigma-star.at>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Jixiong.Hu@mediatek.com, sjg@chromium.org,
	patrick.delaunay@foss.st.com, ilias.apalodimas@linaro.org,
	seanga2@gmail.com, trini@konsulko.com,
	upstream+uboot@sigma-star.at, u-boot@lists.denx.de,
	upstream@sigma-star.at, Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH 1/2] ext4: Fix integer overflow in ext4fs_read_symlink()
Date: Fri, 12 Jul 2024 13:26:35 +0200	[thread overview]
Message-ID: <3325697.VqM8IeB0Os@somecomputer> (raw)
In-Reply-To: <59ebc379-66f7-493a-b024-fcc3224b320c@gmx.de>

Am Freitag, 12. Juli 2024, 13:19:32 CEST schrieb Heinrich Schuchardt:
> > Hm, I see man built-ins in the U-Boot source.
> > Why is this one special?
> 
> See the definition of COMPILER_HAS_GENERIC_BUILTIN_OVERFLOW in
> include/linux/compiler-clang.h.

So I can't use __builtin_add_overflow() because
u-boot is still supporting outdated compilers that don't offer __builtin_add_overflow()?

Maybe this is the ideal moment to raise the bar?
__builtin_add_overflow() is supported by gcc >= 5.1 and clang >= 8.

Thanks,
//richard

-- 
​​​​​sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT
UID/VAT Nr: ATU 66964118 | FN: 374287y



  reply	other threads:[~2024-07-12 11:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 19:42 [PATCH 1/2] ext4: Fix integer overflow in ext4fs_read_symlink() Richard Weinberger
2024-07-02 19:42 ` [PATCH 2/2] ext4: Fix zalloc() Richard Weinberger
2024-07-11 15:45   ` Tom Rini
2024-07-12  7:59     ` Richard Weinberger
2024-07-12 11:15   ` Heinrich Schuchardt
2024-07-12 11:29     ` Richard Weinberger
2024-07-12 11:10 ` [PATCH 1/2] ext4: Fix integer overflow in ext4fs_read_symlink() Heinrich Schuchardt
2024-07-12 11:14   ` Richard Weinberger
2024-07-12 11:19     ` Heinrich Schuchardt
2024-07-12 11:26       ` Richard Weinberger [this message]
2024-07-12 16:54         ` Tom Rini

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=3325697.VqM8IeB0Os@somecomputer \
    --to=richard@sigma-star.at \
    --cc=Jixiong.Hu@mediatek.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=patrick.delaunay@foss.st.com \
    --cc=richard@nod.at \
    --cc=seanga2@gmail.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=upstream+uboot@sigma-star.at \
    --cc=upstream@sigma-star.at \
    --cc=xypron.glpk@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.