linux-kernel - Re: Asynchronous scsi scanning

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: <464A4222.4000208@linux.intel.com>
Date:	Tue, 15 May 2007 16:28:34 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Satyam Sharma <satyam.sharma@...il.com>
CC:	Matthew Wilcox <matthew@....cx>, Simon Arlott <simon@...e.lp0.eu>,
	James Bottomley <james.bottomley@...eleye.com>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org, kernel-packagers@...r.kernel.org,
	"Robert P. J. Day" <rpjday@...dspring.com>
Subject: Re: Asynchronous scsi scanning

Satyam Sharma wrote:
>> > >semantics of it (read-only?  read-write?  write-only?
> 
> Well, it _has_ to be write, don't really care if it's read-write or
> write-only. I would still prefer read-write, but we can go ahead with
> write-only too. It doesn't really matter, does it?

just to be devils advocate...
it should be a read that returns when done, and that can be polled
-
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/