From: Boaz Harrosh <boaz@plexistor.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Matthew Wilcox <willy@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org
Subject: Re: [Linux-nvdimm] [GIT PULL] PMEM driver for v4.1
Date: Wed, 27 May 2015 11:26:21 +0300 [thread overview]
Message-ID: <55657FAD.4020900@plexistor.com> (raw)
In-Reply-To: <20150527081156.GA25375@lst.de>
On 05/27/2015 11:11 AM, Christoph Hellwig wrote:
> On Wed, May 27, 2015 at 11:10:21AM +0300, Boaz Harrosh wrote:
>> Hu funny I just looked and I see with ./check auto I get
>> generic/018 1s ... [not run] defragmentation not supported for fstype "m1fs"
>> generic/020 0s ... 0s
>>
>> 019 is not even printing a skip. But if I run it directly I get:
>> generic/019 [not run] /sys/kernel/debug/fail_make_request not found. \
>> Seems that CONFIG_FAIL_MAKE_REQUEST kernel config option not enabled
>>
>> So my bad, I will try to properly configure and recreate this failure here
>> as well.
>
> It fails I/O above the driver. Any failure in generic/019 is very unlіkely
> to be driver related.
>
Hm, so then that would be expected right?
__blkdev_put fails to WARN_ON_ONCE(write_inode_now(inode, true))
because the test tells the Kernel to fail IO requests.
__blkdev_put then complains because it has no way to report
the error back to caller.
I would then say that 019 test should expect that this might
happen. Or it should somehow make sure to remove the requests
block before the umount.
Thanks
Boaz
next prev parent reply other threads:[~2015-05-27 8:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 9:33 [GIT PULL] PMEM driver for v4.1 Ingo Molnar
2015-04-13 9:35 ` Christoph Hellwig
2015-04-13 10:45 ` Ingo Molnar
2015-04-13 11:11 ` [Linux-nvdimm] " Yigal Korman
2015-04-13 17:19 ` Christoph Hellwig
2015-04-14 6:41 ` Boaz Harrosh
2015-04-13 12:21 ` Boaz Harrosh
2015-04-13 12:35 ` Ingo Molnar
2015-04-13 13:36 ` Boaz Harrosh
2015-04-13 17:22 ` Christoph Hellwig
2015-04-13 17:18 ` Christoph Hellwig
2015-04-14 12:41 ` Ingo Molnar
2015-04-14 13:45 ` Boaz Harrosh
2015-04-14 14:08 ` [Linux-nvdimm] " Elliott, Robert (Server Storage)
2015-04-14 16:34 ` Dan Williams
2015-04-14 21:46 ` Elliott, Robert (Server Storage)
2015-04-15 8:03 ` Ingo Molnar
2015-04-14 16:04 ` Dan Williams
2015-04-15 8:45 ` Ingo Molnar
2015-04-16 4:31 ` Dan Williams
2015-04-17 6:38 ` Christoph Hellwig
2015-04-18 15:42 ` Linus Torvalds
2015-05-25 18:16 ` [Linux-nvdimm] " Matthew Wilcox
2015-05-25 18:30 ` Ingo Molnar
2015-05-26 8:41 ` Boaz Harrosh
2015-05-26 19:31 ` Matthew Wilcox
2015-05-27 8:10 ` Boaz Harrosh
2015-05-27 8:11 ` Christoph Hellwig
2015-05-27 8:26 ` Boaz Harrosh [this message]
2015-05-27 7:50 ` Ingo Molnar
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=55657FAD.4020900@plexistor.com \
--to=boaz@plexistor.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=willy@linux.intel.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).