<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - journalctl crashes when journal is corrupted"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74714#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - journalctl crashes when journal is corrupted"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74714">bug 74714</a>
from <span class="vcard"><a class="email" href="mailto:janna.martl109@gmail.com" title="Janna Martl <janna.martl109@gmail.com>"> <span class="fn">Janna Martl</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=74714#c4">comment #4</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=74714#c3">comment #3</a>)
> > (In reply to <a href="show_bug.cgi?id=74714#c2">comment #2</a>)
> > > Is there any chance you could pass us the journal files triggering this?
> >
> > Do you think that it's journalctl getting confused? I thought that the
> > kernel is sending SIGBUS because it can't read the mmap'ed file.
>
> Oh, hmm, this is a bit confusing in the original bug report.
>
> Janna, the IO error you saw, did that happen when the file was corrupted, or
> when you viewed the file? In the latter case the SIGBUS is to be expected.
> In the former case this would be a bug in journalctl.</span >
I meant the latter. I'm pretty sure the files were corrupted before journalctl
got around to reading them, and the crash was caused by a read error. Sorry for
the confusion.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>