| To: | Dave Jones <davej@xxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 3.14-rc2 XFS backtrace because irqs_disabled. |
| From: | Al Viro <viro@xxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 12 Feb 2014 01:09:41 +0000 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140212004403.GA17129@xxxxxxxxxx> |
| References: | <20140211172707.GA1749@xxxxxxxxxx> <20140211210841.GM13647@dastard> <52FA9ADA.9040803@xxxxxxxxxxx> <20140212004403.GA17129@xxxxxxxxxx> |
| Sender: | Al Viro <viro@xxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Tue, Feb 11, 2014 at 07:44:03PM -0500, Dave Jones wrote: > The 'good' news is I seem to be able to reproduce it fairly quickly. > I've seen it 3-4 times this afternoon. (Always from the coredump path) > > I was on vacation last week, but I wasn't hitting this before then, so it's a > fairly recent change that's introduced this. Slap the check in vfs_create(), see if interrupts had been disabled by it or by something in ->create(). Since it's reproducible... |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 3.14-rc2 XFS backtrace because irqs_disabled., Dave Jones |
|---|---|
| Next by Date: | Особенности приема на работу иностранных работников, ИНСПЕКТОР ПО КАДРАМ |
| Previous by Thread: | Re: 3.14-rc2 XFS backtrace because irqs_disabled., Dave Jones |
| Next by Thread: | Re: 3.14-rc2 XFS backtrace because irqs_disabled., Linus Torvalds |
| Indexes: | [Date] [Thread] [Top] [All Lists] |