From: Michal Luczaj <mhal@rbox.co>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: bpf@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
jakub@cloudflare.com, john.fastabend@gmail.com, kuba@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net] af_unix: Disable MSG_OOB handling for sockets in sockmap/sockhash
Date: Sun, 23 Jun 2024 00:38:22 +0200 [thread overview]
Message-ID: <fda335cd-3fb1-4024-bff7-aedeb1d8710a@rbox.co> (raw)
In-Reply-To: <20240620221223.66096-1-kuniyu@amazon.com>
On 6/21/24 00:12, Kuniyuki Iwashima wrote:
> Sorry for not mentioning this before, but could you replace "net" with
> "bpf" in Subject and rebase the patch on bpf.git so that we can trigger
> the patchwork's CI ?
No problem, will do.
>> ...
>> static int unix_stream_read_skb(struct sock *sk, skb_read_actor_t recv_actor)
>> {
>> + struct unix_sock *u = unix_sk(sk);
>> + struct sk_buff *skb;
>> + int err;
>> +
>> if (unlikely(READ_ONCE(sk->sk_state) != TCP_ESTABLISHED))
>> return -ENOTCONN;
>>
>> - return unix_read_skb(sk, recv_actor);
>> + mutex_lock(&u->iolock);
>> + skb = skb_recv_datagram(sk, MSG_DONTWAIT, &err);
>
> mutex_unlock(&u->iolock);
>
> I think we can drop mutex here as the skb is already unlinked
> and no receiver can touch it.
I guess you're right about the mutex. That said, double mea culpa, lack of
state lock makes things racy:
unix_stream_read_skb
mutex_lock
skb = skb_recv_datagram
mutex_unlock
spin_lock
if (oob_skb == skb) {
unix_release_sock
if (u->oob_skb) {
kfree_skb(u->oob_skb)
u->oob_skb = NULL
}
oob_skb = NULL
drop = true
}
spin_unlock
if (drop) {
skb_unref(skb)
kfree_skb(skb)
}
In v2 I'll do what unix_stream_read_generic() does: take state lock and
check for SOCK_DEAD.
> and the below part can be like the following not to slow down
> the common case:
>
> if (!skb)
> return err;
>
>> +
>> +#if IS_ENABLED(CONFIG_AF_UNIX_OOB)
>> + if (skb) {
>
> if (unlikely(skb == READ_ONCE(u->oob_skb))) {
>
>
>> + bool drop = false;
>> +
>> + spin_lock(&sk->sk_receive_queue.lock);
>> + if (skb == u->oob_skb) {
>
> if (likely(skb == u->oob_skb)) {
>
>> + WRITE_ONCE(u->oob_skb, NULL);
>> + drop = true;
>> + }
>> + spin_unlock(&sk->sk_receive_queue.lock);
>> +
>> + if (drop) {
>> + WARN_ON_ONCE(skb_unref(skb));
>> + kfree_skb(skb);
>> + skb = NULL;
>> + err = -EAGAIN;
> return -EAGAIN;
>
>> + }
>> + }
>> +#endif
>
> return recv_actor(sk, skb);
All right, thanks. So here's v2:
https://lore.kernel.org/netdev/20240622223324.3337956-1-mhal@rbox.co/
prev parent reply other threads:[~2024-06-22 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 20:20 [PATCH net] af_unix: Disable MSG_OOB handling for sockets in sockmap/sockhash Michal Luczaj
2024-06-20 22:12 ` Kuniyuki Iwashima
2024-06-22 0:02 ` Jakub Kicinski
2024-06-22 22:38 ` Michal Luczaj [this message]
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=fda335cd-3fb1-4024-bff7-aedeb1d8710a@rbox.co \
--to=mhal@rbox.co \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--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).