[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54a73bb8163716f724af91de3ed8b2bd59aa5d39.camel@redhat.com>
Date: Fri, 10 May 2024 13:11:06 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Kuniyuki Iwashima <kuniyu@...zon.com>
Cc: billy@...rlabs.sg, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, kuni1840@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH v2 net] af_unix: Update unix_sk(sk)->oob_skb under
sk_receive_queue lock.
On Fri, 2024-05-10 at 19:54 +0900, Kuniyuki Iwashima wrote:
> From: Paolo Abeni <pabeni@...hat.com>
> Date: Fri, 10 May 2024 12:44:58 +0200
> > On Fri, 2024-05-10 at 18:39 +0900, Kuniyuki Iwashima wrote:
> > > diff --git a/net/unix/garbage.c b/net/unix/garbage.c
> > > index 0104be9d4704..b87e48e2b51b 100644
> > > --- a/net/unix/garbage.c
> > > +++ b/net/unix/garbage.c
> > > @@ -342,10 +342,12 @@ static void __unix_gc(struct work_struct *work)
> > > scan_children(&u->sk, inc_inflight, &hitlist);
> > >
> > > #if IS_ENABLED(CONFIG_AF_UNIX_OOB)
> > > + spin_lock(&u->sk.sk_receive_queue.lock);
> > > if (u->oob_skb) {
> > > - kfree_skb(u->oob_skb);
> > > + WARN_ON_ONCE(skb_unref(u->oob_skb));
> >
> > Sorry for not asking this first, but it's not clear to me why the above
> > change (just the 'WARN_ON_ONCE' introduction) is needed and if it's
> > related to the addressed issue???
>
> I think I added it to make it clear that here we don't actually free skb
> and consistent with manage_oob().
>
> But I don't have strong preference as it will be removed soon.
Ok, thanks for the explanation. I'm fine with the above.
Acked-by: Paolo Abeni <pabeni@...hat.com>
Powered by blists - more mailing lists