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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260203032350.3221-1-kohei@enjuk.jp>
Date: Tue,  3 Feb 2026 03:23:35 +0000
From: Kohei Enju <kohei@...uk.jp>
To: jacob.e.keller@...el.com
Cc: aleksander.lobakin@...el.com, aleksandr.loktionov@...el.com,
        andrew+netdev@...n.ch, anthony.l.nguyen@...el.com, davem@...emloft.net,
        edumazet@...gle.com, intel-wired-lan@...ts.osuosl.org,
        kohei.enju@...il.com, kohei@...uk.jp, kuba@...nel.org,
        netdev@...r.kernel.org, pabeni@...hat.com,
        przemyslaw.kitszel@...el.com
Subject: Re: [PATCH v1 iwl-next] ice: fix NULL pointer dereference when

On Mon, 2 Feb 2026 16:31:39 -0800, Jacob Keller wrote:

> > I see the Fixes: commit exists in only tnguy/next-queue.git, so I'm
> > sending this patch to iwl-next, not iwl-net.
> > 
> > Also IIUC dev-queue in tnguy/next-queue.git is rebased continuously, so
> > the commit hash will be stale soon, and I don't know how to handle this.
> > 
> 
> Yea. Including the full subject line should be sufficient for Tony to 
> find this.

I see :)

> 
> > I'd appreciate it if iwl-folks know the way to handle it. Thanks!
> 
> Ideally we can squash this in with the implementation patches and 
> include your Co-developed-by and Signed-off-by tags if you would agree 
> to that?

That sounds good, and I agree to do so.
If I need to take some actions, please let me know.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ