From: Gerd Bayer <gbayer@linux.ibm.com>
To: Niklas Schnelle <schnelle@linux.ibm.com>,
"David S.Miller" <davem@davemloft.net>
Cc: wintera@linux.ibm.com, twinkler@linux.ibm.com, hca@linux.ibm.com,
pabeni@redhat.com, hch@lst.de, pasic@linux.ibm.com,
wenjia@linux.ibm.com, guwen@linux.alibaba.com,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com
Subject: Re: [PATCH net v2] s390/ism: fix receive message buffer allocation
Date: Mon, 08 Apr 2024 21:05:47 +0200 [thread overview]
Message-ID: <7e6baff2338ef4c3af9073c46b5492f271bdd9ae.camel@linux.ibm.com> (raw)
In-Reply-To: <87cfb39893b0e38164e8f3014089c2bb5a79d63f.camel@linux.ibm.com>
On Mon, 2024-04-08 at 14:40 +0200, Niklas Schnelle wrote:
> On Mon, 2024-04-08 at 11:00 +0000, patchwork-bot+netdevbpf@kernel.org
> wrote:
> > Hello:
> >
> > This patch was applied to netdev/net.git (main)
> > by David S. Miller <davem@davemloft.net>:
> >
> > On Fri, 5 Apr 2024 13:16:06 +0200 you wrote:
> > > Since [1], dma_alloc_coherent() does not accept requests for
> > > GFP_COMP
> > > anymore, even on archs that may be able to fulfill this.
> > > Functionality that
> > > relied on the receive buffer being a compound page broke at that
> > > point:
> > > The SMC-D protocol, that utilizes the ism device driver, passes
> > > receive
> > > buffers to the splice processor in a struct splice_pipe_desc with
> > > a
> > > single entry list of struct pages. As the buffer is no longer a
> > > compound
> > > page, the splice processor now rejects requests to handle more
> > > than a
> > > page worth of data.
> > >
> > > [...]
> >
> > Here is the summary with links:
> > - [net,v2] s390/ism: fix receive message buffer allocation
> > https://git.kernel.org/netdev/net/c/58effa347653
> >
> > You are awesome, thank you!
>
> This version of the patch has an outstanding issue around handling
> allocation failure see the comments on v1 here[0]. Please drop. Gerd
> will send a v3 with that issue fixed.
>
> Thanks,
> Niklas
>
> [0] https://lore.kernel.org/all/20240405143641.GA5865@lst.de/
Hi Dave,
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.
Thanks,
Gerd
next prev parent reply other threads:[~2024-04-08 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 11:16 [PATCH net v2] s390/ism: fix receive message buffer allocation Gerd Bayer
2024-04-08 11:00 ` patchwork-bot+netdevbpf
2024-04-08 12:40 ` Niklas Schnelle
2024-04-08 19:05 ` Gerd Bayer [this message]
2024-04-08 19:46 ` Jakub Kicinski
2024-04-09 7:58 ` Gerd Bayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e6baff2338ef4c3af9073c46b5492f271bdd9ae.camel@linux.ibm.com \
--to=gbayer@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=gor@linux.ibm.com \
--cc=guwen@linux.alibaba.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=schnelle@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=twinkler@linux.ibm.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox