netdev - Re: [Intel-wired-lan] [REGRESSION] e1000e probe/link detection fails since 6.2 kernel

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]

Date:   Thu, 30 Mar 2023 12:35:21 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Sasha Neftin <sasha.neftin@...el.com>,
        Bagas Sanjaya <bagasdotme@...il.com>,
        Paul Menzel <pmenzel@...gen.mpg.de>,
        Jesse Brandeburg <jesse.brandeburg@...el.com>,
        Tony Nguyen <anthony.l.nguyen@...el.com>,
        netdev@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
        regressions@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [Intel-wired-lan] [REGRESSION] e1000e probe/link detection fails since 6.2 kernel

On Thu, 30 Mar 2023 08:30:17 +0200,
Takashi Iwai wrote:
> 
> On Wed, 29 Mar 2023 21:12:32 +0200,
> Jakub Kicinski wrote:
> > 
> > On Wed, 29 Mar 2023 10:48:36 +0200 Takashi Iwai wrote:
> > > On Wed, 29 Mar 2023 10:40:44 +0200,
> > > Bagas Sanjaya wrote:
> > > > 
> > > > On Tue, Mar 28, 2023 at 04:39:01PM +0200, Paul Menzel wrote:  
> > > > > Does openSUSE Tumbleweed make it easy to bisect the regression at least on
> > > > > “rc level”? It be great if narrow it more down, so we know it for example
> > > > > regressed in 6.2-rc7.
> > > > >   
> > > > 
> > > > Alternatively, can you do bisection using kernel sources from Linus's
> > > > tree (git required)?  
> > > 
> > > That'll be a last resort, if no one has idea at all :)
> > 
> > I had a quick look yesterday, there's only ~6 or so commits to e1000e.
> > Should be a fairly quick bisection, hopefully?
> 
> *IFF* it's an e1000e-specific bug, right?
> 
> Through a quick glance, the only significant change in e1000e is the
> commit 1060707e3809
>     ptp: introduce helpers to adjust by scaled parts per million
> 
> Others are only for MTP/ADP and new devices, which must be irrelevant.
> The tracing must be irrelevant, and the kmap change must be OK.
> 
> Can 1060707e3809 be the cause of such a bug?

The bug reporter updated the entry and informed that this can be
false-positive; the problem could be triggered with the older kernel
out of sudden.  So he closed the bug as WORKSFORME.

#regzbot invalid: Problems likely not in kernel changes


thanks,

Takashi