All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Wei Yongjun <yjwei@cn.fujitsu.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] net: Fix module refcount leak in kernel_accept()
Date: Fri, 19 Dec 2008 07:35:37 +0100	[thread overview]
Message-ID: <1229668537.17082.15.camel@violet> (raw)
In-Reply-To: <494A23FE.6020305@cn.fujitsu.com>

Hi Wei,

> The kernel_accept() does not hold the module refcount of newsock->ops->owner,
> so we need __module_get(newsock->ops->owner) code after call kernel_accept()
> by hand.
> In sunrpc, the module refcount is missing to hold. So this cause kernel panic.
> 
> Used following script to reproduct:
> 
> while [ 1 ];
> do
>     mount -t nfs4 192.168.0.19:/ /mnt
>     touch /mnt/file
>     umount /mnt
>     lsmod | grep ipv6
> done
> 
> This patch fixed the problem by add __module_get(newsock->ops->owner) to
> kernel_accept(). So we do not need to used __module_get(newsock->ops->owner)
> in every place when used kernel_accept().
> 
> Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
> ---
>  net/bluetooth/rfcomm/core.c |    2 --
>  net/socket.c                |    1 +
>  2 files changed, 1 insertions(+), 2 deletions(-)

I was just about to reply and ask you to double check the users since I
know that I am using that API. Hey, but you already did that. Thanks.

Dave, for what its worth, Acked-by me.

Regards

Marcel



  parent reply	other threads:[~2008-12-19  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 10:20 [PATCH] net: Fix module refcount leak in kernel_accept() Wei Yongjun
2008-12-19  3:35 ` David Miller
2008-12-19  6:35 ` Marcel Holtmann [this message]
2008-12-19  6:39   ` David Miller

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=1229668537.17082.15.camel@violet \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=yjwei@cn.fujitsu.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.