public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "da… via monorail" <monorail+v2.1355924921@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 45705 in oss-fuzz: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_next_arhdr_wrlock
Date: Mon, 21 Mar 2022 08:06:47 -0700	[thread overview]
Message-ID: <0000000000005cbcb105dabbd8f9@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=6e9de1dd49fc7876f5a4e7fd9d8a79b0=oss-fuzz@monorail-prod.appspotmail.com>


Comment #4 on issue 45705 by da...@adalogics.com: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_next_arhdr_wrlock
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c4

Yes -- I did this because I asked in an internal email with Mark if it would be appreciated (the answer was yet). But will stop this as you're taking care of it by way of the mailing list.

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.

  parent reply	other threads:[~2022-03-21 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=6e9de1dd49fc7876f5a4e7fd9d8a79b0=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-18  6:56 ` ClusterFuzz-External via monorail
2022-03-20 10:05 ` da… via monorail
2022-03-20 10:06 ` da… via monorail
2022-03-21  4:54 ` evv… via monorail
2022-03-21 15:06 ` da… via monorail [this message]
2022-03-21 15:49 ` evv… via monorail
2022-03-22 14:23 ` ClusterFuzz-External via monorail

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=0000000000005cbcb105dabbd8f9@google.com \
    --to=monorail+v2.1355924921@chromium.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=oss-fuzz@monorail-prod.appspotmail.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).