| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 29 Oct 2015 16:14:00 +0900 From: Dan Williams <dan.j.williams@...el.com> To: Jeff Moyer <jmoyer@...hat.com> Cc: Jens Axboe <axboe@...com>, Jan Kara <jack@...e.cz>, linux-nvdimm <linux-nvdimm@...1.01.org>, Jan Kara <jack@...e.com>, david <david@...morbit.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Ross Zwisler <ross.zwisler@...ux.intel.com>, Matthew Wilcox <willy@...ux.intel.com>, Andrew Morton <akpm@...ux-foundation.org>, Christoph Hellwig <hch@....de> Subject: Re: [PATCH v2 5/5] block: enable dax for raw block devices On Thu, Oct 29, 2015 at 5:50 AM, Jeff Moyer <jmoyer@...hat.com> wrote: > Dan Williams <dan.j.williams@...el.com> writes: > >> If an application wants exclusive access to all of the persistent memory >> provided by an NVDIMM namespace it can use this raw-block-dax facility >> to forgo establishing a filesystem. This capability is targeted >> primarily to hypervisors wanting to provision persistent memory for >> guests. > > OK, I'm going to expose my ignorance here. :) Why does the block device > need a page_mkwrite handler? > You're right, it buys us nothing, and deleting it saves having to comment on why this page_mkwrite instance is not calling sb_start_pagefault. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists