linux-kernel - Re: NVM Mapping API

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120518171901.GT22985@linux.intel.com>
Date:	Fri, 18 May 2012 13:19:01 -0400
From:	Matthew Wilcox <willy@...ux.intel.com>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: NVM Mapping API

On Fri, May 18, 2012 at 04:31:08PM +0100, James Bottomley wrote:
> On Fri, 2012-05-18 at 10:49 -0400, Matthew Wilcox wrote:
> > You're downplaying the complexity of your own solution while overstating
> > the complexity of mine.  Let's compare, using your suggestion of the
> > dmesg buffer.
> 
> I'll give you that one when you tell me how you use your vfs interface
> simply from within the kernel.  Both are always about the same
> complexity in user space ...
> 
> To be honest, I'm not hugely concerned whether the key management API is
> u32 or a string.  What bothers me the most is that there will be
> in-kernel users for whom trying to mmap a file through the vfs will be
> hugely more complex than a simple give me a pointer to this persistent
> region.

Huh?  You snipped the example where I showed exactly that.  The user
calls nvm_map() and gets back a pointer to a kernel mapping for the
persistent region.
--
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/