RE: invalidate the buffer heads of a block device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > 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 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?
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux