From: "Luís Ferreira" <contact@lsferreira.net>
To: Iain Buclaw <ibuclaw@gdcproject.org>,
Eric Gallager <egall@gwmail.gwu.edu>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] libiberty: prevent buffer overflow when decoding user input
Date: Fri, 08 Oct 2021 18:08:52 +0100 [thread overview]
Message-ID: <4872af878d0c7c20e22cce802ad19f0258ce9716.camel@lsferreira.net> (raw)
In-Reply-To: <1633711888.gc0v938ufz.astroid@galago.none>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
On Fri, 2021-10-08 at 18:52 +0200, Iain Buclaw wrote:
> Excerpts from Luís Ferreira's message of October 7, 2021 8:29 pm:
> > On Tue, 2021-10-05 at 21:49 -0400, Eric Gallager wrote:
> > >
> > > I can help with the autotools part if you can say how precisely
> > > you'd
> > > like to use them to add address sanitization. And as for the OSS
> > > fuzz part, I think someone tried setting up auto-fuzzing for it
> > > once,
> > > but the main bottleneck was getting the bug reports that it
> > > generated
> > > properly triaged, so if you could make sure the bug-submitting
> > > portion
> > > of the process is properly streamlined, that'd probably go a long
> > > way
> > > towards helping it be useful.
> >
> > Bugs are normally reported by email or mailing list. Is there any
> > writable mailing list to publish bugs or is it strictly needed to
> > open
> > an entry on bugzilla?
> >
>
> Please open an issue on bugzilla, fixes towards it can then be
> referenced in the commit message/patch posted here.
>
> Iain.
You mean for this current issue? The discussion was about future bug
reports reported by the OSS fuzzer workers. I can also open an issue on
the bugzilla for this issue, please clarify it and let me know :)
--
Sincerely,
Luís Ferreira @ lsferreira.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-08 17:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 1:10 Luís Ferreira
2021-09-23 10:16 ` ibuclaw
2021-09-23 15:40 ` Luís Ferreira
2021-09-23 15:50 ` Jeff Law
2021-10-04 16:52 ` Luís Ferreira
2021-10-05 15:00 ` Jeff Law
2021-10-05 17:26 ` Luís Ferreira
2021-10-06 1:49 ` Eric Gallager
2021-10-07 18:29 ` Luís Ferreira
2021-10-08 16:52 ` Iain Buclaw
2021-10-08 17:08 ` Luís Ferreira [this message]
2021-10-08 20:11 ` Iain Buclaw
2021-10-12 12:54 ` Luís Ferreira
2021-10-12 19:40 ` Eric Gallager
2021-10-12 20:25 ` Luís Ferreira
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=4872af878d0c7c20e22cce802ad19f0258ce9716.camel@lsferreira.net \
--to=contact@lsferreira.net \
--cc=egall@gwmail.gwu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=ibuclaw@gdcproject.org \
--cc=jeffreyalaw@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).