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: <a781481a0705171002m61bdb9e9ka53c38cbe698265e@mail.gmail.com>
Date:	Thu, 17 May 2007 22:32:30 +0530
From:	"Satyam Sharma" <satyam.sharma@...il.com>
To:	"James Bottomley" <James.Bottomley@...eleye.com>
Cc:	"Stefan Richter" <stefanr@...6.in-berlin.de>,
	linux-scsi@...r.kernel.org, "Simon Arlott" <simon@...e.lp0.eu>,
	"Dave Jones" <davej@...hat.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	kernel-packagers@...r.kernel.org, "Matthew Wilcox" <matthew@....cx>
Subject: Re: [PATCH] SCSI: Let users disable SCSI_WAIT_SCAN to be built

On 5/17/07, James Bottomley <James.Bottomley@...eleye.com> wrote:
> [...]
> Please don't bother ... I really want a more considered way of fixing
> this.  If everyone decides the best way is exposing this to the user,
> then this is the way to do it ... however, I still don't consider this
> argument made out yet.

Neither do I, considering that the user can switch async scanning on
at any later time with the scan=async module option. The absence
of the async scan wait module will only screw things up for him later.

But then I don't consider an argument made out yet for doing this
via a separate module in the first place. scsi_wait_scan just does
_not_ want/deserve/need to be a module.

Of course, whining is useless, and discussions on lkml tend to be
most constructive / progressive only over code, so I'll try and see
if I can learn enough of the code in there to fix a patch to do the
async scan waiting thing using some other mechanism; this
module thing seems just horribly wrong/unnecessary.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ