linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Adrien Schildknecht <adrien+dev@schischi.me>
Cc: Shawn Lin <shawn.lin@rock-chips.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: add ifdef around fault_create_debugfs_attr()
Date: Tue, 10 Nov 2015 18:29:20 +0100	[thread overview]
Message-ID: <CAPDyKFq39uWPTBou+CUDqbWj8_RENeZMmokV3LRA5LBpG7fAVw@mail.gmail.com> (raw)
In-Reply-To: <20151110160420.2ec59606.adrien+dev@schischi.me>

On 10 November 2015 at 16:04, Adrien Schildknecht
<adrien+dev@schischi.me> wrote:
> On Mon, 9 Nov 2015 14:33:11 +0100
> Ulf Hansson <ulf.hansson@linaro.org> wrote:
>> On 6 November 2015 at 13:15, Adrien Schildknecht
>> <adrien+dev@schischi.me> wrote:
>> > FAIL_MMC_REQUEST can be used without FAULT_INJECTION_DEBUG_FS.
>> > In this case fault_create_debugfs_attr() will always return an
>> > error and lead to the deletion of the whole debugfs directory.
>> >
>> > This patch makes sure that FAULT_INJECTION_DEBUG_FS is enabled
>> > before attempting to create the debugfs atttribute.
>> >
>> > Signed-off-by: Adrien Schildknecht <adrien+dev@schischi.me>
>> > ---
>> >  drivers/mmc/core/debugfs.c | 2 ++
>> >  1 file changed, 2 insertions(+)
>> >
>> > diff --git a/drivers/mmc/core/debugfs.c b/drivers/mmc/core/debugfs.c
>> > index 154aced..13e842c 100644
>> > --- a/drivers/mmc/core/debugfs.c
>> > +++ b/drivers/mmc/core/debugfs.c
>> > @@ -259,11 +259,13 @@ void mmc_add_host_debugfs(struct mmc_host
>> > *host) if (fail_request)
>> >                 setup_fault_attr(&fail_default_attr, fail_request);
>> >         host->fail_mmc_request = fail_default_attr;
>> > +#ifdef CONFIG_FAULT_INJECTION_DEBUG_FS
>> >         if (IS_ERR(fault_create_debugfs_attr("fail_mmc_request",
>> >                                              root,
>> >                                              &host->fail_mmc_request)))
>> >                 goto err_node;
>> >  #endif
>> > +#endif
>> >         return;
>> >
>> >  err_node:
>> > --
>> > 2.6.2
>> >
>>
>> I think you are solving this in the wrong way. Will it really makes
>> sense to use FAIL_MMC_REQUEST unless FAULT_INJECTION_DEBUG_FS is set,
>> I don't think so.
> The fault attribute can be configured using either the debugfs or the
> module parameter "fail_request". It is thus possible to use
> FAIL_MMC_REQUEST without FAULT_INJECTION_DEBUG_FS (even if it is less
> convenient).
>
>> I suggest you to change FAIL_MMC_REQUEST from depending on
>> FAULT_INJECTION to FAULT_INJECTION_DEBUG_FS in /lib/Kconfig.debug.
> The other systems that use the fault injection infrastructure (futex,
> alloc_pages, slab...) can be used without the dependency on
> FAULT_INJECTION_DEBUG_FS. They also use nested #ifdef to handle this

There are also those that chosen to depend on
FAULT_INJECTION_DEBUG_FS, such as FAULT_INJECTION_STACKTRACE_FILTER.

> configuration. I chose the #ifdef approach for the sake of coherence.

I would like to keep the amount of #ifdefs around in the code to a
minimal. In this case it doesn't even make sense and as there are no
consistent behaviour to consider, could you please adopt the Kconfig
solution instead!?

Kind regards
Uffe

  reply	other threads:[~2015-11-10 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 12:15 [PATCH] mmc: add ifdef around fault_create_debugfs_attr() Adrien Schildknecht
2015-11-09 13:33 ` Ulf Hansson
2015-11-10 15:04   ` Adrien Schildknecht
2015-11-10 17:29     ` Ulf Hansson [this message]
2015-11-10 19:12       ` [PATCH v2] mmc: kconfig: replace FAULT_INJECTION with FAULT_INJECTION_DEBUG_FS Adrien Schildknecht
2015-11-19 11:29         ` Ulf Hansson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPDyKFq39uWPTBou+CUDqbWj8_RENeZMmokV3LRA5LBpG7fAVw@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=adrien+dev@schischi.me \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shawn.lin@rock-chips.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).