[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHS8izM9xtKMqaeMsm1LyadVuTL2REQ=ZvWaxEoJYCPuMApd4w@mail.gmail.com>
Date: Fri, 9 May 2025 16:55:21 -0700
From: Mina Almasry <almasrymina@...gle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Taehee Yoo <ap420073@...il.com>, davem@...emloft.net, pabeni@...hat.com,
edumazet@...gle.com, horms@...nel.org, sdf@...ichev.me,
netdev@...r.kernel.org, asml.silence@...il.com, dw@...idwei.uk,
skhawaja@...gle.com, kaiyuanz@...gle.com, jdamato@...tly.com
Subject: Re: [PATCH net v3] net: devmem: fix kernel panic when netlink socket
close after module unload
On Fri, May 9, 2025 at 3:32 PM Jakub Kicinski <kuba@...nel.org> wrote:
> > Other than that, I could not find issues. I checked lock ordering. The
> > lock hierarchy is:
> >
> > priv->lock
> > binding->lock
> > netdev_lock(dev)
>
> Did you mean:
>
> priv->lock
> netdev_lock(dev)
> binding->lock
Yep, that's it, sorry. I mixed up what netdev_hold and netdev_lock do
on the first read :(
--
Thanks,
Mina
Powered by blists - more mailing lists