linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 4 Mar 2019 17:32:32 -0500	[thread overview]
Message-ID: <20190304223232.GA6323@mit.edu> (raw)
In-Reply-To: <20190304160255.GA6914@amd>

(Adding linux-mm and moving linux-ext4 and linux-kernel to the bcc
list...)

On Mon, Mar 04, 2019 at 05:02:55PM +0100, Pavel Machek wrote:
> 
> This happened on trying to sync filesystems with unison:
> 
> Any ideas?
> 
> Should I be forcing fsck soon?
> 								Pavel
> 
> [12717.827444] ------------[ cut here ]------------
> [12717.827465] kernel BUG at fs/inode.c:513!

It seems unlikely that fsck is going to help.  The BUG_ON in question
appears to be:

	BUG_ON(inode->i_data.nrexceptional);

This is an in-memory accounting variable which seems to be related to
tracking DAX and shadow page entries --- and it seems very unlikely to
be the sort of thing triggered by an on-disk corruption.

Do you have a reliable repro for this?  If so, the next step would be
to bisect...

					- Ted


       reply	other threads:[~2019-03-04 22:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190304160255.GA6914@amd>
2019-03-04 22:32 ` Theodore Y. Ts'o [this message]
     [not found]   ` <20190304231426.GA6191@amd>
2019-03-05 21:33     ` 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513 Theodore Y. Ts'o

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=20190304223232.GA6323@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).