From: Dave Jones <davej@codemonkey.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [4.14-rc7] task struct corruption after fork
Date: Mon, 30 Oct 2017 16:35:16 -0400 [thread overview]
Message-ID: <20171030203516.ttkflsnlusnvbx23@codemonkey.org.uk> (raw)
In-Reply-To: <CA+55aFzhXKFMzdjeqHn5Nz5vtMqgw_tCgrZ3DuYpgs4qqSL1qA@mail.gmail.com>
On Mon, Oct 30, 2017 at 11:59:30AM -0700, Linus Torvalds wrote:
> and that location would *almost* make sense in that it's the end of
> the same page that contained a "struct task_struct".
>
> Are you running with VMAP_STACK? Is there perhaps some stale code that
> ends up doing the old "stack pointer is in the same allocation as task
> struct"?
yeah, it's enabled.
> If you have the kernel symbols for that image, can you look up if any
> of those addresses look like any static kernel symbol addresses? Those
> things that have the pattern ffffffff8xxxxxxx might be symbol
> addresses and give us a clue about where the values came from.
it got clobbered by another build, but I managed to rebuild it from the
older config. Modulo modules that were loaded, things should be the same.
> ffffffff81172d1e r15
ffffffff81172d00 t usage_match
ffffffff81172d30 t HARDIRQ_verbose
> ffffffff8426daec r14
ffffffff841cee60 b lock_classes
ffffffff844eed00 B nr_lock_classes
> ffffed008b17e001 r13
> ffffffff811737e2 r12
ffffffff81173540 t __bfs
ffffffff81173970 t check_noncircular
> ffffffff8426dbe0 rbp
ffffffff841cee60 b lock_classes
ffffffff844eed00 B nr_lock_classes
> ffff880458bf0008 rbx
> ffffffff84590d00 r11
ffffffff841cee60 b lock_classes
ffffffff844eed00 B nr_lock_classes
> 5 r10
> ffffffff81172d00 r9
ffffffff81172d00 t usage_match
> 1 r8
> 1ffff1008b17dfed rax
> ffff880458bf00f0 rcx
> ffffed008b17dff9 rdx
> dffffc0000000000 rsi
> 41b58ab3 rdi
> ffffffff82a349a8 orig_eax
ffffffff828a7f40 R inat_primary_table
ffffffff82a42840 r POLY
> ffffffff81173540 rip
ffffffff81173540 t __bfs
> 5a5a5a5a5a5a5a5a
> ffffffff8450f080 flags
ffffffff844eed40 b list_entries
ffffffff846eed60 B nr_list_entries
So a bunch of lockdep stuff, and not much else afaics.
Dave
prev parent reply other threads:[~2017-10-30 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 14:11 Dave Jones
2017-10-30 18:59 ` Linus Torvalds
2017-10-30 20:35 ` Dave Jones [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=20171030203516.ttkflsnlusnvbx23@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®