From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] unified spinlock
Date: Thu, 20 Jan 2005 20:04:13 +0000 [thread overview]
Message-ID: <20050120200413.GL25940@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <41EFCFDC.4060509@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
On Thu, Jan 20, 2005 at 08:50:47AM -0800, Greg KH wrote:
> On Thu, Jan 20, 2005 at 07:44:24AM -0800, Randy.Dunlap wrote:
> > Matthew Wilcox wrote:
> > >I think this is referring to initialisation of spinlocks that are
> > >allocated dynamically, not statically. If a lock validator can't cope
> > >with that, it needs to be fixed, IMO.
>
> Yes, it is. See the number of patches that have been flowing into the
> kernel lately to fix this issue up.
However, the correct way to fix this is to use DEFINE_SPIN_LOCK, not to
make static locks dynamically initialised.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-01-20 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 15:35 [KJ] [PATCH] unified spinlock Randy.Dunlap
2005-01-20 15:44 ` Randy.Dunlap
2005-01-20 15:47 ` Matthew Wilcox
2005-01-20 16:50 ` Greg KH
2005-01-20 20:04 ` Matthew Wilcox [this message]
2005-01-20 20:09 ` Greg KH
2005-01-22 18:12 ` Domen Puncer
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=20050120200413.GL25940@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=kernel-janitors@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.