public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Andreas Schwab <schwab@suse.de>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: single bit flip detector.
Date: Fri, 4 Aug 2006 18:06:44 -0400	[thread overview]
Message-ID: <20060804220644.GA28344@redhat.com> (raw)
In-Reply-To: <20060804141955.3139b20b.akpm@osdl.org>

On Fri, Aug 04, 2006 at 02:19:55PM -0700, Andrew Morton wrote:
 > On Tue, 1 Aug 2006 20:16:26 -0400
 > Dave Jones <davej@redhat.com> wrote:
 > 
 > > In case where we detect a single bit has been flipped, we spew
 > > the usual slab corruption message, which users instantly think
 > > is a kernel bug.  In a lot of cases, single bit errors are
 > > down to bad memory, or other hardware failure.
 > > 
 > > This patch adds an extra line to the slab debug messages
 > > in those cases, in the hope that users will try memtest before
 > > they report a bug.
 > 
 > Well boy, this has to be the most-reviewed patch ever.  You'd think that
 > I'd apply it with great confidence and warm fuzzies.

I should stick to one-liner fixes.

 > - one decl per line is more patching-friendly and a bit more idiomatic.
 > - make `bad_count' an int: a uchar might overflow
 > - Put a blank line between decls and code
 > - rename `total' to `error', remove `errors'.
 > - there's no need to sum up the errors.
 > - don't need to check for non-zero `errors': we know it is != POISON_FREE.
 > - make it look non-crapful in an 80-col window.
 > - add missing spaces in arithmetic

With this much iteration, I do have one question..
Does it still work ? :-)

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-08-04 22:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 18:44 single bit flip detector Dave Jones
2006-08-01 20:15 ` Bill Davidsen
2006-08-01 22:14 ` Alan Cox
2006-08-01 22:30   ` Dave Jones
2006-08-01 22:36     ` Dave Jones
2006-08-01 23:00       ` Alexey Dobriyan
2006-08-01 23:16         ` Dave Jones
2006-08-01 23:27           ` Dave Jones
2006-08-01 23:28           ` Andreas Schwab
2006-08-01 23:51             ` Dave Jones
2006-08-02  0:16               ` Dave Jones
2006-08-02  6:20                 ` Rolf Eike Beer
2006-08-02  7:08                 ` Jan Engelhardt
2006-08-06 11:05                   ` Geert Uytterhoeven
2006-08-02 15:24                 ` Patrick McLean
2006-08-02 16:12                   ` Randy.Dunlap
2006-08-04 21:19                 ` Andrew Morton
2006-08-04 22:06                   ` Dave Jones [this message]
2006-08-04 22:25                     ` Andrew Morton
2006-08-04 22:28                       ` Dave Jones
2006-08-02  7:08         ` Jan Engelhardt

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=20060804220644.GA28344@redhat.com \
    --to=davej@redhat.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@suse.de \
    /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