linux-kernel - Re: [PATCH v3] staging: writeboost: Add dm-writeboost

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: <20150220161759.GC4740@debian>
Date:	Fri, 20 Feb 2015 16:17:59 +0000
From:	Joe Thornber <thornber@...hat.com>
To:	Akira Hayakawa <ruby.wktk@...il.com>
Cc:	ejt@...hat.com, Greg KH <gregkh@...uxfoundation.org>,
	snitzer@...hat.com, dm-devel@...hat.com,
	driverdev-devel@...uxdriverproject.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] staging: writeboost: Add dm-writeboost

On Sat, Feb 21, 2015 at 01:06:08AM +0900, Akira Hayakawa wrote:
> The size is configurable but typically 512KB (that's the default).
> 
> Refer to bio payload sounds really dangerous but it may be possible
> in some tricky way. but at the moment I am not sure how the
> implementation would be.
> 
> Is there some fancy function that is like memcpy but actually "move"
> the ownership?

When building up your log chunk bio copy the bio_vecs (not the data)
from the original bios.  You can't complete the original bios until
your log chunk has been written.

- Joe
--
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/