public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: dhowells@redhat.com, netdev@vger.kernel.org,
	syzbot+13a08c0bf4d212766c3c@syzkaller.appspotmail.com,
	syzbot+14234ccf6d0ef629ec1a@syzkaller.appspotmail.com,
	syzbot+4e2e47f32607d0f72d43@syzkaller.appspotmail.com,
	syzbot+472626bb5e7c59fb768f@syzkaller.appspotmail.com,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Jens Axboe <axboe@kernel.dk>,
	Matthew Wilcox <willy@infradead.org>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] crypto: af_alg/hash: Fix recvmsg() after sendmsg(MSG_MORE)
Date: Tue, 20 Jun 2023 09:31:56 +0100	[thread overview]
Message-ID: <1226381.1687249916@warthog.procyon.org.uk> (raw)
In-Reply-To: <ZJFhX3RYknrkcN0x@gondor.apana.org.au>

Herbert Xu <herbert@gondor.apana.org.au> wrote:

> > However, given you want sendmsg() to do the init->digest cycle on zero length
> > data, I think we should revert to the previous version of the patch that makes
> > a pass of the loop even with no data.
> 
> Let's get this fixed ASAP and we can refine it later.
> 
> Acked-by: Herbert Xu <herbert@gondor.apana.org.au>

Um.  Is that against this patch or the old version?

David


  reply	other threads:[~2023-06-20  8:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 11:10 [PATCH net-next v2] crypto: af_alg/hash: Fix recvmsg() after sendmsg(MSG_MORE) David Howells
2023-06-20  4:51 ` Herbert Xu
2023-06-20  7:42   ` David Howells
2023-06-20  8:20     ` Herbert Xu
2023-06-20  8:31       ` David Howells [this message]
2023-06-20  8:34         ` Herbert Xu
2023-06-20 19:20 ` patchwork-bot+netdevbpf

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=1226381.1687249916@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+13a08c0bf4d212766c3c@syzkaller.appspotmail.com \
    --cc=syzbot+14234ccf6d0ef629ec1a@syzkaller.appspotmail.com \
    --cc=syzbot+472626bb5e7c59fb768f@syzkaller.appspotmail.com \
    --cc=syzbot+4e2e47f32607d0f72d43@syzkaller.appspotmail.com \
    --cc=willy@infradead.org \
    /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