From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: real-time device BUG
Date: Fri, 29 Jan 2016 16:40:36 -0700 [thread overview]
Message-ID: <20160129234036.GA24929@linux.intel.com> (raw)
In-Reply-To: <20160129230531.GA29895@linux.intel.com>
On Fri, Jan 29, 2016 at 04:05:31PM -0700, Ross Zwisler wrote:
> Today I was trying to get real-time devices working with XFS, and both a
> manual pwrite() to a real-time device and xfs_rtcp end up with a lockdep spat
> followed by a kernel BUG. This behavior is consistent between kernel versions
> v4.4 and v4.5-rc1. I initially found this using some pmem block devices, but
> it also happens with BRD.
This also happens with an mmap on the real-time file followed by a write.
Essentially I think that any path that tries to allocate a block for the real
time file his this same BUG.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-01-29 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 23:05 real-time device BUG Ross Zwisler
2016-01-29 23:40 ` Ross Zwisler [this message]
2016-01-30 3:11 ` Eric Sandeen
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=20160129234036.GA24929@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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