From: Chris Wright <chris@wirex.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] PCI device list locking - take 2
Date: Wed, 18 Jun 2003 17:20:07 -0700 [thread overview]
Message-ID: <20030618172007.C20182@figure1.int.wirex.com> (raw)
In-Reply-To: <20030618235232.GA2667@kroah.com>; from greg@kroah.com on Wed, Jun 18, 2003 at 04:52:32PM -0700
* Greg KH (greg@kroah.com) wrote:
> On Wed, Jun 18, 2003 at 04:32:37PM -0700, Chris Wright wrote:
> > I'm not sure testing a valid ->next makes sense. It could be non-NULL,
> > but poison, or if it was using list_del_init, it would be stuck in loop.
>
> When we take the devices off of the list, after list_del(), still under
> the lock, we can null out the list pointers. Then, later under the
> lock, we can check the pointer before we move to it. We aren't doing
> fancy list_* functions with the pci device lists at all.
Ah, ok, that should work.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2003-06-19 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 21:29 [RFC] PCI device list locking - take 2 Greg KH
2003-06-18 22:33 ` Chris Wright
2003-06-18 22:46 ` Greg KH
2003-06-18 23:32 ` Chris Wright
2003-06-18 23:52 ` Greg KH
2003-06-19 0:20 ` Chris Wright [this message]
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=20030618172007.C20182@figure1.int.wirex.com \
--to=chris@wirex.com \
--cc=greg@kroah.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox