mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Holger Kiehl <Holger.Kiehl@dwd.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Christoph Hellwig <hch@lst.de>
Subject: bpfilter: write fail messages with 5.15.x and centos 7.9.2009
Date: Wed, 29 Dec 2021 13:27:58 +0000 (GMT)	[thread overview]
Message-ID: <71e27b99-ef9c-4563-833d-e6eab5419cdb@diagnostix.dwd.de> (raw)

Hello,

I just upgraded the kernel from 5.10.x to 5.15.12 on an old Centos
7.9.2009 server. The kernel is build on a new fedora 35 system
via 'make binrpm-pkg'. With this I see the following errors:

    [  232.140766] bpfilter: Loaded bpfilter_umh pid 6327
    [  232.152144] bpfilter: write fail -32
    [  232.187175] bpfilter: Loaded bpfilter_umh pid 6330
    [  232.198540] bpfilter: write fail -32
    [  232.234604] bpfilter: Loaded bpfilter_umh pid 6332
    [  232.245916] bpfilter: write fail -32
    [  232.281883] bpfilter: Loaded bpfilter_umh pid 6337
    [  232.293222] bpfilter: write fail -32
    [  232.335798] bpfilter: Loaded bpfilter_umh pid 6380
    [  232.347157] bpfilter: write fail -32
    [  244.411821] bpfilter: Loaded bpfilter_umh pid 6712
    [  244.423216] bpfilter: write fail -32

These appear as soon as something is done via iptables (setting
something or just viewing). Is this something I need to worry
about? Under 5.10.81 I did not see these messages.

In Jul 2020 I see a similar report 'bpfilter logging write errors in
dmesg', but could not find a solution.

Any hint what I can do to fix this?

Thanks,
Holger

             reply	other threads:[~2021-12-29 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 13:27 Holger Kiehl [this message]
2021-12-29 17:32 ` Christoph Hellwig

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=71e27b99-ef9c-4563-833d-e6eab5419cdb@diagnostix.dwd.de \
    --to=holger.kiehl@dwd.de \
    --cc=hch@lst.de \
    --cc=linux-kernel@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
all inboxes | Powered by JetHome®