From: Milan Broz <gmazyland@gmail.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Julia Lawall <Julia.Lawall@lip6.fr>,
Alasdair Kergon <agk@redhat.com>,
kernel-janitors@vger.kernel.org, dm-devel@redhat.com,
Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/8 v2] dm: replace memset by memzero_explicit
Date: Mon, 01 Dec 2014 22:03:53 +0100 [thread overview]
Message-ID: <547CD7B9.5030000@gmail.com> (raw)
In-Reply-To: <1417367029-32762-6-git-send-email-Julia.Lawall@lip6.fr>
On 11/30/2014 06:03 PM, Julia Lawall wrote:
> From: Julia Lawall <Julia.Lawall@lip6.fr>
>
> Memset on a local variable may be removed when it is called just before the
> variable goes out of scope. Using memzero_explicit defeats this
> optimization. A simplified version of the semantic patch that makes this
> change is as follows: (http://coccinelle.lip6.fr/)
Ack, but I submitted the same patch a week ago....
https://www.redhat.com/archives/dm-devel/2014-November/msg00084.html
Mike, please could you add this to linux-next tree or you want this
to go through Herbert's tree?
(I do not think it is good idea for DM patches.)
Thanks,
Milan
>
> // <smpl>
> @@
> identifier x;
> type T;
> @@
>
> {
> ... when any
> T x[...];
> ... when any
> when exists
> - memset
> + memzero_explicit
> (x,
> -0,
> ...)
> ... when != x
> when strict
> }
> // </smpl>
>
> This change was suggested by Daniel Borkmann <dborkman@redhat.com>
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>
> ---
> Daniel Borkmann suggested that these patches could go through Herbert Xu's
> cryptodev tree.
>
> v2: fixed email address
>
> drivers/md/dm-crypt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
> index fc93b93..08981be 100644
> --- a/drivers/md/dm-crypt.c
> +++ b/drivers/md/dm-crypt.c
> @@ -705,7 +705,7 @@ static int crypt_iv_tcw_whitening(struct crypt_config *cc,
> for (i = 0; i < ((1 << SECTOR_SHIFT) / 8); i++)
> crypto_xor(data + i * 8, buf, 8);
> out:
> - memset(buf, 0, sizeof(buf));
> + memzero_explicit(buf, sizeof(buf));
> return r;
> }
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Milan Broz <gmazyland@gmail.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Julia Lawall <Julia.Lawall@lip6.fr>,
Alasdair Kergon <agk@redhat.com>,
kernel-janitors@vger.kernel.org, dm-devel@redhat.com,
Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/8 v2] dm: replace memset by memzero_explicit
Date: Mon, 01 Dec 2014 21:03:53 +0000 [thread overview]
Message-ID: <547CD7B9.5030000@gmail.com> (raw)
In-Reply-To: <1417367029-32762-6-git-send-email-Julia.Lawall@lip6.fr>
On 11/30/2014 06:03 PM, Julia Lawall wrote:
> From: Julia Lawall <Julia.Lawall@lip6.fr>
>
> Memset on a local variable may be removed when it is called just before the
> variable goes out of scope. Using memzero_explicit defeats this
> optimization. A simplified version of the semantic patch that makes this
> change is as follows: (http://coccinelle.lip6.fr/)
Ack, but I submitted the same patch a week ago....
https://www.redhat.com/archives/dm-devel/2014-November/msg00084.html
Mike, please could you add this to linux-next tree or you want this
to go through Herbert's tree?
(I do not think it is good idea for DM patches.)
Thanks,
Milan
>
> // <smpl>
> @@
> identifier x;
> type T;
> @@
>
> {
> ... when any
> T x[...];
> ... when any
> when exists
> - memset
> + memzero_explicit
> (x,
> -0,
> ...)
> ... when != x
> when strict
> }
> // </smpl>
>
> This change was suggested by Daniel Borkmann <dborkman@redhat.com>
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>
> ---
> Daniel Borkmann suggested that these patches could go through Herbert Xu's
> cryptodev tree.
>
> v2: fixed email address
>
> drivers/md/dm-crypt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
> index fc93b93..08981be 100644
> --- a/drivers/md/dm-crypt.c
> +++ b/drivers/md/dm-crypt.c
> @@ -705,7 +705,7 @@ static int crypt_iv_tcw_whitening(struct crypt_config *cc,
> for (i = 0; i < ((1 << SECTOR_SHIFT) / 8); i++)
> crypto_xor(data + i * 8, buf, 8);
> out:
> - memset(buf, 0, sizeof(buf));
> + memzero_explicit(buf, sizeof(buf));
> return r;
> }
>
>
next prev parent reply other threads:[~2014-12-01 21:03 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 17:03 [PATCH 0/8] replace memset by memzero_explicit Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 17:03 ` [PATCH 1/8 v2] purgatory/sha256: " Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 17:03 ` [PATCH 2/8 v2] sparc64: " Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-12-02 14:58 ` Herbert Xu
2014-12-02 14:58 ` Herbert Xu
2014-11-30 17:03 ` [PATCH 3/8 v2] crypto: " Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 17:03 ` [PATCH 4/8 v2] cifs: " Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 17:03 ` [PATCH 5/8 v2] dm: " Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-12-01 21:03 ` Milan Broz [this message]
2014-12-01 21:03 ` Milan Broz
2014-12-01 23:00 ` Mike Snitzer
2014-12-01 23:00 ` Mike Snitzer
2014-11-30 17:03 ` [PATCH 6/8 v2] crypto: " Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-12-01 0:58 ` Michael Ellerman
2014-12-01 0:58 ` Michael Ellerman
2014-12-01 0:58 ` Michael Ellerman
2014-11-30 17:03 ` [PATCH 7/8 " Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 17:03 ` Julia Lawall
2014-11-30 19:57 ` Ard Biesheuvel
2014-11-30 19:57 ` Ard Biesheuvel
2014-11-30 19:57 ` Ard Biesheuvel
2014-11-30 17:03 ` [PATCH 8/8 v2] wusb: " Julia Lawall
2014-11-30 17:03 ` Julia Lawall
-- strict thread matches above, loose matches on Subject: below --
2014-11-30 16:59 [PATCH 0/8] " Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` [PATCH 1/8] purgatory/sha256: " Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-12-01 15:20 ` David Sterba
2014-12-01 15:20 ` David Sterba
2014-11-30 16:59 ` [PATCH 2/8] sparc64: " Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` [PATCH 3/8] crypto: " Julia Lawall
2014-11-30 16:59 ` Julia Lawall
[not found] ` <1417366774-32412-1-git-send-email-Julia.Lawall-L2FTfq7BK8M@public.gmane.org>
2014-11-30 16:59 ` [PATCH 4/8] cifs: " Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` [PATCH 5/8] dm: " Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` [PATCH 6/8] crypto: " Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` [PATCH 7/8] " Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-11-30 16:59 ` [PATCH 8/8] wusb: " Julia Lawall
2014-11-30 16:59 ` Julia Lawall
2014-12-03 0:14 ` Greg Kroah-Hartman
2014-12-03 0:14 ` Greg Kroah-Hartman
2014-12-03 0:18 ` Daniel Borkmann
2014-12-03 0:18 ` Daniel Borkmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=547CD7B9.5030000@gmail.com \
--to=gmazyland@gmail.com \
--cc=Julia.Lawall@lip6.fr \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=snitzer@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.