[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180829053536.en6crhdfs7r2d6vt@ast-mbp.dhcp.thefacebook.com>
Date: Tue, 28 Aug 2018 22:35:38 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Olivier Brunel <jjk@...cky.com>
Cc: netdev@...r.kernel.org, daniel@...earbox.net
Subject: Re: bpfilter causes a leftover kernel process
On Tue, Aug 28, 2018 at 01:23:38PM +0200, Olivier Brunel wrote:
> On Mon, 27 Aug 2018 20:35:02 -0700
> Alexei Starovoitov <alexei.starovoitov@...il.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.
it's not a kernel thread and sounds like there is a bug in your pid 1
that is worth fixing.
Powered by blists - more mailing lists