From: Florian Fainelli <f.fainelli@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.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>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: mm: Facilitate debugging CONFIG_KUSER_HELPERS disabled
Date: Thu, 25 Oct 2018 11:50:43 -0700 [thread overview]
Message-ID: <a48601e2-dde2-47b8-b591-ffccdc9f1bf8@gmail.com> (raw)
In-Reply-To: <87tvl9nas6.fsf@xmission.com>
On 10/25/18 11:25 AM, Eric W. Biederman wrote:
> 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?
Yes, good point, thanks.
--
Florian
next prev parent reply other threads:[~2018-10-25 18:50 UTC|newest]
Thread overview: 7+ 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:25 ` Eric W. Biederman
2018-10-25 18:50 ` Florian Fainelli [this message]
2018-10-25 18:30 ` Souptick Joarder
2018-10-25 18:48 ` Florian Fainelli
2018-10-25 19:06 ` Souptick Joarder
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=a48601e2-dde2-47b8-b591-ffccdc9f1bf8@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=ebiederm@xmission.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tony@atomide.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).