Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1685481

Re: in:imklog segfault in 4.12+git on most sparc64's

From David Miller <davem@davemloft.net>
Newsgroups linux.kernel
Subject Re: in:imklog segfault in 4.12+git on most sparc64's
Date 2017-07-12 05:20 +0200
Message-ID <u2glX-2Cm-5@gated-at.bofh.it> (permalink)
References <u21PX-1KO-9@gated-at.bofh.it> <u21PX-1KO-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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?

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: in:imklog segfault in 4.12+git on most sparc64's Meelis Roos <mroos@linux.ee> - 2017-07-11 13:50 +0200
  Re: in:imklog segfault in 4.12+git on most sparc64's David Miller <davem@davemloft.net> - 2017-07-12 05:20 +0200
  Re: in:imklog segfault in 4.12+git on most sparc64's David Miller <davem@davemloft.net> - 2017-07-12 06:10 +0200
    Re: in:imklog segfault in 4.12+git on most sparc64's Meelis Roos <mroos@linux.ee> - 2017-07-12 09:20 +0200
      Re: in:imklog segfault in 4.12+git on most sparc64's David Miller <davem@davemloft.net> - 2017-07-12 18:10 +0200
        Re: in:imklog segfault in 4.12+git on most sparc64's Linus Torvalds <torvalds@linux-foundation.org> - 2017-07-12 18:20 +0200
  Re: in:imklog segfault in 4.12+git on most sparc64's Al Viro <viro@ZenIV.linux.org.uk> - 2017-07-12 06:10 +0200

csiph-web