linux-ext4 - Re: [PATCH 1/2] ext4: use bio op helprs in ext4 crypto code

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <57588771.4050905@kernel.dk>
Date:	Wed, 8 Jun 2016 15:00:33 -0600
From:	Jens Axboe <axboe@...nel.dk>
To:	mchristi@...hat.com, linux-ext4@...r.kernel.org,
	linux-block@...r.kernel.org
Subject: Re: [PATCH 1/2] ext4: use bio op helprs in ext4 crypto code

On 06/08/2016 02:49 PM, mchristi@...hat.com wrote:
> From: Mike Christie <mchristi@...hat.com>
>
> This was missed from my last patchset.
>
> This patch has ext4 crypto code use the bio op helper
> to set the operation. The operation (discard, write, writesame,
> etc) is now defined seperately from the other REQ bits. They
> still share the bi_rw field to save space, so we use these
> helpers so modules do not have to worry about setting/overwriting
> info.
>
> Jens, I am not sure how you handle patches on top of patches
> in the next branches. If you merge patches that fix issues
> in previous patches in next, then this patch could be part
> of

Since it's all merged, there's only one way to handle it - and that's to 
apply this on top. I can't fold patches at this point.

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html