All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "Jason A . Donenfeld"
	<Jason-OnJsPKxuuEcAvxtiuMwx3w@public.gmane.org>,
	Jarkko Sakkinen
	<jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
	linux-sctp-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	kasan-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	linux-stm32-XDFAJ8BFU24N7RejjzZ/Li2xQDfSxrLKVpNB7YpNyf8@public.gmane.org,
	devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>,
	Matthew Wilcox <willy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	David Rientjes <rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	Waiman Long <longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ecryptfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	wireguard-/J5FBtcyxH5ZwnvJuMANYw@public.gmane.org,
	linux-fscrypt-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Andrew Morton
	<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	linux-wir
Subject: Re: [PATCH v4 1/3] mm/slab: Use memzero_explicit() in kzfree()
Date: Tue, 16 Jun 2020 12:08:07 +0300	[thread overview]
Message-ID: <20200616090807.GK4151@kadam> (raw)
In-Reply-To: <20200616064208.GA9499-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>

On Tue, Jun 16, 2020 at 08:42:08AM +0200, Michal Hocko wrote:
> On Mon 15-06-20 21:57:16, Waiman Long wrote:
> > The kzfree() function is normally used to clear some sensitive
> > information, like encryption keys, in the buffer before freeing it back
> > to the pool. Memset() is currently used for the buffer clearing. However,
> > it is entirely possible that the compiler may choose to optimize away the
> > memory clearing especially if LTO is being used. To make sure that this
> > optimization will not happen, memzero_explicit(), which is introduced
> > in v3.18, is now used in kzfree() to do the clearing.
> > 
> > Fixes: 3ef0e5ba4673 ("slab: introduce kzfree()")
> > Cc: stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > Signed-off-by: Waiman Long <longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> 
> Acked-by: Michal Hocko <mhocko-IBi9RG/b67k@public.gmane.org>
> 
> Although I am not really sure this is a stable material. Is there any
> known instance where the memset was optimized out from kzfree?

I told him to add the stable.  Otherwise it will just get reported to
me again.  It's a just safer to backport it before we forget.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Jason A . Donenfeld" <Jason@zx2c4.com>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	virtualization@lists.linux-foundation.org,
	David Howells <dhowells@redhat.com>,
	linux-mm@kvack.org, linux-sctp@vger.kernel.org,
	keyrings@vger.kernel.org, kasan-dev@googlegroups.com,
	linux-stm32@st-md-mailman.stormreply.com,
	devel@driverdev.osuosl.org, linux-cifs@vger.kernel.org,
	linux-scsi@vger.kernel.org, James Morris <jmorris@namei.org>,
	Matthew Wilcox <willy@infradead.org>,
	David Rientjes <rientjes@google.com>,
	Waiman Long <longman@redhat.com>,
	linux-pm@vger.kernel.org, ecryptfs@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, wireguard@lists.zx2c4.com,
	linux-fscrypt@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	linux-amlogic@lists.infradead.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-nfs@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-wireless@vger.kernel.org, David Sterba <dsterba@suse.cz>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-bluetooth@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	target-devel@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	linux-crypto@vger.kernel.org,
	Johannes Weiner <hannes@cmpxchg.org>,
	Joe Perches <joe@perches.com>,
	linux-integrity@vger.kernel.org, linux-wpan@vger.kernel.org,
	netdev@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-ppp@vger.kernel.org
Subject: Re: [PATCH v4 1/3] mm/slab: Use memzero_explicit() in kzfree()
Date: Tue, 16 Jun 2020 09:08:07 +0000	[thread overview]
Message-ID: <20200616090807.GK4151@kadam> (raw)
In-Reply-To: <20200616064208.GA9499@dhcp22.suse.cz>

On Tue, Jun 16, 2020 at 08:42:08AM +0200, Michal Hocko wrote:
> On Mon 15-06-20 21:57:16, Waiman Long wrote:
> > The kzfree() function is normally used to clear some sensitive
> > information, like encryption keys, in the buffer before freeing it back
> > to the pool. Memset() is currently used for the buffer clearing. However,
> > it is entirely possible that the compiler may choose to optimize away the
> > memory clearing especially if LTO is being used. To make sure that this
> > optimization will not happen, memzero_explicit(), which is introduced
> > in v3.18, is now used in kzfree() to do the clearing.
> > 
> > Fixes: 3ef0e5ba4673 ("slab: introduce kzfree()")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Waiman Long <longman@redhat.com>
> 
> Acked-by: Michal Hocko <mhocko@suse.com>
> 
> Although I am not really sure this is a stable material. Is there any
> known instance where the memset was optimized out from kzfree?

I told him to add the stable.  Otherwise it will just get reported to
me again.  It's a just safer to backport it before we forget.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Jason A . Donenfeld" <Jason@zx2c4.com>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	virtualization@lists.linux-foundation.org,
	David Howells <dhowells@redhat.com>,
	linux-mm@kvack.org, linux-sctp@vger.kernel.org,
	keyrings@vger.kernel.org, kasan-dev@googlegroups.com,
	linux-stm32@st-md-mailman.stormreply.com,
	devel@driverdev.osuosl.org, linux-cifs@vger.kernel.org,
	linux-scsi@vger.kernel.org, James Morris <jmorris@namei.org>,
	Matthew Wilcox <willy@infradead.org>,
	David Rientjes <rientjes@google.com>,
	Waiman Long <longman@redhat.com>,
	linux-pm@vger.kernel.org, ecryptfs@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, wireguard@lists.zx2c4.com,
	linux-fscrypt@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	linux-amlogic@lists.infradead.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-nfs@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-wireless@vger.kernel.org, David Sterba <dsterba@suse.cz>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-bluetooth@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	target-devel@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	linux-crypto@vger.kernel.org,
	Johannes Weiner <hannes@cmpxchg.org>,
	Joe Perches <joe@perches.com>,
	linux-integrity@vger.kernel.org, linux-wpan@vger.kernel.org,
	netdev@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-ppp@vger.kernel.org
Subject: Re: [PATCH v4 1/3] mm/slab: Use memzero_explicit() in kzfree()
Date: Tue, 16 Jun 2020 12:08:07 +0300	[thread overview]
Message-ID: <20200616090807.GK4151@kadam> (raw)
In-Reply-To: <20200616064208.GA9499@dhcp22.suse.cz>

On Tue, Jun 16, 2020 at 08:42:08AM +0200, Michal Hocko wrote:
> On Mon 15-06-20 21:57:16, Waiman Long wrote:
> > The kzfree() function is normally used to clear some sensitive
> > information, like encryption keys, in the buffer before freeing it back
> > to the pool. Memset() is currently used for the buffer clearing. However,
> > it is entirely possible that the compiler may choose to optimize away the
> > memory clearing especially if LTO is being used. To make sure that this
> > optimization will not happen, memzero_explicit(), which is introduced
> > in v3.18, is now used in kzfree() to do the clearing.
> > 
> > Fixes: 3ef0e5ba4673 ("slab: introduce kzfree()")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Waiman Long <longman@redhat.com>
> 
> Acked-by: Michal Hocko <mhocko@suse.com>
> 
> Although I am not really sure this is a stable material. Is there any
> known instance where the memset was optimized out from kzfree?

I told him to add the stable.  Otherwise it will just get reported to
me again.  It's a just safer to backport it before we forget.

regards,
dan carpenter


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Waiman Long <longman@redhat.com>,
	"Jason A . Donenfeld" <Jason@zx2c4.com>,
	linux-btrfs@vger.kernel.org,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	David Sterba <dsterba@suse.cz>,
	David Howells <dhowells@redhat.com>,
	linux-mm@kvack.org, linux-sctp@vger.kernel.org,
	keyrings@vger.kernel.org, kasan-dev@googlegroups.com,
	linux-stm32@st-md-mailman.stormreply.com,
	devel@driverdev.osuosl.org, linux-cifs@vger.kernel.org,
	linux-scsi@vger.kernel.org, James Morris <jmorris@namei.org>,
	Matthew Wilcox <willy@infradead.org>,
	linux-wpan@vger.kernel.org, David Rientjes <rientjes@google.com>,
	linux-pm@vger.kernel.org, ecryptfs@vger.kernel.org,
	linux-fscrypt@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	linux-amlogic@lists.infradead.org,
	virtualization@lists.linux-foundation.org,
	linux-integrity@vger.kernel.org, linux-nfs@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	target-devel@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	linux-crypto@vger.kernel.org,
	Johannes Weiner <hannes@cmpxchg.org>,
	Joe Perches <joe@perches.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linuxppc-dev@lists.ozlabs.org, netdev@vger.kernel.org,
	wireguard@lists.zx2c4.com, linux-ppp@vger.kernel.org
Subject: Re: [PATCH v4 1/3] mm/slab: Use memzero_explicit() in kzfree()
Date: Tue, 16 Jun 2020 12:08:07 +0300	[thread overview]
Message-ID: <20200616090807.GK4151@kadam> (raw)
In-Reply-To: <20200616064208.GA9499@dhcp22.suse.cz>

On Tue, Jun 16, 2020 at 08:42:08AM +0200, Michal Hocko wrote:
> On Mon 15-06-20 21:57:16, Waiman Long wrote:
> > The kzfree() function is normally used to clear some sensitive
> > information, like encryption keys, in the buffer before freeing it back
> > to the pool. Memset() is currently used for the buffer clearing. However,
> > it is entirely possible that the compiler may choose to optimize away the
> > memory clearing especially if LTO is being used. To make sure that this
> > optimization will not happen, memzero_explicit(), which is introduced
> > in v3.18, is now used in kzfree() to do the clearing.
> > 
> > Fixes: 3ef0e5ba4673 ("slab: introduce kzfree()")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Waiman Long <longman@redhat.com>
> 
> Acked-by: Michal Hocko <mhocko@suse.com>
> 
> Although I am not really sure this is a stable material. Is there any
> known instance where the memset was optimized out from kzfree?

I told him to add the stable.  Otherwise it will just get reported to
me again.  It's a just safer to backport it before we forget.

regards,
dan carpenter


WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Jason A . Donenfeld" <Jason@zx2c4.com>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	virtualization@lists.linux-foundation.org,
	David Howells <dhowells@redhat.com>,
	linux-mm@kvack.org, linux-sctp@vger.kernel.org,
	keyrings@vger.kernel.org, kasan-dev@googlegroups.com,
	linux-stm32@st-md-mailman.stormreply.com,
	devel@driverdev.osuosl.org, linux-cifs@vger.kernel.org,
	linux-scsi@vger.kernel.org, James Morris <jmorris@namei.org>,
	Matthew Wilcox <willy@infradead.org>,
	David Rientjes <rientjes@google.com>,
	Waiman Long <longman@redhat.com>,
	linux-pm@vger.kernel.org, ecryptfs@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, wireguard@lists.zx2c4.com,
	linux-fscrypt@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	linux-amlogic@lists.infradead.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-nfs@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-wireless@vger.kernel.org, David Sterba <dsterba@suse.cz>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-bluetooth@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	target-devel@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	linux-crypto@vger.kernel.org,
	Johannes Weiner <hannes@cmpxchg.org>,
	Joe Perches <joe@perches.com>,
	linux-integrity@vger.kernel.org, linux-wpan@vger.kernel.org,
	netdev@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-ppp@vger.kernel.org
Subject: Re: [PATCH v4 1/3] mm/slab: Use memzero_explicit() in kzfree()
Date: Tue, 16 Jun 2020 12:08:07 +0300	[thread overview]
Message-ID: <20200616090807.GK4151@kadam> (raw)
In-Reply-To: <20200616064208.GA9499@dhcp22.suse.cz>

On Tue, Jun 16, 2020 at 08:42:08AM +0200, Michal Hocko wrote:
> On Mon 15-06-20 21:57:16, Waiman Long wrote:
> > The kzfree() function is normally used to clear some sensitive
> > information, like encryption keys, in the buffer before freeing it back
> > to the pool. Memset() is currently used for the buffer clearing. However,
> > it is entirely possible that the compiler may choose to optimize away the
> > memory clearing especially if LTO is being used. To make sure that this
> > optimization will not happen, memzero_explicit(), which is introduced
> > in v3.18, is now used in kzfree() to do the clearing.
> > 
> > Fixes: 3ef0e5ba4673 ("slab: introduce kzfree()")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Waiman Long <longman@redhat.com>
> 
> Acked-by: Michal Hocko <mhocko@suse.com>
> 
> Although I am not really sure this is a stable material. Is there any
> known instance where the memset was optimized out from kzfree?

I told him to add the stable.  Otherwise it will just get reported to
me again.  It's a just safer to backport it before we forget.

regards,
dan carpenter


_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Jason A . Donenfeld" <Jason@zx2c4.com>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	virtualization@lists.linux-foundation.org,
	David Howells <dhowells@redhat.com>,
	linux-mm@kvack.org, linux-sctp@vger.kernel.org,
	keyrings@vger.kernel.org, kasan-dev@googlegroups.com,
	linux-stm32@st-md-mailman.stormreply.com,
	devel@driverdev.osuosl.org, linux-cifs@vger.kernel.org,
	linux-scsi@vger.kernel.org, James Morris <jmorris@namei.org>,
	Matthew Wilcox <willy@infradead.org>,
	David Rientjes <rientjes@google.com>,
	Waiman Long <longman@redhat.com>,
	linux-pm@vger.kernel.org, ecryptfs@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, wireguard@lists.zx2c4.com,
	linux-fscrypt@vger.kernel.org,
	linux-mediatek@lists.infradead.org,
	linux-amlogic@lists.infradead.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-nfs@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-wireless@vger.kernel.org, David Sterba <dsterba@suse.cz>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-bluetooth@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	target-devel@vger.kernel.org,
	tipc-discussion@lists.sourceforge.net,
	linux-crypto@vger.kernel.org,
	Johannes Weiner <hannes@cmpxchg.org>,
	Joe Perches <joe@perches.com>,
	linux-integrity@vger.kernel.org, linux-wpan@vger.kernel.org,
	netdev@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-ppp@vger.kernel.org
Subject: Re: [PATCH v4 1/3] mm/slab: Use memzero_explicit() in kzfree()
Date: Tue, 16 Jun 2020 12:08:07 +0300	[thread overview]
Message-ID: <20200616090807.GK4151@kadam> (raw)
In-Reply-To: <20200616064208.GA9499@dhcp22.suse.cz>

On Tue, Jun 16, 2020 at 08:42:08AM +0200, Michal Hocko wrote:
> On Mon 15-06-20 21:57:16, Waiman Long wrote:
> > The kzfree() function is normally used to clear some sensitive
> > information, like encryption keys, in the buffer before freeing it back
> > to the pool. Memset() is currently used for the buffer clearing. However,
> > it is entirely possible that the compiler may choose to optimize away the
> > memory clearing especially if LTO is being used. To make sure that this
> > optimization will not happen, memzero_explicit(), which is introduced
> > in v3.18, is now used in kzfree() to do the clearing.
> > 
> > Fixes: 3ef0e5ba4673 ("slab: introduce kzfree()")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Waiman Long <longman@redhat.com>
> 
> Acked-by: Michal Hocko <mhocko@suse.com>
> 
> Although I am not really sure this is a stable material. Is there any
> known instance where the memset was optimized out from kzfree?

I told him to add the stable.  Otherwise it will just get reported to
me again.  It's a just safer to backport it before we forget.

regards,
dan carpenter


  parent reply	other threads:[~2020-06-16  9:08 UTC|newest]

Thread overview: 168+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  1:57 [PATCH v4 0/3] mm, treewide: Rename kzfree() to kfree_sensitive() Waiman Long
2020-06-16  1:57 ` Waiman Long
2020-06-16  1:57 ` Waiman Long
2020-06-16  1:57 ` Waiman Long
2020-06-16  1:57 ` Waiman Long
2020-06-16  1:57 ` Waiman Long
2020-06-16  1:57 ` [PATCH v4 1/3] mm/slab: Use memzero_explicit() in kzfree() Waiman Long
2020-06-16  1:57   ` Waiman Long
2020-06-16  1:57   ` Waiman Long
2020-06-16  1:57   ` Waiman Long
2020-06-16  1:57   ` Waiman Long
2020-06-16  1:57   ` Waiman Long
2020-06-16  3:30   ` Eric Biggers
2020-06-16  3:30     ` Eric Biggers
2020-06-16  3:30     ` Eric Biggers
2020-06-16  3:30     ` Eric Biggers
2020-06-16  3:30     ` Eric Biggers
2020-06-16  3:30     ` Eric Biggers
2020-06-16 13:05     ` Waiman Long
2020-06-16 13:05       ` Waiman Long
2020-06-16 13:05       ` Waiman Long
2020-06-16 13:05       ` Waiman Long
2020-06-16 13:05       ` Waiman Long
2020-06-16 13:05       ` Waiman Long
2020-06-16 15:46       ` David Howells
2020-06-16 15:46         ` David Howells
2020-06-16 15:46         ` David Howells
2020-06-16 15:46         ` David Howells
2020-06-16 15:46         ` David Howells
2020-06-16 15:46         ` David Howells
2020-06-16  6:42   ` Michal Hocko
2020-06-16  6:42     ` Michal Hocko
2020-06-16  6:42     ` Michal Hocko
2020-06-16  6:42     ` Michal Hocko
2020-06-16  6:42     ` Michal Hocko
2020-06-16  6:42     ` Michal Hocko
     [not found]     ` <20200616064208.GA9499-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2020-06-16  9:08       ` Dan Carpenter [this message]
2020-06-16  9:08         ` Dan Carpenter
2020-06-16  9:08         ` Dan Carpenter
2020-06-16  9:08         ` Dan Carpenter
2020-06-16  9:08         ` Dan Carpenter
2020-06-16  9:08         ` Dan Carpenter
     [not found] ` <20200616015718.7812-1-longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-06-16  1:57   ` [PATCH v4 2/3] mm, treewide: Rename kzfree() to kfree_sensitive() Waiman Long
2020-06-16  1:57     ` Waiman Long
2020-06-16  1:57     ` Waiman Long
2020-06-16  1:57     ` Waiman Long
2020-06-16  1:57     ` Waiman Long
2020-06-16  1:57     ` Waiman Long
     [not found]     ` <20200616015718.7812-3-longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2020-06-16 14:26       ` Dan Carpenter
2020-06-16 14:26         ` Dan Carpenter
2020-06-16 14:26         ` Dan Carpenter
2020-06-16 14:26         ` Dan Carpenter
2020-06-16 14:26         ` Dan Carpenter
2020-06-16 14:26         ` Dan Carpenter
2020-06-16 15:05         ` Waiman Long
2020-06-16 15:05           ` Waiman Long
2020-06-16 15:05           ` Waiman Long
2020-06-16 15:05           ` Waiman Long
2020-06-16 15:05           ` Waiman Long
2020-06-16 15:05           ` Waiman Long
2020-06-16  1:57   ` [PATCH v4 3/3] btrfs: Use kfree() in btrfs_ioctl_get_subvol_info() Waiman Long
2020-06-16  1:57     ` Waiman Long
2020-06-16  1:57     ` Waiman Long
2020-06-16  1:57     ` Waiman Long
2020-06-16  1:57     ` Waiman Long
2020-06-16  1:57     ` Waiman Long
2020-06-16 14:48     ` David Sterba
2020-06-16 14:48       ` David Sterba
2020-06-16 14:48       ` David Sterba
2020-06-16 14:48       ` David Sterba
2020-06-16 14:48       ` David Sterba
2020-06-16 14:48       ` David Sterba
2020-06-16 15:05       ` Waiman Long
2020-06-16 15:05         ` Waiman Long
2020-06-16 15:05         ` Waiman Long
2020-06-16 15:05         ` Waiman Long
2020-06-16 15:05         ` Waiman Long
2020-06-16 15:05       ` Waiman Long
2020-06-16 18:53   ` [PATCH v4 0/3] mm, treewide: Rename kzfree() to kfree_sensitive() Joe Perches
2020-06-16 18:53     ` Joe Perches
2020-06-16 18:53     ` Joe Perches
2020-06-16 18:53     ` Joe Perches
2020-06-16 18:53     ` Joe Perches
2020-06-16 18:53     ` Joe Perches
2020-06-16 19:43     ` Waiman Long
2020-06-16 19:43       ` Waiman Long
2020-06-16 19:43       ` Waiman Long
2020-06-16 19:43       ` Waiman Long
2020-06-16 19:43       ` Waiman Long
2020-06-16 19:43       ` Waiman Long
2020-06-16 20:01     ` Waiman Long
2020-06-16 20:01       ` Waiman Long
2020-06-16 20:01       ` Waiman Long
2020-06-16 20:01       ` Waiman Long
2020-06-16 20:01       ` Waiman Long
2020-06-16 20:01       ` Waiman Long
     [not found]     ` <fe3b9a437be4aeab3bac68f04193cb6daaa5bee4.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2020-06-16 19:46       ` Jason A. Donenfeld
2020-06-16 19:46         ` Jason A. Donenfeld
2020-06-16 19:46         ` Jason A. Donenfeld
2020-06-16 19:46         ` Jason A. Donenfeld
2020-06-16 19:46         ` Jason A. Donenfeld
2020-06-16 19:46         ` Jason A. Donenfeld
2020-06-16 21:14       ` Matthew Wilcox
2020-06-16 21:14         ` Matthew Wilcox
2020-06-16 21:14         ` Matthew Wilcox
2020-06-16 21:14         ` Matthew Wilcox
2020-06-16 21:14         ` Matthew Wilcox
2020-06-16 21:14         ` Matthew Wilcox
2020-06-17 21:31       ` Denis Efremov
2020-06-17 21:31         ` Denis Efremov
2020-06-17 21:31         ` Denis Efremov
2020-06-17 21:31         ` Denis Efremov
2020-06-17 21:31         ` Denis Efremov
2020-06-17 21:31         ` Denis Efremov
2020-06-17 23:12         ` Joe Perches
2020-06-17 23:12           ` Joe Perches
2020-06-17 23:12           ` Joe Perches
2020-06-17 23:12           ` Joe Perches
2020-06-17 23:12           ` Joe Perches
2020-06-17 23:12           ` Joe Perches
2020-06-16 23:01     ` David Sterba
2020-06-16 23:01       ` David Sterba
2020-06-16 23:01       ` David Sterba
2020-06-16 23:01       ` David Sterba
2020-06-16 23:01       ` David Sterba
2020-06-16 23:01       ` David Sterba
2020-06-17  0:37       ` Matthew Wilcox
2020-06-17  0:37         ` Matthew Wilcox
2020-06-17  0:37         ` Matthew Wilcox
2020-06-17  0:37         ` Matthew Wilcox
2020-06-17  0:37         ` Matthew Wilcox
2020-06-17  7:12         ` Michal Hocko
2020-06-17  7:12           ` Michal Hocko
2020-06-17  7:12           ` Michal Hocko
2020-06-17  7:12           ` Michal Hocko
2020-06-17  7:12           ` Michal Hocko
2020-06-17  7:12           ` Michal Hocko
     [not found]           ` <20200617071212.GJ9499-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2020-06-17 11:08             ` Matthew Wilcox
2020-06-17 11:08               ` Matthew Wilcox
2020-06-17 11:08               ` Matthew Wilcox
2020-06-17 11:08               ` Matthew Wilcox
2020-06-17 11:08               ` Matthew Wilcox
2020-06-17 11:08               ` Matthew Wilcox
     [not found]               ` <20200617110820.GG8681-PfSpb0PWhxZc2C7mugBRk2EX/6BAtgUQ@public.gmane.org>
2020-06-17 11:31                 ` Michal Hocko
2020-06-17 11:31                   ` Michal Hocko
2020-06-17 11:31                   ` Michal Hocko
2020-06-17 11:31                   ` Michal Hocko
2020-06-17 11:31                   ` Michal Hocko
2020-06-17 11:31                   ` Michal Hocko
     [not found]                   ` <20200617113157.GM9499-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2020-06-17 12:23                     ` Matthew Wilcox
2020-06-17 12:23                       ` Matthew Wilcox
2020-06-17 12:23                       ` Matthew Wilcox
2020-06-17 12:23                       ` Matthew Wilcox
2020-06-17 12:23                       ` Matthew Wilcox
2020-06-17 12:23                       ` Matthew Wilcox
     [not found]                       ` <20200617122321.GJ8681-PfSpb0PWhxZc2C7mugBRk2EX/6BAtgUQ@public.gmane.org>
2020-06-17 12:55                         ` Michal Hocko
2020-06-17 12:55                           ` Michal Hocko
2020-06-17 12:55                           ` Michal Hocko
2020-06-17 12:55                           ` Michal Hocko
2020-06-17 12:55                           ` Michal Hocko
2020-06-17 12:55                           ` Michal Hocko
2020-06-17  8:03         ` Jo -l
2020-06-17  8:03           ` Jo -l
2020-06-17  8:03           ` Jo -l
2020-06-17  8:03           ` Jo -l
2020-06-17  8:03           ` Jo -l
2020-06-17  8:03           ` Jo -l
2020-06-17  0:37       ` Matthew Wilcox

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=20200616090807.GK4151@kadam \
    --to=dan.carpenter-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=Jason-OnJsPKxuuEcAvxtiuMwx3w@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org \
    --cc=dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=ecryptfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org \
    --cc=kasan-dev-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fscrypt-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
    --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-sctp-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-stm32-XDFAJ8BFU24N7RejjzZ/Li2xQDfSxrLKVpNB7YpNyf8@public.gmane.org \
    --cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=willy-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=wireguard-/J5FBtcyxH5ZwnvJuMANYw@public.gmane.org \
    /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.