From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Vineet Gupta <vineet.gupta1@synopsys.com>,
Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH 1/2] ARC: show_regs: avoid page allocator
Date: Thu, 20 Dec 2018 22:30:08 +0900 [thread overview]
Message-ID: <e2d2c160-0ef6-5504-7824-032a5c70fa7f@I-love.SAKURA.ne.jp> (raw)
Message-ID: <20181220133008.GbEQjjTeolBC_IFDlk4XvcyPiAn1a5X51R43jKQqVzk@z> (raw)
In-Reply-To: <49f9edc9-87ee-1efc-58f8-b0d9a52c8a49@synopsys.com>
On 2018/12/20 10:16, Vineet Gupta wrote:
> On 12/19/18 9:04 AM, Eugeniy Paltsev wrote:
>> As I can see x86 use print_vma_addr() in their show_signal_msg()
>> function which allocate page with __get_free_page(GFP_NOWAIT);
>
> Indeed with that the __get_free_page() lockdep splat is gone.
>
> There's a different one now hence my other patch.
>
> | [ARCLinux]# ./segv-null-ptr
> | potentially unexpected fatal signal 11.
> | BUG: sleeping function called from invalid context at kernel/fork.c:1011
> | in_atomic(): 1, irqs_disabled(): 0, pid: 70, name: segv-null-ptr
> | no locks held by segv-null-ptr/70.
> | CPU: 0 PID: 70 Comm: segv-null-ptr Not tainted 4.18.0+ #69
> |
> | Stack Trace:
> | arc_unwind_core+0xcc/0x100
> | ___might_sleep+0x17a/0x190
> | mmput+0x16/0xb8
Then, does mmput_async() help?
> | show_regs+0x52/0x310
> | get_signal+0x5ee/0x610
> | do_signal+0x2c/0x218
> | resume_user_mode_begin+0x90/0xd8
next prev parent reply other threads:[~2018-12-20 13:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 18:53 [PATCH 0/2] ARC show_regs fixes Vineet Gupta
2018-12-18 18:53 ` Vineet Gupta
2018-12-18 18:53 ` [PATCH 1/2] ARC: show_regs: avoid page allocator Vineet Gupta
2018-12-18 18:53 ` Vineet Gupta
2018-12-19 17:04 ` Eugeniy Paltsev
2018-12-19 17:04 ` Eugeniy Paltsev
2018-12-19 17:36 ` Vineet Gupta
2018-12-19 17:36 ` Vineet Gupta
2018-12-20 1:16 ` Vineet Gupta
2018-12-20 1:16 ` Vineet Gupta
2018-12-20 13:30 ` Tetsuo Handa [this message]
2018-12-20 13:30 ` Tetsuo Handa
2018-12-20 18:36 ` Vineet Gupta
2018-12-20 18:36 ` Vineet Gupta
2018-12-20 18:43 ` Vineet Gupta
2018-12-20 18:43 ` Vineet Gupta
2018-12-19 20:46 ` William Kucharski
2018-12-19 20:46 ` William Kucharski
2018-12-19 21:36 ` Vineet Gupta
2018-12-19 21:36 ` Vineet Gupta
2018-12-20 12:57 ` Michal Hocko
2018-12-20 12:57 ` Michal Hocko
2018-12-20 18:38 ` Vineet Gupta
2018-12-20 18:38 ` Vineet Gupta
2018-12-18 18:53 ` [PATCH 2/2] ARC: show_regs: fix lockdep splat for good Vineet Gupta
2018-12-18 18:53 ` Vineet Gupta
2018-12-20 13:04 ` Michal Hocko
2018-12-20 13:04 ` Michal Hocko
2018-12-20 18:45 ` Vineet Gupta
2018-12-20 18:45 ` Vineet Gupta
2018-12-21 13:04 ` Michal Hocko
2018-12-21 13:04 ` Michal Hocko
2018-12-21 13:27 ` Michal Hocko
2018-12-21 13:27 ` Michal Hocko
2018-12-21 17:55 ` Vineet Gupta
2018-12-21 17:55 ` Vineet Gupta
2018-12-24 19:10 ` Michal Hocko
2018-12-24 19:10 ` Michal Hocko
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=e2d2c160-0ef6-5504-7824-032a5c70fa7f@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=eugeniy.paltsev@synopsys.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mhocko@kernel.org \
--cc=peterz@infradead.org \
--cc=vineet.gupta1@synopsys.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).