linux-kernel - Fastfail: Device flag?

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

Message-ID: <20060825110606.GA20146@bitwizard.nl>
Date:	Fri, 25 Aug 2006 13:06:06 +0200
From:	Rogier Wolff <R.E.Wolff@...Wizard.nl>
To:	linux-kernel@...r.kernel.org
Subject: Fastfail: Device flag?

Hi,

The "md" and "multpath" drivers set a flag called "fastfail". I would
like this to become a flag that could also be set/cleared on a
per-device basis. 

I'd rather not spend the time doing the retries, and get an error
immediately. This is an application issue, and I would like to make
that choice myself.....

If there is a chance I won't have to patch kernels until eternity,
I'll write the patch to make this settable from userspace.

The current situation is that the IDE driver thinks it knows which
errors stand a chance of retrying (sectoridnotfound), and which don't
(datacrcerror). This was probably true of some disk in some distant
past. 

I'd rather not spend the time doing the retries, and get an error
immediately. This is an application issue.... 

I was thinking about adding a flag to genhd->flags, and then centrally
in "make_request" set the flag on the specific request if that flag is
set. But if I'm not mistaken, make_request has disappeared (possibly
changed into generic_make_request), and thus this change would have to
be in all "make_request" functions. I'd rather have a single line. So if
anbody has a hint as to where to put it, feel free to point me in the
right direction... ;-)

Comments?

	Roger. 

-- 
** R.E.Wolff@...Wizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
-
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/