All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Arjan van de Ven <arjan@infradead.org>,
	tglx@tglx.de, mingo@elte.hu
Subject: Re: Warning/Oops report of the week of September 16th, 2008
Date: Thu, 25 Sep 2008 01:12:39 +0200	[thread overview]
Message-ID: <200809250112.40661.elendil@planet.nl> (raw)
In-Reply-To: <alpine.LFD.1.10.0809241541320.3265@nehalem.linux-foundation.org>

On Thursday 25 September 2008, Linus Torvalds wrote:
> In the meantime, that warning is just best ignored entirely. It's not a
> kernel bug per se, or even anything that is fixable without changing
> exported user interfaces that in my opinion aren't necessarily even
> _worth_ changing (the only reasonable change is extending on the insane
> interface that nobody cares about).

Yep, I agree it's basically harmless and I have been ignoring it. But that 
does not make it less annoying as, because of the call trace, it will 
continue to show up in logcheck mails every time.

If no other solution is found soon, would a patch to just skip the sysctl 
table check for this particular case be acceptable?

  parent reply	other threads:[~2008-09-24 23:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 16:22 Warning/Oops report of the week of September 16th, 2008 Arjan van de Ven
2008-09-17  0:40 ` Jay Cliburn
2008-09-24 22:36 ` Frans Pop
2008-09-24 22:45   ` Linus Torvalds
2008-09-24 22:57     ` Arjan van de Ven
2008-09-24 23:00     ` Linus Torvalds
2008-09-24 23:12     ` Frans Pop [this message]
2008-09-24 23:18       ` Linus Torvalds
2008-09-26 10:28     ` Alan Cox
2008-09-27 15:21       ` Frans Pop

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=200809250112.40661.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@tglx.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.