From: Eric Biggers <ebiggers3@gmail.com>
To: Tom Herbert <tom@herbertland.com>
Cc: Tom Herbert <tom@quantonium.net>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH net] kcm: lock lower socket in kcm_attach
Date: Mon, 12 Mar 2018 14:33:56 -0700 [thread overview]
Message-ID: <20180312213356.GD230165@gmail.com> (raw)
In-Reply-To: <CALx6S35TJ44b1UM=OqqwfDMFrXFjDJj==shW6Z_8zM3VH9v6WA@mail.gmail.com>
On Mon, Mar 12, 2018 at 02:25:41PM -0700, Tom Herbert wrote:
> On Mon, Mar 12, 2018 at 2:09 PM, Eric Biggers <ebiggers3@gmail.com> wrote:
> > On Mon, Mar 12, 2018 at 02:04:12PM -0700, Tom Herbert wrote:
> >> Need to lock lower socket in order to provide mutual exclusion
> >> with kcm_unattach.
> >>
> >> Fixes: ab7ac4eb9832e32a09f4e804 ("kcm: Kernel Connection Multiplexor module")
> >> Signed-off-by: Tom Herbert <tom@quantonium.net>
> >> ---
> >
> > Is this fixing the syzbot-reported bug "KASAN: use-after-free Read in
> > get_work_pool"? If so, please add:
> >
> > Reported-by: syzbot+ea75c0ffcd353d32515f064aaebefc5279e6161e@syzkaller.appspotmail.com
>
> Yeah, I was looking for a "reported by". I didn't see it in the email
> from syzbot. Where is this found?
>
> Thanks,
> Tom
This was an old bug report that was sent out before syzbot was updated to
suggest a Reported-by line. But you can still use Reported-by for these old
bugs. I took the bug ID from the From: header of the email.
Eric
prev parent reply other threads:[~2018-03-12 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 21:04 [PATCH net] kcm: lock lower socket in kcm_attach Tom Herbert
2018-03-12 21:09 ` Eric Biggers
2018-03-12 21:25 ` Tom Herbert
2018-03-12 21:33 ` Eric Biggers [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=20180312213356.GD230165@gmail.com \
--to=ebiggers3@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.com \
--cc=tom@quantonium.net \
/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.