From: Jules Maselbas <jmaselbas@kalray.eu>
To: Sascha Hauer <sha@pengutronix.de>
Cc: Neeraj Pal <neerajpal09@gmail.com>, barebox@lists.infradead.org
Subject: Re: [BUG] Out of bound read of size 1 in __d_alloc function which further leads to __default_memcpy function
Date: Tue, 11 May 2021 10:52:27 +0200 [thread overview]
Message-ID: <20210511085227.GB20010@tellis.lin.mbt.kalray.eu> (raw)
In-Reply-To: <20210511080003.GF19819@pengutronix.de>
On Tue, May 11, 2021 at 10:00:03AM +0200, Sascha Hauer wrote:
> On Mon, May 10, 2021 at 12:18:08PM +0200, Jules Maselbas wrote:
>
> Indeed I can confirm that 74946415a already fixes the issue, also with a
> 'nfs foo ""' command. This renders my patches unnecessary for this
> issue, but still I think they do the right thing, so I tend to keep
> them.
Agreed
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2021-05-11 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 19:40 Neeraj Pal
2021-05-07 10:58 ` Sascha Hauer
2021-05-10 10:18 ` Jules Maselbas
2021-05-11 8:00 ` Sascha Hauer
2021-05-11 8:52 ` Jules Maselbas [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=20210511085227.GB20010@tellis.lin.mbt.kalray.eu \
--to=jmaselbas@kalray.eu \
--cc=barebox@lists.infradead.org \
--cc=neerajpal09@gmail.com \
--cc=sha@pengutronix.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