linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: "Kani, Toshimitsu" <toshi.kani@hpe.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"hirofumi@mail.parknet.co.jp" <hirofumi@mail.parknet.co.jp>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: FIle copy to FAT FS on NVDIMM hits BUG_ON at fs/buffer.c:3305!
Date: Tue, 25 Jul 2017 16:22:47 -0600	[thread overview]
Message-ID: <20170725222247.GA26391@linux.intel.com> (raw)
In-Reply-To: <1501018096.2042.70.camel@hpe.com>

On Tue, Jul 25, 2017 at 09:37:38PM +0000, Kani, Toshimitsu wrote:
> Hi,
> 
> Copying files to vfat FS on an NVDIMM device hits
> BUG_ON(!PageLocked(page)) in try_to_free_buffers().  It happens on
> 4.13-rc1, and happens on older kernels as well.
> 
> A simple reproducer is shown below.  It is 100% reproducible on my
> setup (8GB of regular memory and 16GB of NVDIMM).  It usually hits in
> the 3rd or 4th file copy and does not repeat with the while-loop.�
> Interestingly, it hits only when an NVDIMM device is set as raw or
> memory mode.  It does not hit with sector mode.

Interesting, thanks for the report..  I was able to reproduce this in my KVM
setup with a virtualized NVDIMM using v4.12.  I also tried reproducing it with
BRD, and wasn't able.

I'll take a look.

  reply	other threads:[~2017-07-25 22:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 21:37 FIle copy to FAT FS on NVDIMM hits BUG_ON at fs/buffer.c:3305! Kani, Toshimitsu
2017-07-25 22:22 ` Ross Zwisler [this message]
2017-07-25 22:27   ` Kani, Toshimitsu
2017-07-26  8:21   ` Johannes Thumshirn
2017-07-26  9:23     ` OGAWA Hirofumi
2017-07-26 14:23       ` Ross Zwisler
2017-07-26 16:08         ` Dan Williams
2017-07-26 17:03           ` Christoph Hellwig
2017-07-26 17:11       ` Matthew Wilcox
2017-07-27 16:12         ` Kani, Toshimitsu
2017-07-27 18:03           ` Ross Zwisler
2017-07-27 18:20             ` Kani, Toshimitsu
2017-09-20 21:04           ` Kani, Toshimitsu

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=20170725222247.GA26391@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=toshi.kani@hpe.com \
    /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).