All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	linux-fsdevel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: fs: gpf in simple_setattr
Date: Tue, 25 Mar 2014 20:12:48 -0400	[thread overview]
Message-ID: <53321B80.4070108@oracle.com> (raw)
In-Reply-To: <20140325211229.GA27422@quack.suse.cz>

On 03/25/2014 05:12 PM, Jan Kara wrote:
> On Tue 25-03-14 13:51:11, Sasha Levin wrote:
>> On 03/25/2014 01:33 PM, Jan Kara wrote:
>>> On Mon 24-03-14 20:44:14, Sasha Levin wrote:
>>>> On 03/24/2014 05:48 PM, Jan Kara wrote:
>>>>>>> [  339.948946] ** 4194304 ffff8805ac03ba38 [eventpoll] ffff8806ec051fe0
>>>>>>> [eventpoll] ffffffff84666040 ffff88056c73e7b0           (null)
>>>>>    OK, great. So finally we have something useful. We know we have problems
>>>>> with [eventpoll] dentry. That is actually a special filesystem not mounted
>>>>> anywhere - likely you get to that dentry through/proc/<pid>/fd/. Now
>>>>> eventpoll is interesting because it uses single anon inode for all
>>>>> eventpoll instances. And that inode should stay in place as long as
>>>>> eventpoll filesystem exists. So it's not clear how come that inode is
>>>>> freed. The basic check of handling of inode use count didn't find anything
>>>>> suspicious. But I can check in more detail and if I fail, we now have a
>>>>> pretty narrow area where to look...
>>>>
>>>> Seems like it's not specific to eventpoll, I saw the same error message with
>>>> "eventfd" and "perf_event".
>>>    Yup, all these use anon_inode_getfile() so it all points to the fact that
>>> for some reason we freed anon_inode_inode. But I don't see where the
>>> problem is. Can you maybe make 'anon_inode_inode' external to
>>> fs/anon_inodes.c and dump stack for all iput() calls to anon_inode_inode?
>>> There must be some suckers which don't belong there...
>>
>> Okay, this is straightforward. It happened right after boot so we're lucky.
>>
>> I'm also looking into that, but odds you'll spot the issue faster than me.
>    Can you try whether the following patch fixes the issue for you?

Looks like it fixes it, thanks!


Thanks,
Sasha

  reply	other threads:[~2014-03-26  0:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  0:25 fs: gpf in simple_setattr Sasha Levin
2014-01-08 16:00 ` Sasha Levin
2014-03-01 20:05   ` Sasha Levin
2014-03-02  3:35     ` Linus Torvalds
2014-03-03  2:01       ` Sasha Levin
2014-03-03 21:40     ` Jan Kara
2014-03-05  0:00       ` Sasha Levin
2014-03-05 12:45         ` Jan Kara
2014-03-06 16:02           ` Sasha Levin
2014-03-08  2:14             ` Sasha Levin
2014-03-10 10:43               ` Jan Kara
2014-03-10 14:13                 ` Sasha Levin
2014-03-24 14:42                   ` Sasha Levin
2014-03-24 21:48                     ` Jan Kara
2014-03-25  0:44                       ` Sasha Levin
2014-03-25 17:33                         ` Jan Kara
2014-03-25 17:51                           ` Sasha Levin
2014-03-25 21:12                             ` Jan Kara
2014-03-26  0:12                               ` Sasha Levin [this message]
2014-03-26  0:41                               ` Linus Torvalds
2014-03-26  5:34                                 ` Jan Kara
2014-03-26  5:53                               ` Dave Jones
2014-03-26 15:00                                 ` Sasha Levin

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=53321B80.4070108@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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.