From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: <adilger.kernel@dilger.ca>, <jack@suse.cz>,
<linux-fsdevel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513
Date: Tue, 5 Mar 2019 16:33:48 -0500 [thread overview]
Message-ID: <20190305213348.GC6323@mit.edu> (raw)
In-Reply-To: <20190304231426.GA6191@amd>
On Tue, Mar 05, 2019 at 12:14:26AM +0100, Pavel Machek wrote:
> Hi!
>
> > (Adding linux-mm and moving linux-ext4 and linux-kernel to the bcc
> > list...)
>
> Umm. So I ... bcc them too?
Nah, I bcc'ed them so that people on those lists would understand that
I had dropped them from thread because it probably isn't appropriate
to include them on the thread.
> > Do you have a reliable repro for this? If so, the next step would be
> > to bisect...
>
> It happened just once... so I don't yet know.
>
> I'm not even sure what file was affected. unison was showing some kind
> of png from openstreetmap cache, but I could read it using md5sum just
> fine.
>
> -next is normally pretty boring, but it seems to get pretty
> interesting around -final release...
OK, let's see if anyone else reports a similar failure.
- Ted
prev parent reply other threads:[~2019-03-05 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190304160255.GA6914@amd>
2019-03-04 22:32 ` 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513 Theodore Y. Ts'o
[not found] ` <20190304231426.GA6191@amd>
2019-03-05 21:33 ` Theodore Y. Ts'o [this message]
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=20190305213348.GC6323@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).