linux-kernel - Re: [PATCH v9 2/3] mmc: core: add random fault injection

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: <CAC5umygv+y4J-hPNDjYo9ToV4z4uv5rzvK9pCLMa7vbjKvJgZg@mail.gmail.com>
Date:	Wed, 14 Sep 2011 17:04:59 +0900
From:	Akinobu Mita <akinobu.mita@...il.com>
To:	Per Forlin <per.forlin@...aro.org>
Cc:	linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linaro-dev@...ts.linaro.org,
	Linus Walleij <linus.walleij@...aro.org>,
	Chris Ball <cjb@...top.org>, linux-doc@...r.kernel.org
Subject: Re: [PATCH v9 2/3] mmc: core: add random fault injection

2011/9/14 Per Forlin <per.forlin@...aro.org>:

> It's simple and the patch would be just two lines.
> The reason for changing my mind is that it may be useful to be able to
> pass the fault injection attributes even when mmc_core is a module.
>
>> module_param is more complicated than this. Also the parameter is only
>> usefull when when mmc_core is built into the kernel (it's useless when
>> mmc_core is built as a module).
>>
> If you want to enable fault injection for the mmc_core module at load
> time (during mmc initialisation) the param must be used.
> modprobe mmc_core fail_request=1,1,1,1
> As soon as the module is loaded there is no need for the module param anymore.

OK, I agree with you.  The module parameter is the only way
to enable mmc fault injection if CONFIG_FAULT_INJECTION_DEBUG_FS
is disabled.
--
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/