From: Michael Ellerman <mpe@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linuxppc-dev@ozlabs.org
Cc: Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] powerpc/mm: Use VM_WARN_ONCE() for irqs disabled check
Date: Tue, 28 Jun 2016 21:13:04 +1000 [thread overview]
Message-ID: <1467112384.16036.1.camel@ellerman.id.au> (raw)
In-Reply-To: <87furx6189.fsf@skywalker.in.ibm.com>
On Tue, 2016-06-28 at 16:15 +0530, Aneesh Kumar K.V wrote:
> Michael Ellerman <mpe@ellerman.id.au> writes:
> > diff --git a/arch/powerpc/include/asm/pgtable.h b/arch/powerpc/include/asm/pgtable.h
> > index ee09e99097f0..651848039dc4 100644
> > --- a/arch/powerpc/include/asm/pgtable.h
> > +++ b/arch/powerpc/include/asm/pgtable.h
> > @@ -71,10 +71,8 @@ pte_t *__find_linux_pte_or_hugepte(pgd_t *pgdir, unsigned long ea,
> > static inline pte_t *find_linux_pte_or_hugepte(pgd_t *pgdir, unsigned long ea,
> > bool *is_thp, unsigned *shift)
> > {
> > - if (!arch_irqs_disabled()) {
> > - pr_info("%s called with irq enabled\n", __func__);
> > - dump_stack();
> > - }
> > + VM_WARN_ONCE(!arch_irqs_disabled(),
> > + "find_linux_pte_or_hugepte() called with irqs enabled!\n");
> > return __find_linux_pte_or_hugepte(pgdir, ea, is_thp, shift);
> > }
> >
>
> https://lkml.kernel.org/r/574de240.uG8/5OM2Lu9RY6K+%akpm@linux-foundation.orgdd
>
> Isn't this patch already part of -mm.
Ugh, yes. I missed that you'd already sent it.
> And why ONCE, we want to find about all the wrong usage.
Sure, but if you hit it repeatedly in a common path you're likely to kill the
box just with console spam.
But I don't mind. Ignore this version.
cheers
prev parent reply other threads:[~2016-06-28 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 6:38 [PATCH] powerpc/mm: Use VM_WARN_ONCE() for irqs disabled check Michael Ellerman
2016-06-28 10:45 ` Aneesh Kumar K.V
2016-06-28 11:13 ` Michael Ellerman [this message]
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=1467112384.16036.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.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 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).