| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS assertion from truncate. (3.10-rc2) |
| From: | Dave Jones <davej@xxxxxxxxxx> |
| Date: | Tue, 21 May 2013 19:40:16 -0400 |
| Cc: | Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20130521233429.GW29466@dastard> |
| Mail-followup-to: | Dave Jones <davej@xxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| References: | <20130521225257.GA12713@xxxxxxxxxx> <20130521233429.GW29466@dastard> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Wed, May 22, 2013 at 09:34:29AM +1000, Dave Chinner wrote:
> On Tue, May 21, 2013 at 06:52:57PM -0400, Dave Jones wrote:
> > [ 464.210598] XFS: Assertion failed: (mask &
> > (ATTR_MODE|ATTR_UID|ATTR_GID|ATTR_ATIME|ATTR_ATIME_SET|
> > ATTR_MTIME_SET|ATTR_KILL_SUID|ATTR_KILL_SGID|
> > ATTR_KILL_PRIV|ATTR_TIMES_SET)) == 0, file: fs/xfs/xfs_iops.c, line: 719
>
> Never seen that fire before, but this is why we have ASSERT()s like
> this - we're being handed something by the VFS we don't expect...
>
> Can you give me some context of the file permissions before the
> syscall and what the syscall parameters are? i.e. is this likely to
> be trying to strip SUID/SGID during the truncate operation?
no idea tbh. Is there something I can add to that assert to dump
which file it was triggered by ?
Dave
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [BUG] XFS: Assertion failed: atomic_read(&pag->pag_ref) == 0, file: fs/xfs/xfs_mount.c, line: 272, Dave Chinner |
|---|---|
| Next by Date: | Re: XFS assertion from truncate. (3.10-rc2), Dave Chinner |
| Previous by Thread: | Re: XFS assertion from truncate. (3.10-rc2), Dave Chinner |
| Next by Thread: | Re: XFS assertion from truncate. (3.10-rc2), Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |