| To: | Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: real-time device BUG |
| From: | Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx> |
| Date: | Fri, 29 Jan 2016 16:40:36 -0700 |
| Cc: | xfs@xxxxxxxxxxx, Dave Chinner <david@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160129230531.GA29895@xxxxxxxxxxxxxxx> |
| References: | <20160129230531.GA29895@xxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.24 (2015-08-30) |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | real-time device BUG, Ross Zwisler |
|---|---|
| Next by Date: | Re: real-time device BUG, Eric Sandeen |
| Previous by Thread: | real-time device BUG, Ross Zwisler |
| Next by Thread: | Re: real-time device BUG, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |