From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <rao.shoaib@oracle.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<kuniyu@amazon.com>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>
Subject: Re: [PATCH net v3] af_unix: Read with MSG_PEEK loops if the first unread byte is OOB
Date: Tue, 23 Apr 2024 17:15:43 -0700 [thread overview]
Message-ID: <20240424001543.7843-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20240422092503.1014699-1-Rao.Shoaib@oracle.com>
From: Rao Shoaib <Rao.Shoaib@oracle.com>
Date: Mon, 22 Apr 2024 02:25:03 -0700
> Read with MSG_PEEK flag loops if the first byte to read is an OOB byte.
> commit 22dd70eb2c3d ("af_unix: Don't peek OOB data without MSG_OOB.")
> addresses the loop issue but does not address the issue that no data
> beyond OOB byte can be read.
>
> >>> from socket import *
> >>> c1, c2 = socketpair(AF_UNIX, SOCK_STREAM)
> >>> c1.send(b'a', MSG_OOB)
> 1
> >>> c1.send(b'b')
> 1
> >>> c2.recv(1, MSG_PEEK | MSG_DONTWAIT)
> b'b'
>
> Fixes: 314001f0bf92 ("af_unix: Add OOB support")
> Signed-off-by: Rao Shoaib <Rao.Shoaib@oracle.com>
> ---
> net/unix/af_unix.c | 26 ++++++++++++++------------
> 1 file changed, 14 insertions(+), 12 deletions(-)
>
> diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
> index 9a6ad5974dff..ed5f70735435 100644
> --- a/net/unix/af_unix.c
> +++ b/net/unix/af_unix.c
> @@ -2658,19 +2658,19 @@ static struct sk_buff *manage_oob(struct sk_buff *skb, struct sock *sk,
> if (skb == u->oob_skb) {
> if (copied) {
> skb = NULL;
> - } else if (sock_flag(sk, SOCK_URGINLINE)) {
> - if (!(flags & MSG_PEEK)) {
> + } else if (!(flags & MSG_PEEK)) {
> + if (sock_flag(sk, SOCK_URGINLINE)) {
> WRITE_ONCE(u->oob_skb, NULL);
> consume_skb(skb);
> + } else {
> + skb_unlink(skb, &sk->sk_receive_queue);
> + WRITE_ONCE(u->oob_skb, NULL);
> + if (!WARN_ON_ONCE(skb_unref(skb)))
> + kfree_skb(skb);
> + skb = skb_peek(&sk->sk_receive_queue);
I added a comment about this case.
> }
> - } else if (flags & MSG_PEEK) {
> - skb = NULL;
> - } else {
> - skb_unlink(skb, &sk->sk_receive_queue);
> - WRITE_ONCE(u->oob_skb, NULL);
> - if (!WARN_ON_ONCE(skb_unref(skb)))
> - kfree_skb(skb);
> - skb = skb_peek(&sk->sk_receive_queue);
> + } else if (!sock_flag(sk, SOCK_URGINLINE)) {
> + skb = skb_peek_next(skb, &sk->sk_receive_queue);
> }
> }
> }
> @@ -2747,9 +2747,11 @@ static int unix_stream_read_generic(struct unix_stream_read_state *state,
> #if IS_ENABLED(CONFIG_AF_UNIX_OOB)
> if (skb) {
> skb = manage_oob(skb, sk, flags, copied);
> - if (!skb && copied) {
> + if (!skb) {
> unix_state_unlock(sk);
> - break;
> + if (copied || (flags & MSG_PEEK))
> + break;
> + goto redo;
Here, copied == 0 && !(flags & MSG_PEEK) && skb == NULL, so it means
skb_peek(&sk->sk_receive_queue) above returned NULL. Then, we need
not jump to the redo label, where we call the same skb_peek().
Instead, we can just fall through the if (!skb) clause below.
Thanks!
> }
> }
> #endif
> --
> 2.39.3
next prev parent reply other threads:[~2024-04-24 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 9:25 [PATCH net v3] af_unix: Read with MSG_PEEK loops if the first unread byte is OOB Rao Shoaib
2024-04-24 0:15 ` Kuniyuki Iwashima [this message]
2024-04-24 1:18 ` Rao Shoaib
2024-04-24 1:39 ` Kuniyuki Iwashima
2024-04-30 8:26 ` Rao Shoaib
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=20240424001543.7843-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rao.shoaib@oracle.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;
as well as URLs for NNTP newsgroup(s).