From: Eric W. Biederman <ebiederm@xmission.com>
To: lkp@lists.01.org
Subject: Re: 4ce5f9c9e7 [ 1.323881] WARNING: CPU: 0 PID: 1 at mm/slab_common.c:1031 kmalloc_slab
Date: Wed, 10 Oct 2018 17:06:52 -0500 [thread overview]
Message-ID: <87h8htv4lf.fsf@xmission.com> (raw)
In-Reply-To: <87sh1dvmc5.fsf@xmission.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
ebiederm(a)xmission.com (Eric W. Biederman) writes:
> So I am flummoxed. I am reading through the code and I don't see
> anything that could trigger this, and when I ran the supplied reproducer
> it did not reproduce for me.
Even more so. With my tool chain the line that reports the failing
address is impossible.
[ 73.034423] RIP: 0010:copy_siginfo_from_user+0x4d/0xd0
With the supplied configureation my tool chain only has 0x30 bytes for
all of copy_siginfo_from_user. So I can't even begin to guess where
in that function things are failing.
Any additional information that you can provide would be a real help
in tracking down this strange failure.
Thank you,
Eric Biederman
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: kernel test robot <rong.a.chen@intel.com>
Cc: linux-kernel@vger.kernel.org, LKP <lkp@01.org>
Subject: Re: [LKP] 4ce5f9c9e7 [ 1.323881] WARNING: CPU: 0 PID: 1 at mm/slab_common.c:1031 kmalloc_slab
Date: Wed, 10 Oct 2018 17:06:52 -0500 [thread overview]
Message-ID: <87h8htv4lf.fsf@xmission.com> (raw)
In-Reply-To: <87sh1dvmc5.fsf@xmission.com> (Eric W. Biederman's message of "Wed, 10 Oct 2018 10:43:38 -0500")
ebiederm@xmission.com (Eric W. Biederman) writes:
> So I am flummoxed. I am reading through the code and I don't see
> anything that could trigger this, and when I ran the supplied reproducer
> it did not reproduce for me.
Even more so. With my tool chain the line that reports the failing
address is impossible.
[ 73.034423] RIP: 0010:copy_siginfo_from_user+0x4d/0xd0
With the supplied configureation my tool chain only has 0x30 bytes for
all of copy_siginfo_from_user. So I can't even begin to guess where
in that function things are failing.
Any additional information that you can provide would be a real help
in tracking down this strange failure.
Thank you,
Eric Biederman
next prev parent reply other threads:[~2018-10-10 22:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 2:06 4ce5f9c9e7 [ 1.323881] WARNING: CPU: 0 PID: 1 at mm/slab_common.c:1031 kmalloc_slab kernel test robot
2018-10-10 2:06 ` [LKP] " kernel test robot
2018-10-10 15:43 ` Eric W. Biederman
2018-10-10 15:43 ` [LKP] " Eric W. Biederman
2018-10-10 22:06 ` Eric W. Biederman [this message]
2018-10-10 22:06 ` Eric W. Biederman
2018-10-10 23:41 ` Sean Christopherson
2018-10-10 23:41 ` [LKP] " Sean Christopherson
2018-10-11 0:31 ` Sean Christopherson
2018-10-11 0:31 ` [LKP] " Sean Christopherson
2018-10-11 1:11 ` Eric W. Biederman
2018-10-11 1:11 ` [LKP] " Eric W. Biederman
2018-10-11 1:14 ` Eric W. Biederman
2018-10-11 1:14 ` [LKP] " Eric W. Biederman
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=87h8htv4lf.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.