lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 26 Mar 2019 09:27:04 +0100
From:   Dmitry Vyukov <>
To:     Ido Schimmel <>
Cc:     syzbot <>,
        "" <>,
        "" <>,
        "" <>,
        Jiri Pirko <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>
Subject: Re: WARNING in bpf_prog_kallsyms_add

On Mon, Mar 25, 2019 at 1:16 PM Ido Schimmel <> wrote:
> + Dmitry
> On Sat, Mar 23, 2019 at 07:16:01PM -0700, syzbot wrote:
> > syzbot has bisected this bug to:
> >
> > commit 7607dd35fc34893214284cca740d015154d20452
> > Author: Ido Schimmel <>
> > Date:   Mon Jul 17 12:15:30 2017 +0000
> >
> >     mlxsw: spectrum: Trap IPv4 packets with Router Alert option
> >
> > bisection log:
> > start commit:   645ff1e8 Merge branch 'for-linus' of git://
> > git tree:       upstream
> > final crash:
> > console output:
> > kernel config:
> > dashboard link:
> > syz repro:
> >
> > Reported-by:
> > Fixes: 7607dd35fc34 ("mlxsw: spectrum: Trap IPv4 packets with Router Alert
> > option")
> >
> > For information about bisection process see:
> Dmitry,
> The bisection is probably wrong. Above mentioned commit is specific to
> mlxsw which is not even present in the provided kernel config.
> I see that this also appears in the web interface [1] which might be
> misleading to some people. Might be worthwhile to add a command for
> syzbot that tells it that bisection is wrong?
> [1]

Hi Ido,

Do you mean for the purposes of showing the results as "wrong" on the dashboard?

Generally the idea is that people can leave any free form comments on
the email thread associated with the bug (there is always a link from
the dashboard back to the email thread).  It's not possible to capture
all possible situations in a set of fixed tags. All information on the
dashboard may be incorrect in interesting ways. For example, consider
bisection diverged at the very last steps, so one may check the
bisection log and easily identify the commit that is most likely the
root cause, but the official result is off-by-one. Or may the free
stack in a use-after-free report is incorrect and then somebody may
suggest the right stack.

But having said that there is a proposal for custom tags for bugs
(e.g. for priority, subsystem, etc):
And "bisection is wrong" may be a reasonable tag. I just don't want to
jump to a first ad-hoc implementation right now. I want to at least
try to thought out some consistent, extensible and useful design for
I will add a note about bisection there.
Another concern is that I suspect very few people will actually use
it. Most people seem to tend to just drop a comment like "this is
fixed" or "syzbot sucks" without actually caring about any formal bug
state tracking...
But even if nobody will use it for majority of bugs, somebody (me)
still needs to design, implement, write tests, carefully deploy and
maintain this thing...

But thanks for the proposal!

Powered by blists - more mailing lists