The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Adrian Bunk <bunk@kernel.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	David Miller <davem@davemloft.net>, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] bitfields API
Date: Thu, 28 Aug 2008 23:54:43 +0300	[thread overview]
Message-ID: <48B71093.3070409@cs.helsinki.fi> (raw)
In-Reply-To: <20080828202750.GB16462@cs181140183.pp.htv.fi>

Adrian Bunk wrote:
>> Heh, heh, one alternative is to have a kmemcheck_memset() thingy that  
>> unconditionally zeroes bit fields and maybe is a no-op when kmemcheck is  
>> disabled.
> 
> This sounds as if this might cause bugs to disappear when debugging gets 
> turned on?

Yeah, I suppose. The problem doing that unconditionally is that it 
increases kernel text slightly on some architectures (e.g. sparc). 
However, as long as you use the KMEMCHECK_BIT_FIELD annotation only in 
places that give you false positives, it's we should be safe.

		Pekka

  reply	other threads:[~2008-08-28 20:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 18:32 [RFC][PATCH] bitfields API Vegard Nossum
2008-08-28 18:40 ` Alexey Dobriyan
2008-08-28 18:40   ` Pekka Enberg
2008-08-28 20:27     ` Adrian Bunk
2008-08-28 20:54       ` Pekka Enberg [this message]
2008-08-28 20:59       ` Vegard Nossum
2008-08-28 18:46   ` Vegard Nossum
2008-08-28 19:02     ` Pekka J Enberg
2008-08-28 19:38       ` Vegard Nossum
2008-08-30  8:28         ` Vegard Nossum
2008-08-28 19:05     ` Alexey Dobriyan
2008-08-28 19:07       ` Pekka Enberg
2008-08-28 19:18       ` Vegard Nossum

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=48B71093.3070409@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vegard.nossum@gmail.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