[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20110517.154521.1357718233260897046.davem@davemloft.net>
Date: Tue, 17 May 2011 15:45:21 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: mst@...hat.com
Cc: mirq-linux@...e.qmqm.pl, netdev@...r.kernel.org,
herbert@...dor.hengli.com.au, bhutchings@...arflare.com
Subject: Re: [PATCH] net: Change netdev_fix_features messages loglevel
From: "Michael S. Tsirkin" <mst@...hat.com>
Date: Mon, 16 May 2011 23:37:39 +0300
> On Mon, May 16, 2011 at 03:14:34PM -0400, David Miller wrote:
>> From: Michaİİ Mirosİİaw <mirq-linux@...e.qmqm.pl>
>> Date: Mon, 16 May 2011 15:17:57 +0200 (CEST)
>>
>> > Those reduced to DEBUG can possibly be triggered by unprivileged processes
>> > and are nothing exceptional. Illegal checksum combinations can only be
>> > caused by driver bug, so promote those messages to WARN.
>> >
>> > Since GSO without SG will now only cause DEBUG message from
>> > netdev_fix_features(), remove the workaround from register_netdevice().
>> >
>> > Signed-off-by: Michaİİ Mirosİİaw <mirq-linux@...e.qmqm.pl>
>>
>> Applied, thanks.
>
> Cool, how about we make 'Features changed' debug as well?
> This way userspace can't fill up the log just by tweaking tun features
> with an ioctl.
>
> Untested, but you get the message.
>
> Signed-off-by: Michael S. Tsirkin <mst@...hat.com>
Agreed and applied.
I agree with Herbert's long term assertion that we should handle this
differently, somehow, to avoid these issues.
But as long as userspace can trigger these events, we have to do things
like decrease the logging level of these messages.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists