From: Olivier Brunel <jjk@jjacky.com>
To: systemd-devel@lists.freedesktop.org
Cc: "initramfs@vger.kernel.org" <initramfs@vger.kernel.org>
Subject: Re: bpfilter blocks root unmount during shutdown
Date: Mon, 24 Sep 2018 16:55:31 +0200 [thread overview]
Message-ID: <20180924165531.5ae6615f@jjacky.com> (raw)
In-Reply-To: <20180924132047.GD31443@gardel-login>
On Mon, 24 Sep 2018 15:20:47 +0200
Lennart Poettering <lennart@poettering.net> wrote:
> On So, 23.09.18 10:38, Andrei Borzenkov (arvidjaar@gmail.com) wrote:
>
> > Dracut /shutdown script first tries to kill all processes still
> > running off old root. Unfortunately this fails for special user
> > process that runs bpfilter because it does not include reference
> > to /oldroot in places where dracut looks for in
> > kilall_proc_mountpoint()
>
> Hmm, when we invoke the /shutdown executable we already executed our
> process killing spree as part of systemd-shutdown. How come your
> processes even survive that long? What am I missing?
I believe it's because the bpfilter helper process is identified as a
kernel thread - since it has an empty command line - and therefore not
killed.
I personally feel this is a bug (in the kernel), but apparently
this whole bpfilter thing isn't quite ready yet and shouldn't be
used for the moment -- so hopefully it'll improve/be fixed in the mean
time.
You can see this thread[1] about the issue.
Cheers,
[1] https://www.spinics.net/lists/netdev/msg520030.html
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
next prev parent reply other threads:[~2018-09-24 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 7:38 bpfilter blocks root unmount during shutdown Andrei Borzenkov
2018-09-24 13:20 ` Lennart Poettering
2018-09-24 14:55 ` Olivier Brunel [this message]
2018-09-24 16:30 ` Andrei Borzenkov
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=20180924165531.5ae6615f@jjacky.com \
--to=jjk@jjacky.com \
--cc=initramfs@vger.kernel.org \
--cc=systemd-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.