linux-kernel - Re: net-next/master bisection: boot on beaglebone-black

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20191122.101147.1112820693050959325.davem@davemloft.net>
Date:   Fri, 22 Nov 2019 10:11:47 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     guillaume.tucker@...labora.com
Cc:     hulkci@...wei.com, tomeu.vizoso@...labora.com, broonie@...nel.org,
        khilman@...libre.com, mgalka@...labora.com,
        enric.balletbo@...labora.com, yuehaibing@...wei.com,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        andrew@...n.ch, f.fainelli@...il.com, hkallweit1@...il.com
Subject: Re: net-next/master bisection: boot on beaglebone-black

From: Guillaume Tucker <guillaume.tucker@...labora.com>
Date: Fri, 22 Nov 2019 18:02:06 +0000

> As far as I can tell, it's the first time someone replies to say
> this issue is already fixed.  Sorry if I've missed an email.

I saw the first one and just ignored it hoping that since I had
the fix in 'net' these emails would simply stop.

> Also, it's apparently not fixed in the net-next tree which
> explains why it was reported again.  I guess we need to disable
> bisections in net-next until it gets rebased and includes the
> fix, and add a way to mark issues fixed somewhere else in
> KernelCI to avoid this situation in the future.

If you're not combining the net and the net-next tree, as Stephen
Rothwell's tree is doing, then you're going to run into this problem
every single day and spam us with these messages.

What is being done right now doesn't work.  You can't just wait for
net integration into net-next, that doesn't cut it.