public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: syzbot <syzbot+24ebd650e20bd263ca01@syzkaller.appspotmail.com>,
	davem@davemloft.net, johan.hedberg@gmail.com, kuba@kernel.org,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	marcel@holtmann.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in hci_le_meta_evt
Date: Mon, 3 Aug 2020 10:58:32 -0700	[thread overview]
Message-ID: <20200803175832.GB1644292@gmail.com> (raw)
In-Reply-To: <20200803173223.GS1551@shell.armlinux.org.uk>

On Mon, Aug 03, 2020 at 06:32:24PM +0100, Russell King - ARM Linux admin wrote:
> On Mon, Aug 03, 2020 at 10:21:04AM -0700, Eric Biggers wrote:
> > On Mon, Aug 03, 2020 at 06:12:33PM +0100, Russell King - ARM Linux admin wrote:
> > > Dear syzbot,
> > > 
> > > Please explain why you are spamming me with all these reports - four so
> > > far.  I don't understand why you think I should be doing anything with
> > > these.
> > > 
> > > Thanks.
> > 
> > syzbot just uses get_maintainer.pl.
> > 
> > $ ./scripts/get_maintainer.pl net/bluetooth/hci_event.c
> > Marcel Holtmann <marcel@holtmann.org> (maintainer:BLUETOOTH SUBSYSTEM)
> > Johan Hedberg <johan.hedberg@gmail.com> (maintainer:BLUETOOTH SUBSYSTEM)
> > "David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING [GENERAL])
> > Jakub Kicinski <kuba@kernel.org> (maintainer:NETWORKING [GENERAL])
> > Russell King <linux@armlinux.org.uk> (maintainer:SFF/SFP/SFP+ MODULE SUPPORT)
> > linux-bluetooth@vger.kernel.org (open list:BLUETOOTH SUBSYSTEM)
> > netdev@vger.kernel.org (open list:NETWORKING [GENERAL])
> > linux-kernel@vger.kernel.org (open list)
> 
> Ah, and, because the file mentions "phylink" (although it makes no use
> of the phylink code), get_maintainer spits out my address. Great.
> 
> So how do I get get_maintainer to identify patches that are making use
> of phylink, but avoid this bluetooth code... (that's not a question.)
> 

I think "K: " (content regex) in MAINTAINERS is best avoided.  This isn't the
first time that someone has volunteered to maintain all files containing $foo,
then complained when they receive emails for those files as they requested...

If you do really want to use it, can you use a more specific regex?  E.g. a
regex that matches "#include <linux/phylink.h>" or some specific function(s)?

- Eric

      reply	other threads:[~2020-08-03 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 15:05 KASAN: slab-out-of-bounds Read in hci_le_meta_evt syzbot
2020-08-03 17:12 ` Russell King - ARM Linux admin
2020-08-03 17:21   ` Eric Biggers
2020-08-03 17:32     ` Russell King - ARM Linux admin
2020-08-03 17:58       ` 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=20200803175832.GB1644292@gmail.com \
    --to=ebiggers@kernel.org \
    --cc=davem@davemloft.net \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+24ebd650e20bd263ca01@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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