public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: Taehee Yoo <ap420073@gmail•com>
Cc: Mina Almasry <almasrymina@google•com>,
	Stanislav Fomichev <stfomichev@gmail•com>,
	davem@davemloft•net, pabeni@redhat•com, edumazet@google•com,
	andrew+netdev@lunn•ch, horms@kernel•org, asml.silence@gmail•com,
	dw@davidwei•uk, sdf@fomichev•me, skhawaja@google•com,
	simona.vetter@ffwll•ch, kaiyuanz@google•com,
	netdev@vger•kernel.org
Subject: Re: [PATCH net] net: devmem: fix kernel panic when socket close after module unload
Date: Mon, 5 May 2025 10:34:19 -0700	[thread overview]
Message-ID: <20250505103419.1965365b@kernel.org> (raw)
In-Reply-To: <CAMArcTVog3pUQtXrytyRppkXvwBH6mHvcTsh9OsHZ3zPQYytiQ@mail.gmail.com>

On Fri, 18 Apr 2025 19:52:43 +0900 Taehee Yoo wrote:
> I’ll send the patch over shortly.

Hi Taehee!

Are you still working on this problem? I haven't seen any patches,
I think it's the last known instance locking problem we have.

  reply	other threads:[~2025-05-05 17:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15  9:24 [PATCH net] net: devmem: fix kernel panic when socket close after module unload Taehee Yoo
2025-04-15 17:33 ` Stanislav Fomichev
2025-04-15 18:22 ` Mina Almasry
2025-04-15 18:59   ` Stanislav Fomichev
2025-04-16  2:59     ` Jakub Kicinski
2025-04-16 14:40       ` Stanislav Fomichev
2025-04-17  0:15         ` Jakub Kicinski
2025-04-16 15:01       ` Taehee Yoo
2025-04-17  0:35         ` Jakub Kicinski
2025-04-17  6:57           ` Taehee Yoo
2025-04-17 14:09             ` Jakub Kicinski
2025-04-18 10:46               ` Taehee Yoo
2025-04-16 15:47       ` Mina Almasry
2025-04-17  0:27         ` Jakub Kicinski
2025-04-17 21:07           ` Mina Almasry
2025-04-18 10:52             ` Taehee Yoo
2025-05-05 17:34               ` Jakub Kicinski [this message]
2025-05-06 11:41                 ` Taehee Yoo

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=20250505103419.1965365b@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=almasrymina@google$(echo .)com \
    --cc=andrew+netdev@lunn$(echo .)ch \
    --cc=ap420073@gmail$(echo .)com \
    --cc=asml.silence@gmail$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dw@davidwei$(echo .)uk \
    --cc=edumazet@google$(echo .)com \
    --cc=horms@kernel$(echo .)org \
    --cc=kaiyuanz@google$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=sdf@fomichev$(echo .)me \
    --cc=simona.vetter@ffwll$(echo .)ch \
    --cc=skhawaja@google$(echo .)com \
    --cc=stfomichev@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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