linux-kernel - Re: why does udev set timeout for all SCSI devices?

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] [day] [month] [year] [list]

Message-ID: <ac3eb2510810300130k29d6533ei6f49948889158712@mail.gmail.com>
Date:	Thu, 30 Oct 2008 09:30:56 +0100
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Tejun Heo" <tj@...nel.org>
Cc:	linux-scsi <linux-scsi@...r.kernel.org>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>,
	"Jens Axboe" <jens.axboe@...cle.com>
Subject: Re: why does udev set timeout for all SCSI devices?

On Thu, Oct 30, 2008 at 03:55, Tejun Heo <tj@...nel.org> wrote:
> As the $SUBJ says, why does udev set timeout for all SCSI devices?
> It's the following two rules.
>
> 50-udev-default.rules:SUBSYSTEM=="scsi", KERNEL=="[0-9]*:[0-9]*",
> ACTION=="add", ATTR{type}=="0|7|14", ATTR{timeout}="60"
> 50-udev-default.rules:SUBSYSTEM=="scsi", KERNEL=="[0-9]*:[0-9]*",
> ACTION=="add", ATTR{type}=="1", ATTR{timeout}="900"
>
> The appropriate default timeout differs depending on the transport and
> the type of the attached device, so the above two rules harm more than
> help.  The affect of the above two rules weren't visible for some
> reason but with recent block layer timeout update, they actually work
> and cause problems.

It's in there for years, I can not even dig out, where it is coming
from. I just removed it from the default rules.

Thanks,
Kay
--
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/