netdev - Re: Bug 216320 - KSZ8794 operation broken

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: <f1a68bf1-2fc3-48f9-520f-2343e20c9bfc@leemhuis.info>
Date:   Wed, 17 Aug 2022 19:12:37 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Vladimir Oltean <olteanv@...il.com>
Cc:     Michael Grzeschik <m.grzeschik@...gutronix.de>,
        Oleksij Rempel <o.rempel@...gutronix.de>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        LKML <linux-kernel@...r.kernel.org>,
        Florian Fainelli <f.fainelli@...il.com>,
        netdev <netdev@...r.kernel.org>, craig@...ueen.id.au,
        UNGLinuxDriver@...rochip.com,
        Arun Ramadoss <arun.ramadoss@...rochip.com>
Subject: Re: Bug 216320 - KSZ8794 operation broken

On 17.08.22 16:04, Vladimir Oltean wrote:
> On Wed, Aug 17, 2022 at 03:36:44PM +0200, Thorsten Leemhuis wrote:
>> I noticed a regression report in bugzilla.kernel.org that afaics nobody
>> acted upon since it was reported. That's why I decided to forward it by
>> mail to those that afaics should handle this.
> 
> Thanks. I don't track bugzilla,

No worries, that's not unusual (or I guess: pretty common).

> but I will respond to this ticket.
> Is there a way to get automatically notified of DSA related issues?

I assume in theory it would be possible to create a product for this
case in bugzilla.kernel.org and then you could directly (if you become
the default assignee) or indirectly (virtual user you could then could
start to watch) be notified.

In practice that is rarely done afaik.

My plan is to discuss bugzilla.kernel.org handling next month on
kernel/maintainers summit. Maybe we decide something there to improve
things. I'd say: wait for it and continue to no track bugzilla for now,
as https://docs.kernel.org/admin-guide/reporting-issues.html clearly
tells people to not file bugs there, unless MAINTAINERS tells them to
(which is not the case here afaik).

Ciao, Thorsten