From: Song Liu <song@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
"Daniel Díaz" <daniel.diaz@linaro.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
"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: Fri, 23 Oct 2020 14:15:53 -0700 [thread overview]
Message-ID: <CAPhsuW6wZRVoT3Bu6YBVjWVm6JBz9n6_RoZKGM7KrVAXx89SFQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wjyp3Y_vXJwvoieBJpmmTrs46kc4GKbq5x_nvonHvPJBw@mail.gmail.com>
On Fri, Oct 23, 2020 at 10:51 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Fri, Oct 23, 2020 at 10:00 AM Naresh Kamboju
> <naresh.kamboju@linaro.org> wrote:
> >
> > [Old patch from yesterday]
> >
> > After applying your patch on top on linux next tag 20201015
> > there are two observations,
> > 1) i386 build failed. please find build error build
>
> Yes, this was expected. That patch explicitly only works on x86-64,
> because 32-bit needs the double register handling for 64-bit values
> (mainly loff_t).
>
> > 2) x86_64 kasan test PASS and the reported error not found.
>
> Ok, good. That confirms that the problem you reported is indeed the
> register allocation.
>
> The patch I sent an hour ago (the one based on Rasmus' one from
> yesterday) should fix things too, and - unlike yesterday's - work on
> 32-bit.
>
> But I'll wait for confirmation (and hopefully a sign-off from Rasmus
> so that I can give him authorship) before actually committing it.
>
> Linus
My test vm failed to boot since
commit d55564cfc222326e944893eff0c4118353e349ec
x86: Make __put_user() generate an out-of-line call
The patch also fixed it.
Thanks!
Song
prev parent reply other threads:[~2020-10-23 21:16 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 ` [LTP] " Daniel Díaz
2020-10-23 3:05 ` 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 [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=CAPhsuW6wZRVoT3Bu6YBVjWVm6JBz9n6_RoZKGM7KrVAXx89SFQ@mail.gmail.com \
--to=song@kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=daniel.diaz@linaro.org \
--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 \
/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).