From: "Daniel Díaz" <daniel.diaz@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
zenglg.jy@cn.fujitsu.com,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Viresh Kumar <viresh.kumar@linaro.org>, X86 ML <x86@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-mm <linux-mm@kvack.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
kasan-dev <kasan-dev@googlegroups.com>,
Dmitry Vyukov <dvyukov@google.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
Ingo Molnar <mingo@redhat.com>, LTP List <ltp@lists.linux.it>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [LTP] mmstress[1309]: segfault at 7f3d71a36ee8 ip 00007f3d77132bdf sp 00007f3d71a36ee8 error 4 in libc-2.27.so[7f3d77058000+1aa000]
Date: Thu, 22 Oct 2020 20:36:22 -0500 [thread overview]
Message-ID: <CAEUSe78A4fhsyF6+jWKVjd4isaUeuFWLiWqnhic87BF6cecN3w@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wi=sf4WtmZXgGh=nAp4iQKftCKbdQqn56gjifxWNpnkxw@mail.gmail.com>
Hello!
On Thu, 22 Oct 2020 at 19:11, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Oct 22, 2020 at 4:43 PM Linus Torvalds
> Would you mind sending me the problematic vmlinux file in private (or,
> likely better - a pointer to some place I can download it, it's going
> to be huge).
The kernel Naresh originally referred to is here:
https://builds.tuxbuild.com/SCI7Xyjb7V2NbfQ2lbKBZw/
Greetings!
Daniel Díaz
daniel.diaz@linaro.org
next prev parent reply other threads:[~2020-10-23 1:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 16:58 mmstress[1309]: segfault at 7f3d71a36ee8 ip 00007f3d77132bdf sp 00007f3d71a36ee8 error 4 in libc-2.27.so[7f3d77058000+1aa000] Naresh Kamboju
2020-10-21 17:05 ` Linus Torvalds
2020-10-21 17:22 ` Naresh Kamboju
2020-10-22 20:55 ` Naresh Kamboju
2020-10-22 23:43 ` Linus Torvalds
2020-10-23 0:11 ` Linus Torvalds
2020-10-23 0:22 ` Linus Torvalds
2020-10-23 1:36 ` Daniel Díaz [this message]
2020-10-23 3:05 ` [LTP] " Linus Torvalds
2020-10-23 5:02 ` Sean Christopherson
2020-10-23 7:14 ` Rasmus Villemoes
2020-10-23 15:54 ` Linus Torvalds
2020-10-23 16:32 ` Linus Torvalds
2020-10-23 17:50 ` Naresh Kamboju
2020-10-23 15:52 ` Linus Torvalds
2020-10-23 17:00 ` Naresh Kamboju
2020-10-23 17:50 ` Linus Torvalds
2020-10-23 21:15 ` Song Liu
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=CAEUSe78A4fhsyF6+jWKVjd4isaUeuFWLiWqnhic87BF6cecN3w@mail.gmail.com \
--to=daniel.diaz@linaro.org \
--cc=christian.brauner@ubuntu.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viresh.kumar@linaro.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=zenglg.jy@cn.fujitsu.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).