From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, viro@ZenIV.linux.org.uk
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: 3.1-rc10 oops in nameidata_to_filp
Date: 24 Nov 2011 16:47:10 -0500 [thread overview]
Message-ID: <20111124214710.13413.qmail@science.horizon.com> (raw)
In-Reply-To: <20111124173829.GL2203@ZenIV.linux.org.uk>
Thanks for the pointer. I'll write some debug code.
> Said that, I'm not buying the theory of open assigning to ->f_mapping and
> screwing it up; all such assignments end up with ->i_mapping of *some*
> inode, as far as I can see from cursory grep over the tree. Just in case:
> do you have CONFIG_FS_POSIX_ACL set?
No, I always turn that off. (And TMPFS_POSIX_ACL, too.)
next prev parent reply other threads:[~2011-11-24 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 11:22 3.1-rc10 oops in nameidata_to_filp George Spelvin
2011-11-24 14:51 ` Jan Kara
2011-11-24 16:44 ` George Spelvin
2011-11-24 17:38 ` Al Viro
2011-11-24 17:50 ` Al Viro
2011-11-24 17:51 ` Al Viro
2011-11-30 23:57 ` Andrew Morton
2011-11-24 21:14 ` Jan Kara
2011-11-24 21:47 ` George Spelvin [this message]
2011-11-24 22:13 ` Al Viro
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=20111124214710.13413.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox