From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <mhal@rbox.co>
Cc: <billy@starlabs.sg>, <davem@davemloft.net>, <edumazet@google.com>,
<kuba@kernel.org>, <kuni1840@gmail.com>, <kuniyu@amazon.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>
Subject: Re: [PATCH v2 net] af_unix: Update unix_sk(sk)->oob_skb under sk_receive_queue lock.
Date: Mon, 13 May 2024 15:12:44 +0900 [thread overview]
Message-ID: <20240513061244.12229-1-kuniyu@amazon.com> (raw)
In-Reply-To: <5670c1c4-985d-4e87-9732-ad1cc59bc8db@rbox.co>
From: Michal Luczaj <mhal@rbox.co>
Date: Sun, 12 May 2024 16:47:11 +0200
> On 5/10/24 11:39, Kuniyuki Iwashima wrote:
> > @@ -2655,6 +2661,8 @@ static struct sk_buff *manage_oob(struct sk_buff *skb, struct sock *sk,
> > consume_skb(skb);
> > skb = NULL;
> > } else {
> > + spin_lock(&sk->sk_receive_queue.lock);
> > +
> > if (skb == u->oob_skb) {
> > if (copied) {
> > skb = NULL;
> > @@ -2666,13 +2674,15 @@ static struct sk_buff *manage_oob(struct sk_buff *skb, struct sock *sk,
> > } else if (flags & MSG_PEEK) {
> > skb = NULL;
> > } else {
> > - skb_unlink(skb, &sk->sk_receive_queue);
> > + __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);
> > }
> > }
> > +
> > + spin_unlock(&sk->sk_receive_queue.lock);
> > }
> > return skb;
> > }
>
> Now it is
>
> spin_lock(&sk->sk_receive_queue.lock)
> kfree_skb
This does not free skb actually and just drops a refcount by skb_get()
in queue_oob().
> unix_destruct_scm
So, here we don't reach unix_destruct_scm().
That's why I changed kfree_skb() to skb_unref() in __unix_gc().
Thanks!
> unix_notinflight
> spin_lock(&unix_gc_lock)
>
> I.e. sk_receive_queue.lock -> unix_gc_lock, inversion of what unix_gc() does.
> But that's benign, right?
next prev parent reply other threads:[~2024-05-13 6:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 9:39 [PATCH v2 net] af_unix: Update unix_sk(sk)->oob_skb under sk_receive_queue lock Kuniyuki Iwashima
2024-05-10 10:44 ` Paolo Abeni
2024-05-10 10:54 ` Kuniyuki Iwashima
2024-05-10 11:11 ` Paolo Abeni
2024-05-12 14:47 ` Michal Luczaj
2024-05-13 6:12 ` Kuniyuki Iwashima [this message]
2024-05-13 6:40 ` Michal Luczaj
2024-05-13 7:44 ` Kuniyuki Iwashima
2024-05-13 9:14 ` Michal Luczaj
2024-05-13 9:24 ` Kuniyuki Iwashima
2024-05-13 10:15 ` Michal Luczaj
2024-05-13 12:44 ` Kuniyuki Iwashima
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=20240513061244.12229-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=billy@starlabs.sg \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=mhal@rbox.co \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.