From: Eric Dumazet <eric.dumazet@gmail.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] slub: fix check_bytes() for slub debugging
Date: Tue, 09 Aug 2011 05:33:03 +0200 [thread overview]
Message-ID: <1312860783.2531.31.camel@edumazet-laptop> (raw)
In-Reply-To: <1312859440.2531.20.camel@edumazet-laptop>
Le mardi 09 aoA>>t 2011 A 05:10 +0200, Eric Dumazet a A(C)crit :
> Le dimanche 07 aoA>>t 2011 A 18:30 +0900, Akinobu Mita a A(C)crit :
> > The check_bytes() function is used by slub debugging. It returns a pointer
> > to the first unmatching byte for a character in the given memory area.
> >
> > If the character for matching byte is greater than 0x80, check_bytes()
> > doesn't work. Becuase 64-bit pattern is generated as below.
> >
> > value64 = value | value << 8 | value << 16 | value << 24;
> > value64 = value64 | value64 << 32;
> >
> > The integer promotions are performed and sign-extended as the type of value
> > is u8. The upper 32 bits of value64 is 0xffffffff in the first line, and
> > the second line has no effect.
> >
> > This fixes the 64-bit pattern generation.
> >
> > Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> > Cc: Christoph Lameter <cl@linux-foundation.org>
> > Cc: Pekka Enberg <penberg@kernel.org>
> > Cc: Matt Mackall <mpm@selenic.com>
> > Cc: linux-mm@kvack.org
> > ---
> > mm/slub.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/mm/slub.c b/mm/slub.c
> > index eb5a8f9..5695f92 100644
> > --- a/mm/slub.c
> > +++ b/mm/slub.c
> > @@ -701,7 +701,7 @@ static u8 *check_bytes(u8 *start, u8 value, unsigned int bytes)
> > return check_bytes8(start, value, bytes);
> >
> > value64 = value | value << 8 | value << 16 | value << 24;
> > - value64 = value64 | value64 << 32;
> > + value64 = (value64 & 0xffffffff) | value64 << 32;
> > prefix = 8 - ((unsigned long)start) % 8;
> >
> > if (prefix) {
>
> Still buggy I am afraid. Could we use the following ?
>
>
> value64 = value;
> value64 |= value64 << 8;
> value64 |= value64 << 16;
> value64 |= value64 << 32;
>
>
Well, 'buggy' was not well chosen.
Another possibility would be to use a multiply if arch has a fast
multiplier...
value64 = value;
#if defined(ARCH_HAS_FAST_MULTIPLIER) && BITS_PER_LONG == 64
value64 *= 0x0101010101010101;
#elif defined(ARCH_HAS_FAST_MULTIPLIER)
value64 *= 0x01010101;
value64 |= value64 << 32;
#else
value64 |= value64 << 8;
value64 |= value64 << 16;
value64 |= value64 << 32;
#endif
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-09 3:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 9:30 Akinobu Mita
2011-08-08 21:24 ` Marcin Slusarz
2011-08-09 1:08 ` Akinobu Mita
2011-08-09 3:10 ` Eric Dumazet
2011-08-09 3:33 ` Eric Dumazet [this message]
2011-08-09 9:38 ` Akinobu Mita
2011-08-09 9:43 ` Pekka Enberg
2011-08-09 9:54 ` Eric Dumazet
2011-08-09 9:46 ` Eric Dumazet
2011-08-09 21:46 ` Marcin Slusarz
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=1312860783.2531.31.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox