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

2017-07-12 Thread Linus Torvalds
On Wed, Jul 12, 2017 at 9:09 AM, David Miller wrote: > > Al, please push this to Linus soon. I'll take it directly, Al is currently in Boston without a real computer methinks. Linus

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

2017-07-12 Thread David Miller
From: Meelis Roos Date: Wed, 12 Jul 2017 10:09:50 +0300 (EEST) >> From: Al Viro >> Date: Wed, 12 Jul 2017 04:59:45 +0100 >> >> > Again, my apologies for format of that all - I'm almost completely >> > off-net and while typing an ed script is feasible, context diff is >> > too far over the top.

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

2017-07-12 Thread Meelis Roos
> From: Al Viro > Date: Wed, 12 Jul 2017 04:59:45 +0100 > > > Again, my apologies for format of that all - I'm almost completely > > off-net and while typing an ed script is feasible, context diff is > > too far over the top. Usimg mutt in ssh session from android is > > not fun, to put it mildl

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

2017-07-11 Thread David Miller
From: Al Viro Date: Wed, 12 Jul 2017 04:59:45 +0100 > Again, my apologies for format of that all - I'm almost completely > off-net and while typing an ed script is feasible, context diff is > too far over the top. Usimg mutt in ssh session from android is > not fun, to put it mildly... Yes, t

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

2017-07-11 Thread 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 fff8 ip f774e154 (rpc > f774dfe8) sp 0001f7965a68 error 30002 in > li

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

2017-07-11 Thread David Miller
From: Meelis Roos 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

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

2017-07-11 Thread Meelis Roos
> 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)