On Fri, Dec 05, 2014 at 11:31:11AM -0800, Linus Torvalds wrote:
> On Fri, Dec 5, 2014 at 10:48 AM, Dave Jones <da...@redhat.com> wrote:
> >
> > In the meantime, I rebooted into the same kernel, and ran trinity
> > solely doing the lsetxattr syscalls.
>
> Any particular reason for the lsetxattr guess? Just the last call
> chain? I don't recognize it from the other traces, but maybe I just
> didn't notice.
yeah just a wild guess, just that that trace looked so.. clean.
> > The load was a bit lower, so I
> > cranked up the number of child processes to 512, and then this
> > happened..
>
> Ugh. "dump_trace()" being broken and looping forever? I don't actually
> believe it, because this isn't even on the exception stack (well, the
> NMI dumper is, but that one worked fine - this is the "nested" dumping
> of just the allocation call chain)
>
> Smells like more random callchains to me. Unless this one is repeatable.
>
> Limiting trinity to just lsetxattr is interesting. Did it make things
> fail faster?
It sure failed quickly, but not in the "machine is totally locked up"
sense, just "shit is all corrupted" sense. So it might be a completely different
thing, or it could be a different manifestation of a corruptor.
I guess we'll see how things go now that I marked it 'bad'.
I'll give it a quick run with just lsetxattr again just to see what
happens, but before I leave this one run over the weekend, I'll switch
it back to "do everything", and pick it up again on Monday.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
