ndfhWÀ¿åw2,&%æß71|<0YØá¸Ç\ÂJîÁ\üF<NÙÅ>¸ß½pH3ÓBæw%ÏF´:Ú5f`!Â^?ì)ÙjVºnîêmÇ÷ê8p_óPF/?I°¼¤_5Ð]±±3¼Z¾xbME
V5¡4£b?¹ÝúN5áqÁ1äP¹eÙÓVÙïÖ*äîþ¿uNèÕ[.ÈÉG!Ø᣼ËÚYüag.k.(F¼c°ÈpGT<Òâxx¼»±ÞÏËÞEuç¯Ò|ÚO.s.v6PÂ>
TûtóUE¤Êø¾Þc~;Ôñç¤}¦?6ÑÜMÐðî¨~&·bÁØ£RÈF2dåxObbgBB
Convert the dax filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Signed-off-
Hi Al,
Here's a set of patches that converts a bunch (but not yet all!) to the new
mount API. To this end, it makes the following changes:
(1) Provides a convenience member in struct fs_context that is OR'd into
sb->s_iflags by sget_fc().
(2) Provides a convenience helper function, vfs
Add a .travis.yml config to enable Travis CI.
Also add the Travis CI status 'badge' to README.md
For now, this only does a compile test. It can be built upon in the
future to do more runtime testing. Since the travis environment uses
Ubuntu, this is useful regardless, as it will immediately catch
Add a .travis.yml config to enable Travis CI.
Also add the Travis CI status 'badge' to README.md
For now, this only does a compile test. It can be built upon in the
future to do more runtime testing. Since the travis environment uses
Ubuntu, this is useful regardless, as it will immediately catch
With zero-key defined, we can remove previous detection of key id 0 or null
key in order to deal with a zero-key situation. Syncing all security
commands to use the zero-key. Helper functions are introduced to return the
data that points to the actual key payload or the zero_key. This helps
uniform
Add a zero key in order to standardize hardware that want a key of 0's to
be passed. Some platforms defaults to a zero-key with security enabled
rather than allow the OS to enable the security. The zero key would allow
us to manage those platform as well. This also adds a fix to secure erase
so it
From: Dave Hansen
[ Upstream commit 5cd401ace914dc68556c6d2fcae0c349444d5f86 ]
walk_system_ram_range() can return an error code either becuase
*it* failed, or because the 'func' that it calls returned an
error. The memory hotplug does the following:
ret = walk_system_ram_range(..., fun
On Fri, 2019-03-22 at 16:50 -0700, Dave Jiang wrote:
> Add warning note in man page that overwrite may take a long time to
> execute.
>
> Suggested-by: Robert Elliot
> Signed-off-by: Dave Jiang
> ---
> Documentation/ndctl/ndctl-sanitize-dimm.txt |3 ++-
> 1 file changed, 2 insertions(+),
> From: Verma, Vishal L
> Sent: Wednesday, March 27, 2019 9:17 AM
> To: Williams, Dan J ; Dexuan Cui
> ; Jiang, Dave ;
> linux-nvdimm@lists.01.org; dexuan@gmail.com; Michael Kelley
>
> Cc: jthumsh...@suse.de; qi.f...@fujitsu.com
> Subject: Re: [ndctl PATCH v3 4/5] libndctl: Add a new dimm-op
On Fri, 2019-03-22 at 16:42 -0700, Dave Jiang wrote:
> Providing a way for crypto-erase to pass in a key that is with 0's as
> payload.
>
> Signed-off-by: Dave Jiang
> ---
>
> v2:
> - Make zero key option explicit with -z parameter. Otherwise we will look
> for a key. (Dan)
>
> Documentati
On Wed, Mar 27, 2019 at 9:13 AM Michal Hocko wrote:
>
> On Tue 26-03-19 17:20:41, Dan Williams wrote:
> > On Tue, Mar 26, 2019 at 1:04 AM Michal Hocko wrote:
> > >
> > > On Mon 25-03-19 13:03:47, Dan Williams wrote:
> > > > On Mon, Mar 25, 2019 at 3:20 AM Michal Hocko wrote:
> > > [...]
> > > >
On Tue, 2019-03-26 at 23:29 +, Dexuan Cui wrote:
> Here ndctl is checking if ND_CMD_SMART is supported in
> dimm->cmd_mask. For all the non-NVDIMM_FAMILY_INTEL families,
> the check is false, including the HPE1 and MSFT families.
>
> So IMO we need this new dimm-ops to make "ndctl monitor"
On Tue 26-03-19 17:20:41, Dan Williams wrote:
> On Tue, Mar 26, 2019 at 1:04 AM Michal Hocko wrote:
> >
> > On Mon 25-03-19 13:03:47, Dan Williams wrote:
> > > On Mon, Mar 25, 2019 at 3:20 AM Michal Hocko wrote:
> > [...]
> > > > > User-defined memory namespaces have this problem, but 2MB is the
14 matches
Mail list logo
