netdev - Re: [PATCH net v2] s390/ism: fix receive message buffer allocation

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: <20240408124609.4ca811f2@kernel.org>
Date: Mon, 8 Apr 2024 12:46:09 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Gerd Bayer <gbayer@...ux.ibm.com>
Cc: Niklas Schnelle <schnelle@...ux.ibm.com>, "David S.Miller" 
 <davem@...emloft.net>, wintera@...ux.ibm.com, twinkler@...ux.ibm.com,
 hca@...ux.ibm.com, pabeni@...hat.com, hch@....de, pasic@...ux.ibm.com,
 wenjia@...ux.ibm.com, guwen@...ux.alibaba.com, linux-s390@...r.kernel.org,
 netdev@...r.kernel.org, gor@...ux.ibm.com, agordeev@...ux.ibm.com,
 borntraeger@...ux.ibm.com, svens@...ux.ibm.com
Subject: Re: [PATCH net v2] s390/ism: fix receive message buffer allocation

On Mon, 08 Apr 2024 21:05:47 +0200 Gerd Bayer wrote:
> Hi Dave,

Hi, from the Dave replacement service.

> so how do we go forward? Would you revert this v2 in the netdev tree to
> have my next v3 properly reviewed?
> 
> Second best option: I can send a fixup to address the last issue from
> [0], but that would still leave some pieces sent with (v1/v2) not
> properly R-by'd or at least ack'd.

If there's a chance we can get an incremental fix ready to merge by
Wednesday morning, let's try that. If we fail please post a revert by
Wednesday morning. On Thu morning EU time we'll ship the fixes to Linus,
so we gotta have the tree in a good share at that point.