From: David Miller <davem@davemloft.net>
To: mroos@linux.ee
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: in:imklog segfault in 4.12+git on most sparc64's
Date: Tue, 11 Jul 2017 20:13:40 -0700 (PDT) [thread overview]
Message-ID: <20170711.201340.349852191942631669.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1707111441480.31569@math.ut.ee>
From: Meelis Roos <mroos@linux.ee>
Date: Tue, 11 Jul 2017 14:48:27 +0300 (EEST)
>> I tested yesterdays git with 4.13 sparc merge on a big bunch of my test
>> machines.
>>
>> Good news: the timestamps starting from boot seem to work on all the
>> machines, starting with Ultra 1 and Ultra 2.
>>
>> Bad news: all working sun4u machines have the following line in dmesg
>> (PID varies):
>> in:imklog[1036]: segfault at 49 ip 0000000000035bb0 (rpc 00000000f779dfa0) sp 00000002f7a78818 error 30002 in rsyslogd[10000+88000]
>>
>> This is with Debian unstable 32-bit userland as of 2015 summer. It did
>> not happen with 4.12.
>
> I bisected it to the commit below. CC Al Viro.
>
> In following commits around this one (some bisect steps before, and the
> last step) the crashes were slightly different from the original crash
> yersterday, like
>
> in:imuxsock[1606]: segfault at fffffff8 ip 00000000f774e154 (rpc 00000000f774dfe8) sp 00000001f7965a68 error 30002 in libc-2.19.so[f76cc000+16a000]
>
> but this was the first commit introducing the crashes.
>
> d9e968cb9f849770288f5fde3d8d3a5f7e339052 is the first bad commit
> commit d9e968cb9f849770288f5fde3d8d3a5f7e339052
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date: Wed May 31 04:33:51 2017 -0400
>
> getrlimit()/setrlimit(): move compat to native
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>
> :040000 040000 5e1a0c25f4554ccdc824b18dc50078d379cdbf9a
> 6d820451a388c5771a2a410578365d14a0194e4e M kernel
I can't figure out what is wrong in this change, except that it does
two things at once.
It moves code, and changes it at the same time. That should have been
done in two changes.
Because of that, we can't tell which of the two things introduced the
regression.
Al?
next prev parent reply other threads:[~2017-07-12 3:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.2.20.1707101111290.5280@math.ut.ee>
2017-07-11 11:48 ` Meelis Roos
2017-07-12 3:13 ` David Miller [this message]
2017-07-12 3:59 ` Al Viro
2017-07-12 4:09 ` David Miller
2017-07-12 7:09 ` Meelis Roos
2017-07-12 16:09 ` David Miller
2017-07-12 16:14 ` Linus Torvalds
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=20170711.201340.349852191942631669.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=sparclinux@vger.kernel.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
all inboxes | Powered by JetHome®