From: Bernard Metzler <BMT@zurich.ibm.com>
To: Pedro Falcato <pfalcato@suse.de>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Jakub Kicinski <kuba@kernel.org>,
David Howells <dhowells@redhat.com>, Tom Talpey <tom@talpey.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
kernel test robot <oliver.sang@intel.com>
Subject: RE: [PATCH] RDMA/siw: Fix the sendmsg byte count in siw_tcp_sendpages
Date: Wed, 23 Jul 2025 16:49:30 +0000 [thread overview]
Message-ID: <DS0SPRMB006759C349217E60D43F923B995FA@DS0SPRMB0067.namprd15.prod.outlook.com> (raw)
In-Reply-To: <nwtutmewgtziygnp7drmhdxpenrbxumrjprcz7ls2afwub5lwf@due2djp7llv5>
> -----Original Message-----
> From: Pedro Falcato <pfalcato@suse.de>
> Sent: Wednesday, 23 July 2025 17:49
> To: Bernard Metzler <BMT@zurich.ibm.com>
> Cc: Jason Gunthorpe <jgg@ziepe.ca>; Leon Romanovsky <leon@kernel.org>;
> Vlastimil Babka <vbabka@suse.cz>; Jakub Kicinski <kuba@kernel.org>; David
> Howells <dhowells@redhat.com>; Tom Talpey <tom@talpey.com>; linux-
> rdma@vger.kernel.org; linux-kernel@vger.kernel.org; linux-mm@kvack.org;
> stable@vger.kernel.org; kernel test robot <oliver.sang@intel.com>
> Subject: [EXTERNAL] Re: [PATCH] RDMA/siw: Fix the sendmsg byte count in
> siw_tcp_sendpages
>
> On Wed, Jul 23, 2025 at 02:52:12PM +0000, Bernard Metzler wrote:
> >
> >
> > > -----Original Message-----
> > > From: Pedro Falcato <pfalcato@suse.de>
> > > Sent: Wednesday, 23 July 2025 12:41
> > > To: Jason Gunthorpe <jgg@ziepe.ca>; Bernard Metzler
> <BMT@zurich.ibm.com>;
> > > Leon Romanovsky <leon@kernel.org>; Vlastimil Babka <vbabka@suse.cz>
> > > Cc: Jakub Kicinski <kuba@kernel.org>; David Howells
> <dhowells@redhat.com>;
> > > Tom Talpey <tom@talpey.com>; linux-rdma@vger.kernel.org; linux-
> > > kernel@vger.kernel.org; linux-mm@kvack.org; Pedro Falcato
> > > <pfalcato@suse.de>; stable@vger.kernel.org; kernel test robot
> > > <oliver.sang@intel.com>
> > [snip]
> > > ---
> > > drivers/infiniband/sw/siw/siw_qp_tx.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/infiniband/sw/siw/siw_qp_tx.c
> > > b/drivers/infiniband/sw/siw/siw_qp_tx.c
> > > index 3a08f57d2211..9576a2b766c4 100644
> > > --- a/drivers/infiniband/sw/siw/siw_qp_tx.c
> > > +++ b/drivers/infiniband/sw/siw/siw_qp_tx.c
> > > @@ -340,11 +340,11 @@ static int siw_tcp_sendpages(struct socket *s,
> struct
> > > page **page, int offset,
> > > if (!sendpage_ok(page[i]))
> > > msg.msg_flags &= ~MSG_SPLICE_PAGES;
> > > bvec_set_page(&bvec, page[i], bytes, offset);
> > > - iov_iter_bvec(&msg.msg_iter, ITER_SOURCE, &bvec, 1, size);
> > > + iov_iter_bvec(&msg.msg_iter, ITER_SOURCE, &bvec, 1, bytes);
> > >
> > > try_page_again:
> > > lock_sock(sk);
> > > - rv = tcp_sendmsg_locked(sk, &msg, size);
> > > + rv = tcp_sendmsg_locked(sk, &msg, bytes);
> > > release_sock(sk);
> > >
> >
> > Pedro, many thanks for catching this! I completely
> > missed it during my too sloppy review of that patch.
> > It's a serious bug which must be fixed asap.
> > BUT, looking closer, I do not see the offset being taken
> > into account when retrying a current segment. So,
> > resend attempts seem to send old data which are already
> > out. Shouldn't the try_page_again: label be above
> > bvec_set_page()??
>
> This was raised off-list by Vlastimil - I think it's harmless to bump (but
> not use)
> the offset here, because by reusing the iov_iter we progressively consume
> the data
> (it keeps its own size and offset tracking internally). So the only thing
> we
> need to track is the size we pass to tcp_sendmsg_locked[1].
>
Ah okay, I didn't know that. Are we sure? I am currently travelling and have
only limited possibilities to try out things. I just looked up other
use cases and found one in net/tls/tls_main.c#L197. Here the loop looks
very similar, but it works as I was suggesting (taking offset into account
and re-initializing new bvec in case of partial send).
> If desired (and if my logic is correct!) I can send a v2 deleting that bit.
>
So yes if that's all save, please. We shall not have dead code.
Thanks!
Bernard.
>
> [1] Assuming tcp_sendmsg_locked guarantees it will never consume something
> out
> of the iovec_iter without reporting it as bytes copied, which from a code
> reading
> it seems like it won't...
>
>
> --
> Pedro
next prev parent reply other threads:[~2025-07-23 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 10:41 Pedro Falcato
2025-07-23 14:52 ` Bernard Metzler
2025-07-23 15:49 ` Pedro Falcato
2025-07-23 16:49 ` Bernard Metzler [this message]
2025-07-25 16:09 ` Pedro Falcato
2025-07-28 11:34 ` Bernard Metzler
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=DS0SPRMB006759C349217E60D43F923B995FA@DS0SPRMB0067.namprd15.prod.outlook.com \
--to=bmt@zurich.ibm.com \
--cc=dhowells@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=pfalcato@suse.de \
--cc=stable@vger.kernel.org \
--cc=tom@talpey.com \
--cc=vbabka@suse.cz \
/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