From: Andor Daam <andor.daam@googlemail.com>
To: linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, ocfs2-devel@oss.oracle.com
Cc: dan.magenheimer@oracle.com, fschmaus@gmail.com,
linux-mm@kvack.org, ilendir@googlemail.com,
sjenning@linux.vnet.ibm.com, konrad.wilk@oracle.com,
i4passt@lists.informatik.uni-erlangen.de, ngupta@vflare.org
Subject: ext3/4, btrfs, ocfs2: How to assure that cleancache_invalidate_fs is called on every superblock free
Date: Fri, 9 Mar 2012 14:40:22 +0100 [thread overview]
Message-ID: <CACQs63L2wfXKaD5sH6OOV+Bm_+37F3QOdt1QMFbWnB9AE4iCpA@mail.gmail.com> (raw)
Hello,
Is it ever possible for a superblock for a mounted filesystem to be
free'd without a previous call to unmount the filesystem?
I need to be certain that the function cleancache_invalidate_fs, which
is at the moment called by deactivate_locked_super (fs/super.c) [1],
is called before every free on a superblock of cleancache-enabled
filesystems.
Is this already the case or are there situations in which this does not happen?
It would be interesting to know this, as we are planning to have
cleancache save pointers to superblocks of every mounted
cleancache-enabled filesystem [2] and it would be fatal if a
superblock is free'd without cleancache being notified.
Regards
Andor
[1] commit c515e1fd361c2a08a9c2eb139396ec30a4f477dc
[2] http://marc.info/?l=linux-mm&m=133122649732669&w=2
next reply other threads:[~2012-03-09 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 13:40 Andor Daam [this message]
2012-03-12 13:38 ` Jan Kara
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=CACQs63L2wfXKaD5sH6OOV+Bm_+37F3QOdt1QMFbWnB9AE4iCpA@mail.gmail.com \
--to=andor.daam@googlemail.com \
--cc=dan.magenheimer@oracle.com \
--cc=fschmaus@gmail.com \
--cc=i4passt@lists.informatik.uni-erlangen.de \
--cc=ilendir@googlemail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=sjenning@linux.vnet.ibm.com \
/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