From: Christoph Hellwig <hch@lst.de>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] proper replacements for ->proc_info
Date: Fri, 25 Apr 2003 12:59:18 +0200 [thread overview]
Message-ID: <20030425125918.A5330@lst.de> (raw)
In-Reply-To: <20030425104137.GE10374@parcelfarce.linux.theplanet.co.uk>; from viro@parcelfarce.linux.theplanet.co.uk on Fri, Apr 25, 2003 at 11:41:37AM +0100
On Fri, Apr 25, 2003 at 11:41:37AM +0100, viro@parcelfarce.linux.theplanet.co.uk wrote:
> On Fri, Apr 25, 2003 at 12:27:54PM +0200, Christoph Hellwig wrote:
>
> > + list_for_each_entry(sdev, &host->my_devices, siblings) {
> > + seq_printf(s, " %2d:%2d %4d %4d\n",
> > + sdev->id, sdev->lun,
> > + NCR_700_get_depth(sdev),
> > + sdev->current_tag);
>
> And that loop is protected by ...?
The right lock would be sdev->list_lock.
next prev parent reply other threads:[~2003-04-25 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 19:21 [PATCH] proper replacements for ->proc_info Christoph Hellwig
2003-04-23 19:29 ` James Bottomley
2003-04-23 19:39 ` Christoph Hellwig
2003-04-25 10:27 ` Christoph Hellwig
2003-04-25 10:41 ` viro
2003-04-25 10:59 ` Christoph Hellwig [this message]
2003-04-25 14:52 ` Christoph Hellwig
2003-04-25 15:17 ` Christoph Hellwig
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=20030425125918.A5330@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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