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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 23 Jan 2017 17:01:03 +0100
From:   Christoph Hellwig <>
To:     Dan Williams <>
Cc:     Christoph Hellwig <>,
        Matthew Wilcox <>,
        "" <>,
        Brian Boylston <>,
        Tony Luck <>, Jan Kara <>,
        Toshi Kani <>,
        Mike Snitzer <>,
        "" <>,
        "" <>, Jeff Moyer <>,
        Jens Axboe <>,
        "" <>,
        Ingo Molnar <>,
        Al Viro <>,
        "H. Peter Anvin" <>,
        "" <>,
        Thomas Gleixner <>,
        Linus Torvalds <>,
        Ross Zwisler <>
Subject: Re: [PATCH 00/13] dax, pmem: move cpu cache maintenance to

On Sun, Jan 22, 2017 at 09:30:23AM -0800, Dan Williams wrote:
> So are you saying we need a way to go from a block_device inode to a
> dax_device inode and then look up the dax_operations from there?
> A filesystem, if it so chooses, could mount on top of the dax_device
> inode directly?

Sentence 1: maybe if we have to.  Sentence 2: absolutely.

> I did add a dax_superblock for the device-dax character device
> representation I could refactor that so the block_device presentation
> of a namespace and a character device presentation are just different
> layers on top of the base-level dax inode.

That's a good start.

Powered by blists - more mailing lists