From: Rao Shoaib <rao.shoaib@oracle.com>
To: Kuniyuki Iwashima <kuniyu@amazon.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Kuniyuki Iwashima <kuni1840@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net 1/2] af_unix: Call manage_oob() for every skb in unix_stream_read_generic().
Date: Sun, 14 Apr 2024 19:26:10 -0700 [thread overview]
Message-ID: <acd7dda5-0e80-4bda-b484-55515aac8fd8@oracle.com> (raw)
In-Reply-To: <20240410171016.7621-2-kuniyu@amazon.com>
On 4/10/24 10:10, Kuniyuki Iwashima wrote:
> When we call recv() for AF_UNIX socket, we first peek one skb and
> calls manage_oob() to check if the skb is sent with MSG_OOB.
>
> However, when we fetch the next (and the following) skb, manage_oob()
> is not called now, leading a wrong behaviour.
>
> Let's say a socket send()s "hello" with MSG_OOB and the peer tries
> to recv() 5 bytes with MSG_PEEK. Here, we should get only "hell"
> without 'o', but actually not:
>
> >>> from socket import *
> >>> c1, c2 = socketpair(AF_UNIX, SOCK_STREAM)
> >>> c1.send(b'hello', MSG_OOB)
> 5
> >>> c2.recv(5, MSG_PEEK)
> b'hello'
>
> The first skb fills 4 bytes, and the next skb is peeked but not
> properly checked by manage_oob().
>
> Let's move up the again label to call manage_oob() for evry skb.
>
> With this patch:
>
> >>> from socket import *
> >>> c1, c2 = socketpair(AF_UNIX, SOCK_STREAM)
> >>> c1.send(b'hello', MSG_OOB)
> 5
> >>> c2.recv(5, MSG_PEEK)
> b'hell'
>
> Fixes: 314001f0bf92 ("af_unix: Add OOB support")
> Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
> ---
> net/unix/af_unix.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
> index d032eb5fa6df..f297320438bf 100644
> --- a/net/unix/af_unix.c
> +++ b/net/unix/af_unix.c
> @@ -2741,6 +2741,7 @@ static int unix_stream_read_generic(struct unix_stream_read_state *state,
> last = skb = skb_peek(&sk->sk_receive_queue);
> last_len = last ? last->len : 0;
>
> +again:
> #if IS_ENABLED(CONFIG_AF_UNIX_OOB)
> if (skb) {
> skb = manage_oob(skb, sk, flags, copied);
> @@ -2752,7 +2753,6 @@ static int unix_stream_read_generic(struct unix_stream_read_state *state,
> }
> }
> #endif
> -again:
> if (skb == NULL) {
> if (copied >= target)
> goto unlock;
Looks Good.
Reviewed-by: Rao shoaib <rao.shoaib@oracle.com>
Shoaib
next prev parent reply other threads:[~2024-04-15 2:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 17:10 [PATCH v2 net 0/2] af_unix: Fix MSG_OOB bugs with MSG_PEEK Kuniyuki Iwashima
2024-04-10 17:10 ` [PATCH v2 net 1/2] af_unix: Call manage_oob() for every skb in unix_stream_read_generic() Kuniyuki Iwashima
2024-04-15 2:26 ` Rao Shoaib [this message]
2024-04-10 17:10 ` [PATCH v2 net 2/2] af_unix: Don't peek OOB data without MSG_OOB Kuniyuki Iwashima
2024-04-16 20:11 ` Rao Shoaib
2024-04-16 20:51 ` Kuniyuki Iwashima
2024-04-16 21:34 ` Rao Shoaib
2024-04-16 21:47 ` Kuniyuki Iwashima
2024-04-16 22:01 ` Rao Shoaib
2024-04-16 22:10 ` Kuniyuki Iwashima
2024-04-17 4:37 ` Rao Shoaib
2024-04-13 2:10 ` [PATCH v2 net 0/2] af_unix: Fix MSG_OOB bugs with MSG_PEEK 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=acd7dda5-0e80-4bda-b484-55515aac8fd8@oracle.com \
--to=rao.shoaib@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).