[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090114085341.442C.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Date: Wed, 14 Jan 2009 08:54:20 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: David Miller <davem@...emloft.net>
Cc: kosaki.motohiro@...fujitsu.com, Jesper.Nilsson@...s.com,
tj@...nel.org, gregkh@...e.de, stern@...land.harvard.edu,
jens.axboe@...cle.com, hinko.kocevar@...rtapot.si,
linux-kernel@...r.kernel.org
Subject: Re: lib/klist.c: bit 0 in pointer can't be used as flag
> From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
> Date: Wed, 14 Jan 2009 07:40:19 +0900
>
> > > It may be that we've worked around the other spots, although I haven't
> > > seen anything like that, we might just have been lucky until now.
> > >
> > > Can you recall another place where this trick is used?
> >
> > rmap.
> > Don't CRIS use mmu?
>
> I'm beginning to suspect the issue is only with objects
> in the kernel image itself. Dynamically allocated memory
> is properly aligned and therefore the "low bit status bits
> in pointer" trick works.
Ah, I see.
very thank you for helpful explain.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists