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:	Wed, 14 Jan 2009 11:25:00 +0100
From:	Jesper Nilsson <Jesper.Nilsson@...s.com>
To:	Greg KH <gregkh@...e.de>
Cc:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	David Miller <davem@...emloft.net>,
	"tj@...nel.org" <tj@...nel.org>,
	"stern@...land.harvard.edu" <stern@...land.harvard.edu>,
	"jens.axboe@...cle.com" <jens.axboe@...cle.com>,
	"hinko.kocevar@...rtapot.si" <hinko.kocevar@...rtapot.si>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: lib/klist.c: bit 0 in pointer can't be used as flag

On Wed, Jan 14, 2009 at 12:59:14AM +0100, Greg KH wrote:
> So, is this change still needed for klists?  I'm guessing so as they
> could be in statically allocated objects, right?

Like I said in another email, we can get away with just making
the struct klist aligned to 4 bytes (or 2 would probably suffice).
It would be a less intrusive patch.

> Here's yet another reason to never statically allocate a kobject...
> 
> thanks,
> 
> greg k-h

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@...s.com
--
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/