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: Wed, 5 Sep 2018 17:52:43 +0200 [thread overview]
Message-ID: <20180905175243.78a6ba81@jjacky.com> (raw)
In-Reply-To: <20180828033500.g3siwst5h2ckewwb@ast-mbp>
Hi,
Quick follow-up on this:
- first off, Arch devs have updated their kernel config so the next
kernel will not have bpfilter enabled anymore, thus avoiding any
issue.
- having said that, I've found a neasy way to reproduce it in an Arch
VM, in case you're interested :
Boot the latest Arch ISO[1] which now contains a kernel 4.18.5 and do a
very basic installation, pretty much just:
# pacstrap /mnt base
# genfstab -U /mnt >> /mnt/etc/fstab
And of course install your boot loader of choice.
Then boot the brand new system, log in and make sure the helper is
actually started, i.e. `modprobe bpfilter` -- Now halt.
You'll see in the end that systemd complains that it can't
unmount /oldroot (EBUSY), aka the root fs; and that's because of the
bpfilter helper, which wasn't killed because it's seen as a kernel
thread due to its empty command line and therefore not signaled.
Cheers,
[1] https://www.archlinux.org/download/
next prev parent reply other threads:[~2018-09-05 21:36 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
2018-08-29 5:35 ` Alexei Starovoitov
2018-08-29 16:21 ` Olivier Brunel
2018-09-05 15:52 ` Olivier Brunel [this message]
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=20180905175243.78a6ba81@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 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.