From: Jeffrey Bastian <jbastian@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
Kees Cook <keescook@chromium.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Colin Ian King <colin.king@canonical.com>
Subject: Re: [Bug 209919] New: kernel BUG at mm/usercopy.c:99 from stress-ng procfs
Date: Thu, 29 Oct 2020 10:22:51 -0500 [thread overview]
Message-ID: <20201029152251.ls2wifd7rtczfvcc@tarantula.users.ipa.redhat.com> (raw)
In-Reply-To: <20201028163611.2d2cf82c0919ca4018741c97@linux-foundation.org>
On Wed, Oct 28, 2020 at 04:36:11PM -0700, Andrew Morton wrote:
>(switched to email. Please respond via emailed reply-to-all, not via the
>bugzilla web interface).
>
>On Wed, 28 Oct 2020 15:49:15 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
>> [ 984.279683] Call Trace:
>> [ 984.282581] __check_heap_object+0xe0/0x110
>> [ 984.287405] __check_object_size+0x136/0x150
>> [ 984.292347] proc_sys_call_handler+0x167/0x250
>> [ 984.297565] new_sync_read+0x108/0x180
>> [ 984.302082] vfs_read+0x174/0x1d0
>> [ 984.306126] ksys_read+0x58/0xd0
>> [ 984.310022] do_syscall_64+0x33/0x40
>> [ 984.314277] entry_SYSCALL_64_after_hwframe+0x44/0xa9
>
>Can we determine which /proc/sys entries these are?
Colin Ian King narrowed it down to
/proc/sys/kernel/sched_domain/cpu0/domain0/flags
and commit 5b9f8ff7b320a34af3dbcf04edb40d9b04f22f4a.
He has a proposed patch, too, that he'll be sending to the list soon.
See https://bugzilla.kernel.org/show_bug.cgi?id=209919#c9
Thanks for the quick debugging, Colin!
--
Jeff Bastian
Kernel QE - Hardware Enablement
Red Hat
next prev parent reply other threads:[~2020-10-29 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-209919-27@https.bugzilla.kernel.org/>
2020-10-28 23:36 ` Andrew Morton
2020-10-29 15:22 ` Jeffrey Bastian [this message]
2020-10-29 17:22 ` Jeffrey Bastian
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=20201029152251.ls2wifd7rtczfvcc@tarantula.users.ipa.redhat.com \
--to=jbastian@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=colin.king@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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