From: Pablo Neira Ayuso <pablo@gnumonks.org>
To: Romain Francoise <romain@orebokech.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
coreteam@netfilter.org, Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
eric.dumazet@gmail.com
Subject: Re: [PATCH] netfilter: xt_LOG: avoid using old-style "<.>" printk prefix
Date: Wed, 12 Sep 2012 17:06:42 +0200 [thread overview]
Message-ID: <20120912150642.GA22197@1984> (raw)
In-Reply-To: <87392n8j3w.fsf@silenus.orebokech.com>
Replying from different email, @netfilter.org is currently down due to
some power supply problems.
On Wed, Sep 12, 2012 at 03:29:39PM +0200, Romain Francoise wrote:
> Hi Pablo,
>
> Pablo Neira Ayuso <pablo@netfilter.org> writes:
>
> > ebt_log chunk is missing.
>
> Sorry, didn't notice that it has the same bug. Do you want that in the
> same patch, or separate?
>
> >> m->buf[m->count] = 0;
> >> - printk("%s\n", m->buf);
> >> + printk_emit(0, level, NULL, 0, "%s\n", m->buf);
>
> > I think it should be printk_emit(-1, ... Note facility is -1.
>
> > Thus, we skip the syslog prefix stripping (we can skip it and save
> > some cycles).
>
> I don't think that's possible, the facility is copied down to user-space
> consumers and it has to be zero for the message to be identified as
> originating from the kernel (0 is LOG_KERN).
I see.
> As it boils down to a single test for KERN_SOH_ASCII I don't think it
> matters very much.
I'm going to take Joe's patch, I prefer using the printk interface.
Thanks anyway.
prev parent reply other threads:[~2012-09-12 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 17:29 [PATCH] netfilter: xt_LOG: avoid using old-style "<.>" printk prefix Romain Francoise
2012-09-12 12:48 ` Pablo Neira Ayuso
2012-09-12 13:29 ` Romain Francoise
2012-09-12 15:06 ` Pablo Neira Ayuso [this message]
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=20120912150642.GA22197@1984 \
--to=pablo@gnumonks.org \
--cc=akpm@linux-foundation.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=joe@perches.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=romain@orebokech.com \
/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).