From: Mark Fasheh <mark.fasheh@oracle.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -rc2-mm2] update tmpfs for new delete_inode behavior
Date: Tue, 12 Jul 2005 13:52:09 -0700 [thread overview]
Message-ID: <20050712205209.GE14505@ca-server1.us.oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0507121508520.6933@goblin.wat.veritas.com>
On Tue, Jul 12, 2005 at 03:22:11PM +0100, Hugh Dickins wrote:
> LTP on tmpfs hits kernel BUG at mm/shmem.c:680! shmem_delete_inode needs
> to truncate_inode_pages for itself now. It's not immediately obvious since
> many cases get covered by shmem_truncate's followup truncate_inode_pages:
> maybe with thought we can just call it once, but right now fix the BUG.
Erf, indeed I missed that one.
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
prev parent reply other threads:[~2005-07-12 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 14:22 [PATCH -rc2-mm2] update tmpfs for new delete_inode behavior Hugh Dickins
2005-07-12 20:52 ` Mark Fasheh [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=20050712205209.GE14505@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox