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: Tue, 30 Jun 2020 16:43:55 +0200 From: Michal Suchánek <msuchanek@...e.de> To: Mike Snitzer <snitzer@...hat.com> Cc: Mikulas Patocka <mpatocka@...hat.com>, linux-nvdimm@...ts.01.org, "Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>, Jan Kara <jack@...e.cz>, Alasdair Kergon <agk@...hat.com>, dm-devel@...hat.com, "Michael S. Tsirkin" <mst@...hat.com>, Yuval Shaia <yuval.shaia@...cle.com>, Cornelia Huck <cohuck@...hat.com>, Jakub Staron <jstaron@...gle.com>, linux-kernel@...r.kernel.org Subject: Re: dm writecache: reject asynchronous pmem. On Tue, Jun 30, 2020 at 09:36:33AM -0400, Mike Snitzer wrote: > On Tue, Jun 30 2020 at 10:10am -0400, > Michal Suchánek <msuchanek@...e.de> wrote: > > > On Tue, Jun 30, 2020 at 09:32:01AM -0400, Mikulas Patocka wrote: > > > > > > > > > On Tue, 30 Jun 2020, Michal Suchanek wrote: > > > > > > > The writecache driver does not handle asynchronous pmem. Reject it when > > > > supplied as cache. > > > > > > > > Link: https://lore.kernel.org/linux-nvdimm/87lfk5hahc.fsf@linux.ibm.com/ > > > > Fixes: 6e84200c0a29 ("virtio-pmem: Add virtio pmem driver") > > > > > > > > Signed-off-by: Michal Suchanek <msuchanek@...e.de> > > > > --- > > > > drivers/md/dm-writecache.c | 6 ++++++ > > > > 1 file changed, 6 insertions(+) > > > > > > > > diff --git a/drivers/md/dm-writecache.c b/drivers/md/dm-writecache.c > > > > index 30505d70f423..57b0a972f6fd 100644 > > > > --- a/drivers/md/dm-writecache.c > > > > +++ b/drivers/md/dm-writecache.c > > > > @@ -2277,6 +2277,12 @@ static int writecache_ctr(struct dm_target *ti, unsigned argc, char **argv) > > > > > > > > wc->memory_map_size -= (uint64_t)wc->start_sector << SECTOR_SHIFT; > > > > > > > > + if (!dax_synchronous(wc->ssd_dev->dax_dev)) { > > > > + r = -EOPNOTSUPP; > > > > + ti->error = "Asynchronous persistent memory not supported as pmem cache"; > > > > + goto bad; > > > > + } > > > > + > > > > bio_list_init(&wc->flush_list); > > > > wc->flush_thread = kthread_create(writecache_flush_thread, wc, "dm_writecache_flush"); > > > > if (IS_ERR(wc->flush_thread)) { > > > > -- > > > > > > Hi > > > > > > Shouldn't this be in the "if (WC_MODE_PMEM(wc))" block? > > That should be always the case at this point. > > > > > > WC_MODE_PMEM(wc) retrurns true if we are using persistent memory as a > > > cache device, otherwise we are using generic block device as a cache > > > device. > > > > This is to prevent the situation where we have WC_MODE_PMEM(wc) but > > cannot guarantee consistency because the async flush is not handled. > > The writecache operates in 2 modes. SSD or PMEM. Mikulas is saying > your dax_synchronous() check should go within a WC_MODE_PMEM(wc) block > because it doesn't make sense to do the check when in SSD mode. Indeed, it's in the wrong if/else branch. Thanks Michal
Powered by blists - more mailing lists