linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Stephan Mueller <smueller@chronox.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	Jet Chen <jet.chen@intel.com>, Su Tao <tao.su@intel.com>,
	Yuanhan Liu <yuanhan.liu@intel.com>, LKP <lkp@01.org>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	aris@redhat.com, aquini@redhat.com
Subject: Re: [crypto] BUG: unable to handle kernel paging request at ffff88000bb88000
Date: Mon, 30 Jun 2014 13:31:26 +0800	[thread overview]
Message-ID: <20140630053126.GA13887@localhost> (raw)
In-Reply-To: <42550233.Kxs179MjQV@myon.chronox.de>

Hi Stephan,

On Sun, Jun 29, 2014 at 09:45:48PM +0200, Stephan Mueller wrote:
> Am Sonntag, 29. Juni 2014, 22:52:46 schrieb Fengguang Wu:
> 
> Hi Fengguang,
> 
> > Greetings,
> > 
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> 
> May I ask whether there is anything special in your kernel config?

It's an x86_64 randconfig. You may find it in the attachment of the
original report email.

> This very bug should have been triggered already in all previous code levels! 
> I am seriously wondering why this bug was not triggered before -- does kalloc 
> somehow allocates more memory than you requested? And only your specific 
> kernel config made kalloc to allocate the exact amount of memory that was 
> requested?

Yeah the bug may have been triggered in other places. If you see
anything valuable from this bisect result, it would be great. Judging
from the comparison of 64d1cdfbe2 and its parent commit 3332ee2a17,
it's pretty reproducible, so easy to verify the possible fixes.

+----------------------------------------------------------------------------+------------+------------+
|                                                                            | 3332ee2a17 | 64d1cdfbe2 |
+----------------------------------------------------------------------------+------------+------------+
| boot_successes                                                             | 81         | 3          |
| boot_failures                                                              | 0          | 23         |
| BUG:unable_to_handle_kernel_paging_request                                 | 0          | 20         |
| Oops                                                                       | 0          | 19         |
| RIP:kzfree                                                                 | 0          | 15         |
| WARNING:CPU:PID:at_kernel/rcu/tree.c:rcu_do_batch()                        | 0          | 9          |
| backtrace:cryptomgr_test                                                   | 0          | 18         |
| backtrace:cpu_startup_entry                                                | 0          | 3          |
| kernel_BUG_at_include/linux/mm.h                                           | 0          | 1          |
...

Thanks,
Fengguang

  reply	other threads:[~2014-06-30  5:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 14:52 [crypto] BUG: unable to handle kernel paging request at ffff88000bb88000 Fengguang Wu
2014-06-29 14:56 ` [crypto] kernel BUG at kernel/cred.c:790 Fengguang Wu
2014-06-29 19:45 ` [crypto] BUG: unable to handle kernel paging request at ffff88000bb88000 Stephan Mueller
2014-06-30  5:31   ` Fengguang Wu [this message]
2014-06-30 13:39     ` Stephan Mueller

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=20140630053126.GA13887@localhost \
    --to=fengguang.wu@intel.com \
    --cc=aquini@redhat.com \
    --cc=aris@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jet.chen@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=smueller@chronox.de \
    --cc=tao.su@intel.com \
    --cc=yuanhan.liu@intel.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).