From: Jesper Nilsson <Jesper.Nilsson@axis.com>
To: Greg KH <gregkh@suse.de>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
David Miller <davem@davemloft.net>,
"tj@kernel.org" <tj@kernel.org>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"jens.axboe@oracle.com" <jens.axboe@oracle.com>,
"hinko.kocevar@cetrtapot.si" <hinko.kocevar@cetrtapot.si>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: lib/klist.c: bit 0 in pointer can't be used as flag
Date: Wed, 14 Jan 2009 11:25:00 +0100 [thread overview]
Message-ID: <20090114102500.GG19262@axis.com> (raw)
In-Reply-To: <20090113235914.GA20727@suse.de>
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@axis.com
next prev parent reply other threads:[~2009-01-14 10:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 15:14 Jesper Nilsson
2009-01-13 21:10 ` David Miller
2009-01-13 22:12 ` Jesper Nilsson
2009-01-13 22:40 ` KOSAKI Motohiro
2009-01-13 22:45 ` David Miller
2009-01-13 23:11 ` Bastien ROUCARIES
2009-01-14 10:19 ` Jesper Nilsson
2009-01-14 10:21 ` David Miller
2009-01-14 10:36 ` Jesper Nilsson
2009-01-14 10:45 ` David Miller
2009-01-14 11:02 ` Jesper Nilsson
2009-01-14 15:12 ` Jesper Nilsson
2009-01-14 18:17 ` Greg KH
2009-01-14 21:53 ` Jesper Nilsson
2009-01-13 23:54 ` KOSAKI Motohiro
2009-01-13 23:59 ` Greg KH
2009-01-14 10:25 ` Jesper Nilsson [this message]
2009-01-14 0:33 ` Hugh Dickins
2009-01-14 10:18 ` Jesper Nilsson
2009-01-13 22:42 ` David Miller
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=20090114102500.GG19262@axis.com \
--to=jesper.nilsson@axis.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=hinko.kocevar@cetrtapot.si \
--cc=jens.axboe@oracle.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tj@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
Powered by JetHome