linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Thanos Makatos <thanos.makatos@citrix.com>
Cc: 'Jan Kara' <jack@suse.cz>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Ross Lagerwall <ross.lagerwall@citrix.com>,
	Felipe Franciosi <felipe.franciosi@citrix.com>
Subject: Re: invalidate the buffer heads of a block device
Date: Tue, 30 Sep 2014 11:19:02 +0200	[thread overview]
Message-ID: <20140930091902.GA26216@quack.suse.cz> (raw)
In-Reply-To: <2368A3FCF9F7214298E53C823B0A48EC0420B711@AMSPEX01CL02.citrite.net>

On Tue 30-09-14 08:58:54, Thanos Makatos wrote:
> > > If the above observations are correct, it seems that I have to either
> > > extend BLKFLSBUF to some invalidate such memory maps (I'm completely
> > > ignorant in that field, is it even possible?), or look for other
> > > solutions.
> >   Well, you could unmap the pages of block device that are mapped in your
> > new ioctl but I don't think it's easily possible to disallow userspace to fault the
> > pages back behind your back. And that could be a problem for you.
> 
> I'm not sure I understand what "I don't think it's easily possible to
> disallow userspace to fault the pages back behind your back" means, could
> you explain?
  I mean by that that even if you evict page from page cache, it can be
immediately reloaded from the device. So you have to be careful to
provide new data once you decide to go and evict page cache. But that's
obvious I guess.

> I definitely don't care what happens to the process that dared to memory
> map the block device, this configuration is not supported in my
> environment. Is this what you mean?
  OK, so it isn't supported but you don't want such application to be able
to screw up your other processes, am I right?

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2014-09-30  9:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 16:24 invalidate the buffer heads of a block device Thanos Makatos
2014-09-29 18:11 ` Jan Kara
2014-09-30  8:58   ` Thanos Makatos
2014-09-30  9:19     ` Jan Kara [this message]
2014-09-30  9:39       ` Thanos Makatos
2014-09-30  9:55         ` Jan Kara
2014-09-30 10:11           ` Thanos Makatos
2014-09-30 10:48             ` Jan Kara
2014-09-30 20:53               ` Zach Brown
2014-09-30 21:13                 ` Trond Myklebust
2014-10-01  9:05                   ` Jan Kara
2014-10-01 11:50                     ` Trond Myklebust
2014-10-01 14:07                       ` Jan Kara
2014-10-01 14:47                         ` Trond Myklebust
2014-10-01 15:15                           ` 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=20140930091902.GA26216@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=felipe.franciosi@citrix.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ross.lagerwall@citrix.com \
    --cc=thanos.makatos@citrix.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;
as well as URLs for NNTP newsgroup(s).