linux-kernel - [PATCH 0/7] padata/pcrypt: cleanups

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-next>] [day] [month] [year] [list]

Date:	Tue, 27 Jul 2010 07:13:47 +0200
From:	Steffen Klassert <steffen.klassert@...unet.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	Dan Kruchinin <dkruchinin@....org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/7] padata/pcrypt: cleanups

This patchset contains the following changes:

1. padata - Rename padata_alloc functions to not export underlined functions.

2. padata - Rearrange set_cpumask functions to have proper locking for all
these functions and to avoid to export underlined functions.

3. padata - Pass the padata cpumasks to the cpumask_change_notifier chain, so
users can access them without the need of a padata_get_cpumask function.

4. pcrypt - Rename the stuct pcrypt_instance. An instance refers usually to a
crypto instance in the crypto-layer, the struct pcrypt_instance is not related
to a crypto instance, so we rename it.

5. pcrypt - Update pcrypt cpumask acording to the padata cpumask notifier.
The padata cpumask change notifier passes a padata_cpumask to the
notifier chain, so we use this to update the pcrypt cpumask.

6. padata - Remove padata_get_cpumask. This function is a bit error prone
because the cpumask can change at any time, so we can't be sure to get the
right cpumask from that function.

7. padata - Update the API documentation.

Steffen

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