From: Dave Chinner <david@fromorbit.com>
To: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: notify_change() WARN_ON being triggered on XFS.
Date: Tue, 2 Jun 2015 07:19:02 +1000 [thread overview]
Message-ID: <20150601211902.GD9143@dastard> (raw)
In-Reply-To: <20150527214448.GA14089@codemonkey.org.uk>
On Wed, May 27, 2015 at 05:44:48PM -0400, Dave Jones wrote:
> WARNING: CPU: 1 PID: 29887 at fs/attr.c:198 notify_change+0x2e6/0x390()
> CPU: 1 PID: 29887 Comm: trinity-c13 Not tainted 4.1.0-rc5-gelk-debug+ #1
> 0000000000000009 ffff880041fb7b28 ffffffff967685f0 ffff8800bf7d12b8
> 0000000000000000 ffff880041fb7b68 ffffffff9607eaaa ffff880041fb7b58
> 0000000000000a00 ffff880073442510 000000000000888f ffff8800a61c2698
> Call Trace:
> [<ffffffff967685f0>] dump_stack+0x4f/0x7b
> [<ffffffff9607eaaa>] warn_slowpath_common+0x8a/0xc0
> [<ffffffff9607eb9a>] warn_slowpath_null+0x1a/0x20
> [<ffffffff9622c3f6>] notify_change+0x2e6/0x390
> [<ffffffff9622a072>] file_remove_suid+0x92/0xb0
> [<ffffffff962311f2>] ? __mnt_drop_write_file+0x12/0x20
> [<ffffffff9622a138>] ? file_update_time+0xa8/0xf0
> [<ffffffffc04e936e>] xfs_file_aio_write_checks+0x11e/0x160 [xfs]
> [<ffffffffc04e9477>] xfs_file_dio_aio_write+0xc7/0x590 [xfs]
> [<ffffffff9676cca3>] ? mutex_lock_nested+0x283/0x440
> [<ffffffff9621318a>] ? pipe_wait+0x8a/0xb0
> [<ffffffffc04e9dd5>] xfs_file_write_iter+0x105/0x120 [xfs]
> [<ffffffff9620980d>] vfs_iter_write+0x6d/0xa0
> [<ffffffff962417e4>] iter_file_splice_write+0x264/0x3c0
> [<ffffffff962432a1>] SyS_splice+0x361/0x7d0
> [<ffffffff9619fba3>] ? context_tracking_user_exit+0x13/0x20
> [<ffffffff9677223c>] tracesys_phase2+0x84/0x89
There's a fix pending. Waiting on Al Viro to pick it up for the next
merge window...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2015-06-01 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 21:44 notify_change() WARN_ON being triggered on XFS Dave Jones
2015-06-01 21:19 ` Dave Chinner [this message]
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=20150601211902.GD9143@dastard \
--to=david@fromorbit.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.