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]

Message-Id: <20090114.024528.80563421.davem@davemloft.net>
Date:	Wed, 14 Jan 2009 02:45:28 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	Jesper.Nilsson@...s.com
Cc:	roucaries.bastien@...il.com, linux-kernel@...r.kernel.org,
	tj@...nel.org, gregkh@...e.de, stern@...land.harvard.edu,
	jens.axboe@...cle.com, hinko.kocevar@...rtapot.si
Subject: Re: lib/klist.c: bit 0 in pointer can't be used as flag

From: Jesper Nilsson <Jesper.Nilsson@...s.com>
Date: Wed, 14 Jan 2009 11:36:24 +0100

> On Wed, Jan 14, 2009 at 11:21:40AM +0100, David Miller wrote:
> > From: Jesper Nilsson <Jesper.Nilsson@...s.com>
> > Date: Wed, 14 Jan 2009 11:19:08 +0100
> > > The following patch works for CRIS, and is less intrusive than
> > > my earlier patch. If this the way to go I can resubmit a proper patch.
> > 
> > Out of curiosity, is there a way to get gcc to output code such
> > that data objects are aligned more naturally?  Some option or
> > similar?
> 
> There's flags for alignment of objects, but no flags for changing
> structure layout or size, which is probably what we run into here.

Really?

I thought the problem is that the base object can have any odd
alignment in the kernel image.  And this is why the problem isn't run
into for objects allocated using dynamic allocation.

--
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/