linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@oracle.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Oleg Nesterov <oleg@redhat.com>,
	Jamie Iles <jamie.iles@oracle.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: mips qemu test failures in -next due to "kthread: Fix use-after-free if kthread fork fails"
Date: Sun, 28 May 2017 13:45:13 +0200	[thread overview]
Message-ID: <dc237f28-a065-2eee-5c99-20e130c080e5@oracle.com> (raw)
In-Reply-To: <20170527175612.GA22714@roeck-us.net>

On 05/27/17 19:56, Guenter Roeck wrote:
> Hi,
> 
> my qemu testis of mips images are failing in -next. Symptom is a hang during
> boot; see http://kerneltests.org/builders/qemu-mips-next for some examples.
> 
> I bisected the problem in next-20170526. It points to commit 4d6501dce079c
> ("kthread: Fix use-after-free if kthread fork fails"). Reverting that patch
> fixes the problem.
> 
> Bisect log is attached.

Hi,

Thanks for the report and sorry for the breakage :-/

I can't immediately spot what's going wrong, but I am able to reproduce
it on mips so I will try to debug.

Are you sure it's this commit, though? I checked out linus/master and
I get a boot hang even after reverting it.


Vegard

  reply	other threads:[~2017-05-28 11:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27 17:56 mips qemu test failures in -next due to "kthread: Fix use-after-free if kthread fork fails" Guenter Roeck
2017-05-28 11:45 ` Vegard Nossum [this message]
2017-05-28 14:44   ` Guenter Roeck
2017-05-28 14:49   ` Vegard Nossum
2017-05-28 15:00     ` Guenter Roeck
2017-05-28 15:26     ` Guenter Roeck

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=dc237f28-a065-2eee-5c99-20e130c080e5@oracle.com \
    --to=vegard.nossum@oracle.com \
    --cc=jamie.iles@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=oleg@redhat.com \
    --cc=tglx@linutronix.de \
    /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).