From: Olivier Brunel <jjk@jjacky.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: netdev@vger.kernel.org, daniel@iogearbox.net
Subject: Re: bpfilter causes a leftover kernel process
Date: Tue, 28 Aug 2018 13:23:38 +0200 [thread overview]
Message-ID: <20180828132338.6995e445@jjacky.com> (raw)
In-Reply-To: <20180828033500.g3siwst5h2ckewwb@ast-mbp>
On Mon, 27 Aug 2018 20:35:02 -0700
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> I'm also running Arch Linux in my VM, but I'm not able to reproduce
> umount issue. I'm guessing it's somehow related to non-static build
> and libc.so being busy with old systemd.
Oh, I mentioned it in a previous draft of my original mail but it
seems it got lost in rewrites, I don't actually use systemd. Not that
it should matter here though.
> Typical shutdown should have done:
> [ 73.498022] shutdown[1]: Sending SIGTERM to remaining processes...
> [ 73.505501] shutdown[1]: Sending SIGKILL to remaining processes...
> [ 73.512783] shutdown[1]: Unmounting file systems.
> And at the time of umount / no processes are alive other than systemd.
Yeah, I have a similar thing happening on shutdown, except that we're
talking about a kernel thread here, so that process is ignored by the
mentionned killing spree as a result, thus leaving that process running.
>From a shell opened after the umounting fails I can see that only my
pid1 & the opened shell are running, except of course that this
bpfilter process is there, as a kernel thread "[none]"
Manually killing it at that point works, i.e. allows the umounting to
succeed and a proper shutdown to complete.
next prev parent reply other threads:[~2018-08-28 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 16:08 bpfilter causes a leftover kernel process Olivier Brunel
2018-08-27 16:31 ` Olivier Brunel
2018-08-28 3:35 ` Alexei Starovoitov
2018-08-28 11:23 ` Olivier Brunel [this message]
2018-08-29 5:35 ` Alexei Starovoitov
2018-08-29 16:21 ` Olivier Brunel
2018-09-05 15:52 ` Olivier Brunel
2018-10-16 16:38 ` Alexei Starovoitov
2018-10-20 17:39 ` [PATCH 0/2] " Olivier Brunel
2018-10-20 17:39 ` [PATCH 1/2] umh: Add command line to user mode helpers Olivier Brunel
2018-10-23 2:37 ` David Miller
2018-10-20 17:39 ` [PATCH 2/2] net: bpfilter: Set user mode helper's command line Olivier Brunel
2018-10-23 2:37 ` David Miller
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=20180828132338.6995e445@jjacky.com \
--to=jjk@jjacky.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
/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).