linux-kernel - Re: [PATCH] async scsi scanning, version 13

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: <1159732857.3542.5.camel@mulgrave.il.steeleye.com>
Date:	Sun, 01 Oct 2006 15:00:57 -0500
From:	James Bottomley <James.Bottomley@...elEye.com>
To:	Matthew Wilcox <matthew@....cx>
Cc:	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] async scsi scanning, version 13

On Thu, 2006-09-28 at 15:19 -0600, Matthew Wilcox wrote:
> Version 13 ...
>   
> changes vs version 12:
> 
> Address akpm's comments:
>  - use DEFINE_SPINLOCK
>  - document how scsi_complete_async_scans works
>  - document why the memory allocation loop in scsi_complete_async_scans
>    will eventually terminate
>  - document why we don't add ourselves to the list if it's already empty
>     
> shost_for_each_device is safe and shost_for_each_device_safe isn't.
> Delete shost_for_each_device_safe, use shost_for_each_device and update
> the docs for __shost_for_each_device and shost_for_each_device to be
> more accurate.
> 
> changes vs version 11:
> 
> Fix whitespace pointed out by Randy Dunlap.

OK, my plan for this is to place it in SCSI misc as soon as we get
2.6.19-rc1.  That way we'll give it a thorough check out in -mm before
it hits mainline.

By the way, a global change log (rather than changes relative to
previous versions) would be appreciated.

James


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