From: Richard Weinberger <richard@sigma-star.at>
To: Richard Weinberger <richard@nod.at>, upstream@sigma-star.at
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,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH 2/2] ext4: Fix zalloc()
Date: Fri, 12 Jul 2024 13:29:14 +0200 [thread overview]
Message-ID: <15231895.JCcGWNJJiE@somecomputer> (raw)
In-Reply-To: <85482355-3c1d-49cd-9b43-ba031fbfc707@gmx.de>
Am Freitag, 12. Juli 2024, 13:15:56 CEST schrieb 'Heinrich Schuchardt' via upstream:
> Memalign() is called in many code locations.
>
> If memalign() has a bug, it needs to be fixed in memalign. We should not
> try to work around it in all callers.
Agreed, I did already:
See https://lists.denx.de/pipermail/u-boot/2024-July/558477.html
Thanks,
//richard
--
sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT
UID/VAT Nr: ATU 66964118 | FN: 374287y
next prev parent reply other threads:[~2024-07-12 11:29 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 [this message]
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
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=15231895.JCcGWNJJiE@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox