From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Anton Guda <atu@dmeti.dp.ua>
Subject: Re: linux-next: build failure after merge of the final tree (driver-core tree related)
Date: Tue, 10 May 2011 21:38:45 +0200 [thread overview]
Message-ID: <201105102138.45867.rjw@sisk.pl> (raw)
In-Reply-To: <1304983104.1351.17.camel@zag>
On Tuesday, May 10, 2011, Kay Sievers wrote:
> On Tue, 2011-05-10 at 00:19 +0200, Rafael J. Wysocki wrote:
> > On Monday, May 09, 2011, Kay Sievers wrote:
> > > On Mon, May 9, 2011 at 06:58, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > > After merging the final tree, today's linux-next build (powerpc allnoconfig)
> > > > failed like this:
> > > >
> > > > kernel/sys.c: In function 'kernel_restart_prepare':
> > > > kernel/sys.c:317: error: implicit declaration of function 'usermodehelper_disable'
> > >
> > > Rafael, seems usermodehelper_disable() depends on CONFIG_PM_SLEEP.
> > >
> > > Any reason for that conditional? Remove it now?
> >
> > Aw, we have two conflicting changes. Could you prepare a patch on top of:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-2.6.git pm-next
> >
> > removing that #ifdef? That needs to be done in kmod.h too.
>
> Like this?
Yes, thanks.
I applied it to suspend-2.6/linux-next.
Rafael
> From: Kay Sievers <kay.sievers@vrfy.org>
> Subject: kmod: always provide usermodehelper_disable()
>
> We need to prevent kernel-forked processes during system poweroff.
> Such processes try to access the filesystem whose disks we are
> trying to shutdown at the same time. This causes delays and exceptions
> in the storage drivers.
>
> A follow-up patch will add these calls and need usermodehelper_disable()
> also on systems without suspend support.
>
> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
> ---
>
> diff --git a/include/linux/kmod.h b/include/linux/kmod.h
> index 7f3dbcb..3102318 100644
> --- a/include/linux/kmod.h
> +++ b/include/linux/kmod.h
> @@ -111,12 +111,8 @@ call_usermodehelper(char *path, char **argv, char **envp, enum umh_wait wait)
>
> extern void usermodehelper_init(void);
>
> -#ifdef CONFIG_PM_SLEEP
> extern int usermodehelper_disable(void);
> extern void usermodehelper_enable(void);
> extern bool usermodehelper_is_disabled(void);
> -#else
> -static inline bool usermodehelper_is_disabled(void) { return false; }
> -#endif
>
> #endif /* __LINUX_KMOD_H__ */
> diff --git a/kernel/kmod.c b/kernel/kmod.c
> index 9ab513b..5ae0ff3 100644
> --- a/kernel/kmod.c
> +++ b/kernel/kmod.c
> @@ -245,7 +245,6 @@ static void __call_usermodehelper(struct work_struct *work)
> }
> }
>
> -#ifdef CONFIG_PM_SLEEP
> /*
> * If set, call_usermodehelper_exec() will exit immediately returning -EBUSY
> * (used for preventing user land processes from being created after the user
> @@ -321,12 +320,6 @@ static void helper_unlock(void)
> if (atomic_dec_and_test(&running_helpers))
> wake_up(&running_helpers_waitq);
> }
> -#else /* CONFIG_PM_SLEEP */
> -#define usermodehelper_disabled 0
> -
> -static inline void helper_lock(void) {}
> -static inline void helper_unlock(void) {}
> -#endif /* CONFIG_PM_SLEEP */
>
> /**
> * call_usermodehelper_setup - prepare to call a usermode helper
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2011-05-10 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 4:58 linux-next: build failure after merge of the final tree (driver-core tree related) Stephen Rothwell
2011-05-09 9:34 ` Kay Sievers
2011-05-09 22:19 ` Rafael J. Wysocki
2011-05-09 23:18 ` Kay Sievers
2011-05-10 19:38 ` Rafael J. Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-08 8:02 Stephen Rothwell
2012-05-08 11:04 ` Kay Sievers
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=201105102138.45867.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=atu@dmeti.dp.ua \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).