All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mm: Facilitate debugging CONFIG_KUSER_HELPERS disabled
Date: Thu, 25 Oct 2018 13:25:45 -0500	[thread overview]
Message-ID: <87tvl9nas6.fsf@xmission.com> (raw)
In-Reply-To: <20181025180957.7900-1-f.fainelli@gmail.com> (Florian Fainelli's message of "Thu, 25 Oct 2018 11:09:55 -0700")

Florian Fainelli <f.fainelli@gmail.com> writes:

> Some software such as perf makes unconditional use of the special
> [vectors] page which is only provided when CONFIG_KUSER_HELPERS is
> enabled in the kernel.
>
> Facilitate the debugging of such situations by printing a debug message
> to the kernel log showing the task name and the faulting address.

Can't someone trigger this segv deliberately and spam the kerne log?
Doesn't this need something like printk_ratelimit or something to ensure
this message only gets printed once?

Eric

> Suggested-by: Russell King <rmk+kernel@armlinux.org.uk>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
>  arch/arm/mm/fault.c | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/mm/fault.c b/arch/arm/mm/fault.c
> index f4ea4c62c613..f17471fbc1c4 100644
> --- a/arch/arm/mm/fault.c
> +++ b/arch/arm/mm/fault.c
> @@ -173,6 +173,11 @@ __do_user_fault(struct task_struct *tsk, unsigned long addr,
>  		show_regs(regs);
>  	}
>  #endif
> +#ifndef CONFIG_KUSER_HELPERS
> +	if ((sig == SIGSEGV) && ((addr & PAGE_MASK) == 0xffff0000))
> +		printk(KERN_DEBUG "%s: CONFIG_KUSER_HELPERS disabled at 0x%08lx\n",
> +		       tsk->comm, addr);
> +#endif
>  
>  	tsk->thread.address = addr;
>  	tsk->thread.error_code = fsr;

WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, andrew@lunn.ch,
	Russell King <linux@armlinux.org.uk>,
	Tony Lindgren <tony@atomide.com>,
	Souptick Joarder <jrdr.linux@gmail.com>,
	linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH] ARM: mm: Facilitate debugging CONFIG_KUSER_HELPERS disabled
Date: Thu, 25 Oct 2018 13:25:45 -0500	[thread overview]
Message-ID: <87tvl9nas6.fsf@xmission.com> (raw)
In-Reply-To: <20181025180957.7900-1-f.fainelli@gmail.com> (Florian Fainelli's message of "Thu, 25 Oct 2018 11:09:55 -0700")

Florian Fainelli <f.fainelli@gmail.com> writes:

> Some software such as perf makes unconditional use of the special
> [vectors] page which is only provided when CONFIG_KUSER_HELPERS is
> enabled in the kernel.
>
> Facilitate the debugging of such situations by printing a debug message
> to the kernel log showing the task name and the faulting address.

Can't someone trigger this segv deliberately and spam the kerne log?
Doesn't this need something like printk_ratelimit or something to ensure
this message only gets printed once?

Eric

> Suggested-by: Russell King <rmk+kernel@armlinux.org.uk>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
>  arch/arm/mm/fault.c | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/mm/fault.c b/arch/arm/mm/fault.c
> index f4ea4c62c613..f17471fbc1c4 100644
> --- a/arch/arm/mm/fault.c
> +++ b/arch/arm/mm/fault.c
> @@ -173,6 +173,11 @@ __do_user_fault(struct task_struct *tsk, unsigned long addr,
>  		show_regs(regs);
>  	}
>  #endif
> +#ifndef CONFIG_KUSER_HELPERS
> +	if ((sig == SIGSEGV) && ((addr & PAGE_MASK) == 0xffff0000))
> +		printk(KERN_DEBUG "%s: CONFIG_KUSER_HELPERS disabled at 0x%08lx\n",
> +		       tsk->comm, addr);
> +#endif
>  
>  	tsk->thread.address = addr;
>  	tsk->thread.error_code = fsr;

  reply	other threads:[~2018-10-25 18:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25 18:09 [PATCH] ARM: mm: Facilitate debugging CONFIG_KUSER_HELPERS disabled Florian Fainelli
2018-10-25 18:09 ` Florian Fainelli
2018-10-25 18:25 ` Eric W. Biederman [this message]
2018-10-25 18:25   ` Eric W. Biederman
2018-10-25 18:50   ` Florian Fainelli
2018-10-25 18:50     ` Florian Fainelli
2018-10-25 18:30 ` Souptick Joarder
2018-10-25 18:30   ` Souptick Joarder
2018-10-25 18:48   ` Florian Fainelli
2018-10-25 18:48     ` Florian Fainelli
2018-10-25 19:06     ` Souptick Joarder
2018-10-25 19:06       ` Souptick Joarder
2018-10-25 21:20   ` Russell King - ARM Linux
2018-10-25 21:20     ` Russell King - ARM Linux

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=87tvl9nas6.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.