Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Meelis Roos <mroos@linux.ee>, John David Anglin <dave.anglin@bell.net>
Cc: linux-parisc@vger.kernel.org
Subject: Re: parisc 4.13-git, BUG: sleeping function called from invalid context at mm/slab.h:416
Date: Tue, 01 Aug 2017 07:26:14 -0700	[thread overview]
Message-ID: <1501597574.2736.1.camel@HansenPartnership.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1708011050580.27473@math.ut.ee>

On Tue, 2017-08-01 at 10:52 +0300, Meelis Roos wrote:
> > 
> > Since this code hasn't changed in a long time, it should be
> > possible to bisect problem.
> 
> I know the patch works, but out of curiosity I bisected it and found 
> that the BUG is brough out with the following commit. Seems to make 
> sense.

Yes, I guessed it would be something like that.  The bug was actually
always in our code; that commit just causes us to notice it.  Bisect
naturally takes you to that commit rather than the original problem one
(which is way back in history now).

James


      reply	other threads:[~2017-08-01 14:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-29 19:09 parisc 4.13-git, BUG: sleeping function called from invalid context at mm/slab.h:416 Meelis Roos
2017-07-29 19:53 ` John David Anglin
2017-07-29 20:27   ` James Bottomley
2017-07-30  6:47   ` Meelis Roos
2017-07-30 12:27     ` John David Anglin
2017-07-30 15:30       ` James Bottomley
2017-07-30 18:12         ` Meelis Roos
2017-07-30 18:21           ` John David Anglin
2017-07-30 18:37             ` James Bottomley
2017-07-30 18:53               ` Helge Deller
2017-07-30 19:27                 ` John David Anglin
2017-07-30 19:08               ` Meelis Roos
2017-08-01  7:52       ` Meelis Roos
2017-08-01 14:26         ` James Bottomley [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=1501597574.2736.1.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=linux-parisc@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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