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: <yq1ip9zbyjq.fsf@sermon.lab.mkp.net>
Date:	Wed, 24 Oct 2012 12:54:49 -0400
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	Kent Overstreet <koverstreet@...gle.com>
Cc:	linux-bcache@...r.kernel.org, linux-kernel@...r.kernel.org,
	dm-devel@...hat.com, tj@...nel.org, axboe@...nel.dk,
	vgoyal@...hat.com, martin.petersen@...cle.com
Subject: Re: [PATCH v4 2/2] block: Convert integrity to bvec_alloc_bs()

>>>>> "Kent" == Kent Overstreet <koverstreet@...gle.com> writes:

Kent> Also, bio_integrity_alloc() was using fs_bio_set if no bio_set was
Kent> specified. This was wrong

You did that, I didn't.


Kent> - using the bio_set doesn't protect us from memory allocation
Kent>   failures, because we just used kmalloc for the
Kent>   bio_integrity_payload.

I don't understand this comment. kmalloc where?

The bip includes an embedded bvec array and comes from either one of the
dedicated slabs or - in the case of the max bvec size - from a
mempool. These slabs and the mempool are per bio_set.

-- 
Martin K. Petersen	Oracle Linux Engineering
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ