linux-kernel - Re: lib/klist.c: bit 0 in pointer can't be used as flag

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Jan 2009 14:45:21 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	kosaki.motohiro@...fujitsu.com
Cc:	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.
--
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/