* [PATCH 11/14] nfs: idr_destroy() no longer needs idr_remove_all()
[not found] <1359163872-1949-1-git-send-email-tj@kernel.org>
@ 2013-01-26 1:31 ` Tejun Heo
2013-01-29 22:58 ` J. Bruce Fields
0 siblings, 1 reply; 4+ messages in thread
From: Tejun Heo @ 2013-01-26 1:31 UTC (permalink / raw)
To: akpm; +Cc: rusty, linux-kernel, Tejun Heo, J. Bruce Fields, linux-nfs
idr_destroy() can destroy idr by itself and idr_remove_all() is being
deprecated. Drop reference to idr_remove_all(). Note that the code
wasn't completely correct before because idr_remove() on all entries
doesn't necessarily release all idr_layers which could lead to memory
leak.
Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
---
This patch depends on an earlier idr patch and given the trivial
nature of the patch, I think it would be best to route these together
through -mm. Please holler if there's any objection.
Thanks.
fs/nfs/client.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/nfs/client.c b/fs/nfs/client.c
index 9f3c664..84d8eae 100644
--- a/fs/nfs/client.c
+++ b/fs/nfs/client.c
@@ -197,7 +197,6 @@ error_0:
EXPORT_SYMBOL_GPL(nfs_alloc_client);
#if IS_ENABLED(CONFIG_NFS_V4)
-/* idr_remove_all is not needed as all id's are removed by nfs_put_client */
void nfs_cleanup_cb_ident_idr(struct net *net)
{
struct nfs_net *nn = net_generic(net, nfs_net_id);
--
1.8.1
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH 11/14] nfs: idr_destroy() no longer needs idr_remove_all()
2013-01-26 1:31 ` [PATCH 11/14] nfs: idr_destroy() no longer needs idr_remove_all() Tejun Heo
@ 2013-01-29 22:58 ` J. Bruce Fields
2013-01-30 2:18 ` Myklebust, Trond
0 siblings, 1 reply; 4+ messages in thread
From: J. Bruce Fields @ 2013-01-29 22:58 UTC (permalink / raw)
To: Tejun Heo; +Cc: akpm, rusty, linux-kernel, linux-nfs, Trond Myklebust
On Fri, Jan 25, 2013 at 05:31:09PM -0800, Tejun Heo wrote:
> idr_destroy() can destroy idr by itself and idr_remove_all() is being
> deprecated. Drop reference to idr_remove_all(). Note that the code
> wasn't completely correct before because idr_remove() on all entries
> doesn't necessarily release all idr_layers which could lead to memory
> leak.
Seems fine, but actually this is client-side so I think you meant the cc
to be to Trond.
--b.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: "J. Bruce Fields" <bfields@fieldses.org>
> Cc: linux-nfs@vger.kernel.org
> ---
> This patch depends on an earlier idr patch and given the trivial
> nature of the patch, I think it would be best to route these together
> through -mm. Please holler if there's any objection.
>
> Thanks.
>
> fs/nfs/client.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/fs/nfs/client.c b/fs/nfs/client.c
> index 9f3c664..84d8eae 100644
> --- a/fs/nfs/client.c
> +++ b/fs/nfs/client.c
> @@ -197,7 +197,6 @@ error_0:
> EXPORT_SYMBOL_GPL(nfs_alloc_client);
>
> #if IS_ENABLED(CONFIG_NFS_V4)
> -/* idr_remove_all is not needed as all id's are removed by nfs_put_client */
> void nfs_cleanup_cb_ident_idr(struct net *net)
> {
> struct nfs_net *nn = net_generic(net, nfs_net_id);
> --
> 1.8.1
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 11/14] nfs: idr_destroy() no longer needs idr_remove_all()
2013-01-29 22:58 ` J. Bruce Fields
@ 2013-01-30 2:18 ` Myklebust, Trond
2013-02-01 0:08 ` Tejun Heo
0 siblings, 1 reply; 4+ messages in thread
From: Myklebust, Trond @ 2013-01-30 2:18 UTC (permalink / raw)
To: J. Bruce Fields
Cc: Tejun Heo, akpm@linux-foundation.org, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Myklebust, Trond
On Tue, 2013-01-29 at 17:58 -0500, J. Bruce Fields wrote:
> On Fri, Jan 25, 2013 at 05:31:09PM -0800, Tejun Heo wrote:
> > idr_destroy() can destroy idr by itself and idr_remove_all() is being
> > deprecated. Drop reference to idr_remove_all(). Note that the code
> > wasn't completely correct before because idr_remove() on all entries
> > doesn't necessarily release all idr_layers which could lead to memory
> > leak.
>
> Seems fine, but actually this is client-side so I think you meant the cc
> to be to Trond.
Acked-by: Trond Myklebust <Trond.Myklebust@netapp.com>
No problems whatsoever with removing a comment. :-)
My worry is more about Tejun's comment that we did actually need a call
to idr_remove_all() in the original code. Do we need to queue up a fix
for the 3.8 and existing stable kernels?
Cheers
Trond
> > Signed-off-by: Tejun Heo <tj@kernel.org>
> > Cc: "J. Bruce Fields" <bfields@fieldses.org>
> > Cc: linux-nfs@vger.kernel.org
> > ---
> > This patch depends on an earlier idr patch and given the trivial
> > nature of the patch, I think it would be best to route these together
> > through -mm. Please holler if there's any objection.
> >
> > Thanks.
> >
> > fs/nfs/client.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/fs/nfs/client.c b/fs/nfs/client.c
> > index 9f3c664..84d8eae 100644
> > --- a/fs/nfs/client.c
> > +++ b/fs/nfs/client.c
> > @@ -197,7 +197,6 @@ error_0:
> > EXPORT_SYMBOL_GPL(nfs_alloc_client);
> >
> > #if IS_ENABLED(CONFIG_NFS_V4)
> > -/* idr_remove_all is not needed as all id's are removed by nfs_put_client */
> > void nfs_cleanup_cb_ident_idr(struct net *net)
> > {
> > struct nfs_net *nn = net_generic(net, nfs_net_id);
> > --
> > 1.8.1
> >
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 11/14] nfs: idr_destroy() no longer needs idr_remove_all()
2013-01-30 2:18 ` Myklebust, Trond
@ 2013-02-01 0:08 ` Tejun Heo
0 siblings, 0 replies; 4+ messages in thread
From: Tejun Heo @ 2013-02-01 0:08 UTC (permalink / raw)
To: Myklebust, Trond
Cc: J. Bruce Fields, akpm@linux-foundation.org, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Hello, Trond.
On Wed, Jan 30, 2013 at 02:18:06AM +0000, Myklebust, Trond wrote:
> My worry is more about Tejun's comment that we did actually need a call
> to idr_remove_all() in the original code. Do we need to queue up a fix
> for the 3.8 and existing stable kernels?
IIUC, the only case where idr_layer is left around after idr_remove()
on all elems is when the deletions lead to multi-level left-most
collapse. Not sure whether the current code can actually hit that.
No harm in adding idr_remove_all(), I guess.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-02-01 0:08 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1359163872-1949-1-git-send-email-tj@kernel.org>
2013-01-26 1:31 ` [PATCH 11/14] nfs: idr_destroy() no longer needs idr_remove_all() Tejun Heo
2013-01-29 22:58 ` J. Bruce Fields
2013-01-30 2:18 ` Myklebust, Trond
2013-02-01 0:08 ` Tejun Heo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).