[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <496ACEF8.2030605@trash.net>
Date: Mon, 12 Jan 2009 06:02:48 +0100
From: Patrick McHardy <kaber@...sh.net>
To: Rusty Russell <rusty@...tcorp.com.au>
CC: Dave Jones <davej@...hat.com>,
Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>,
Jan Engelhardt <jengelh@...ozas.de>,
David Miller <davem@...emloft.net>, ajax@...hat.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
netfilter-devel@...r.kernel.org
Subject: Re: [PATCH] net: Remove a noisy printk
Rusty Russell wrote:
> On Monday 15 December 2008 06:33:53 Dave Jones wrote:
>> On Sun, Dec 14, 2008 at 06:09:17PM +0100, Jozsef Kadlecsik wrote:
>> > In a >normal< system one usually does not use raw sockets. So if a root
>> > process do use raw socket, at least netfilter sends a notification and
>> > there's a chance that someone take notice it by checking the kernel logs.
>>
>> 'normal' systems are irrelevant here. This message is triggerable remotely.
>
> I don't think it can be. This is for truncated locally-generated outgoing
> packets, which can only happen when root is playing with raw sockets.
Yes, it can only be triggered locally by root.
> As you can probably tell, I was the one who wrote this printk :) IMHO,
> one reasonable complaint is sufficient to have it removed, so just remove
> it. If anyone thinks it's valuable, put a static counter < 5 around it
> and add pid/comm info.
I've queued this patch to remove it.
View attachment "01.diff" of type "text/x-patch" (3606 bytes)
Powered by blists - more mailing lists