From: Bruno Meneguele <bmeneg@redhat.com>
To: Martin Zaharinov <micron10@gmail.com>
Cc: netdev@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH v2] net/bpfilter: fix dprintf usage for /dev/kmsg
Date: Tue, 31 Mar 2020 09:46:05 -0300 [thread overview]
Message-ID: <20200331124605.GG10754@glitch> (raw)
In-Reply-To: <20200330131313.GA10754@glitch>
[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]
On Mon, Mar 30, 2020 at 10:13:15AM -0300, Bruno Meneguele wrote:
> On Mon, Mar 30, 2020 at 03:48:12PM +0300, Martin Zaharinov wrote:
> > Hi Bruno
> > i see after release kernel 5.6.0 with your latest patch have strange
> > messages please check:
> >
> > [ 31.025483] bpfilter: Loaded bpfilter_umh pid 2689
> > [ 31.025533] Started bpfilter
> > [ 31.042586] testing the buffer
> > [ 31.050822] testing the buffer
> > [ 31.059304] testing the buffer
> > [ 31.067747] testing the buffer
> > [ 31.148789] testing the buffer
> > [ 31.156130] testing the buffer
> > [ 31.164012] testing the buffer
> > [ 31.170685] testing the buffer
> > [ 31.176886] testing the buffer
> >
> > when drop bpfilter module stop enter new messages in kmsg.
> >
>
> Hi Martin,
>
> these aren't really "strange messages", but the correct ones. They
> started to appear now because before my patch the log wasn't working at
> all. I'm not really aware what is the logic behind the bpfilter_umh
> module, but AFAIK each iptable rule sent from kernel side to UMH
> userspace code will generate one "testing the buffer" message.
>
> I think we can silence it by limiting it to print only once, but I would
> need to check with Alexei Starovoitov <ast@kernel.org> if it would be
> fine (CC'ing here).
>
> Thanks for the heads up :).
>
Wow, forget about all of that! That's actually my mistake!
This "testing the buffer" was actually added by my own patch! How could
I not see that? I'm really sorry and /thanks/ at the same time Martin.
I'm going to send a new patch removing it.
--
bmeneg
PGP Key: http://bmeneg.com/pubkey.txt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-31 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALidq=VmXZ5erdNOeBdXE087QHO7SZVn4rb5+M26GrB56dpYpQ@mail.gmail.com>
2020-03-30 13:13 ` [PATCH v2] net/bpfilter: fix dprintf usage for /dev/kmsg Bruno Meneguele
2020-03-31 12:46 ` Bruno Meneguele [this message]
2020-03-12 23:08 Bruno Meneguele
2020-03-15 4:02 ` 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=20200331124605.GG10754@glitch \
--to=bmeneg@redhat.com \
--cc=ast@kernel.org \
--cc=micron10@gmail.com \
--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).