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  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:   Wed, 15 May 2019 17:21:51 -0700
From:   Dan Williams <>
To:     Vivek Goyal <>
Cc:     linux-fsdevel <>,
        Linux Kernel Mailing List <>,
        KVM list <>,
        linux-nvdimm <>,
        Steven Whitehouse <>,
        "Dr. David Alan Gilbert" <>,
        Stefan Hajnoczi <>,
        Miklos Szeredi <>
Subject: Re: [PATCH v2 12/30] dax: remove block device dependencies

On Wed, May 15, 2019 at 12:28 PM Vivek Goyal <> wrote:
> From: Stefan Hajnoczi <>
> Although struct dax_device itself is not tied to a block device, some
> DAX code assumes there is a block device.  Make block devices optional
> by allowing bdev to be NULL in commonly used DAX APIs.
> When there is no block device:
>  * Skip the partition offset calculation in bdev_dax_pgoff()
>  * Skip the blkdev_issue_zeroout() optimization
> Note that more block device assumptions remain but I haven't reach those
> code paths yet.

Is there a generic object that non-block-based filesystems reference
for physical storage as a bdev stand-in? I assume "sector_t" is still
the common type for addressing filesystem capacity?

It just seems to me that we should stop pretending that the
filesystem-dax facility requires block devices and try to move this
functionality to generically use a dax device across all interfaces.

Powered by blists - more mailing lists