linux-kernel - Re: [PATCH v2 25/26] bio-integrity: Add explicit field for owner of bip

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: <20120917210945.GD14492@google.com>
Date:	Mon, 17 Sep 2012 14:09:45 -0700
From:	Kent Overstreet <koverstreet@...gle.com>
To:	"Martin K. Petersen" <martin.petersen@...cle.com>
Cc:	linux-bcache@...r.kernel.org, linux-kernel@...r.kernel.org,
	dm-devel@...hat.com, axboe@...nel.dk, tj@...nel.org, neilb@...e.de
Subject: Re: [PATCH v2 25/26] bio-integrity: Add explicit field for owner of
 bip_buf

On Wed, Sep 12, 2012 at 03:41:36PM -0400, Martin K. Petersen wrote:
> >>>>> "Kent" == Kent Overstreet <koverstreet@...gle.com> writes:
> 
> Kent> This was the only real user of BIO_CLONED, which didn't have very
> Kent> clear semantics. Convert to its own flag so we can get rid of
> Kent> BIO_CLONED.
> 
> I already have a patch in my queue that moves all integrity-relevant
> flags from struct bio to the bip. So I'm ok with removing BIO_CLONED but
> I'll send a separate patch for the integrity flags.

Cool - have a git repo I can take a look at?
--
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/