linux-kernel - Re: [PATCH 2/2] kprobes: check CONFIG_FREEZER instead of CONFIG

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: <alpine.LFD.2.00.0901091530090.16697@localhost.localdomain>
Date:	Fri, 09 Jan 2009 15:30:56 -0500 (EST)
From:	Len Brown <lenb@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	pm list <linux-pm@...ts.linux-foundation.org>,
	Pavel Machek <pavel@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Cheng Renquan <crquan@...il.com>
Subject: Re: [PATCH 2/2] kprobes: check CONFIG_FREEZER instead of CONFIG_PM

> > Check CONFIG_FREEZER instead of CONFIG_PM because kprobe booster
> > depends on freeze_processes() and thaw_processes() when CONFIG_PREEMPT=y.
> > 
> > This fixes a linkage error which occurs when CONFIG_PREEMPT=y, CONFIG_PM=y
> > and CONFIG_FREEZER=n.
> > 
> > Reported-by: Cheng Renquan <crquan@...il.com>
> > Signed-off-by: Masami Hiramatsu <mhiramat@...hat.com>
> > Signed-off-by: Rafael J. Wysocki <rjw@...k.pl>
> > ---
> >  arch/ia64/kernel/kprobes.c |    2 +-
> >  arch/x86/kernel/kprobes.c  |    2 +-
> >  kernel/kprobes.c           |    2 +-
> >  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> looks good, the x86 bits:
> 
> Acked-by: Ingo Molnar <mingo@...e.hu>

man, we have too many config options:-)

applied.
thanks,
Len Brown, Intel Open Source Technology Center


--
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/