From: Michal Hocko <mhocko@kernel.org>
To: Vineet Gupta <vineet.gupta1@synopsys.com>
Cc: "linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 2/2] ARC: show_regs: fix lockdep splat for good
Date: Fri, 21 Dec 2018 14:27:53 +0100 [thread overview]
Message-ID: <20181221132753.GB4842@dhcp22.suse.cz> (raw)
In-Reply-To: <20181221130404.GF16107@dhcp22.suse.cz>
On Fri 21-12-18 14:04:04, Michal Hocko wrote:
[...]
> Yes, but you are building on a broken concept I believe. What
> implications does re-enabling really have? Now you could reschedule and
> you can move to another CPU. Is this really safe? I believe that yes
> because the preemption disabling is simply bogus. Which doesn't sound
> like a proper justification, does it?
Well, thinking about it a bit more. What is the result of calling
preempt_enable outside of preempt_disabled section? E.g. __warn which
doesn't disable preemption AFAICS.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-12-21 13:27 UTC|newest]
Thread overview: 20+ 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 ` [PATCH 1/2] ARC: show_regs: avoid page allocator Vineet Gupta
2018-12-19 17:04 ` Eugeniy Paltsev
2018-12-19 17:36 ` Vineet Gupta
2018-12-20 1:16 ` Vineet Gupta
2018-12-20 13:30 ` Tetsuo Handa
2018-12-20 18:36 ` Vineet Gupta
2018-12-20 18:43 ` Vineet Gupta
2018-12-19 20:46 ` William Kucharski
2018-12-19 21:36 ` Vineet Gupta
2018-12-20 12:57 ` Michal Hocko
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-20 13:04 ` Michal Hocko
2018-12-20 18:45 ` Vineet Gupta
2018-12-21 13:04 ` Michal Hocko
2018-12-21 13:27 ` Michal Hocko [this message]
2018-12-21 17:55 ` Vineet Gupta
2018-12-21 17:55 ` Vineet Gupta
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=20181221132753.GB4842@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--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=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