Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1737391yba; Thu, 9 May 2019 23:37:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqzfs5W9a+XNn41FdLAhdR8tW58Nb8KVeEaQd6IfA2/TKfy7wptVa9fTZsq869I1HNl06YSY X-Received: by 2002:a62:ee0a:: with SMTP id e10mr11534029pfi.6.1557470249923; Thu, 09 May 2019 23:37:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557470249; cv=none; d=google.com; s=arc-20160816; b=LwxBZw8ab7WwdG3pY73t/kjadVGg2zmgpAMDNSKYZYoBTVNiuZeqOdJsvmyrhjRXzg TEa2S1KjPfsouN9u61z+qRKsUE+1f3jjMSS8Nd8lf9SbKTIsMvANAMpjA++x1jXNcPr2 HTIujfuR7yePLF7dZhr15ine56ytc6HocRgCp+OHqbVadrLndbQF1qyIO+Q2MlMJfJa7 N5CgwcS+6RP/Yc4y1es13twMDnxuTpIR7mwI1cbZBPpJAIzgBpPFJjdUs6XIr2CjWsaa K/iOc/QW7N6bh9UI9G0SsFtbIpNpzey1sDW+Ojwclhi2zvlP++GQx6D69s5sQ1fpCMru qudw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature; bh=vT8J+5xe8+a83KFHodncMBgwSSqGKELQF/J0hFsWGtA=; b=EHWO2xmqev68ePdx9901s4rB/Mi+mb9cATcaiqOsuEnKXwdXyGTwKPJxif4r4FY7VE +L/1wU3sh1jVB4v8NRhhVY0+2VI5t+4ihGqOXDJTITBpdXbz41pQfdTPOw7UcjVj9hn4 e6R9K57vmEfCaqJZJAMJKJmx2TwV0SLmrZBXbgCCnzh0eNQuKHBeiAkRuzqyv/z9GRE2 lzhKfDQ9g+4Hm3btL04Aoob8cK2Tk80ZMu1eAkuSB5XyiAN5pO7EGaxqjxA+2fEP5/72 LdbM1afJ4OV49mVDsZDBhlprdiVlhxKw0dClakhgdLSRiuTcMoDDJCOWhl8wMh5LW9vG DkjQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qw5fJbIG; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 5si6539845pgz.231.2019.05.09.23.37.01; Thu, 09 May 2019 23:37:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qw5fJbIG; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727000AbfEJGgz (ORCPT + 99 others); Fri, 10 May 2019 02:36:55 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:44296 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726983AbfEJGgz (ORCPT ); Fri, 10 May 2019 02:36:55 -0400 Received: by mail-pg1-f195.google.com with SMTP id z16so2495969pgv.11; Thu, 09 May 2019 23:36:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=vT8J+5xe8+a83KFHodncMBgwSSqGKELQF/J0hFsWGtA=; b=qw5fJbIGPWcA28KqHaWQHU/4N2mlSVKQW5V8JZ3jxW1bmtyoGCRFuE54VT++XfaTJk ECxfJP3LMFFdmQKpmVSMTUFPSj7EQEhyrpUmvoWn/JXvQhhTXtoIPmM7IVQnrvIX4sGC luQbTA0HnLqWm4CZGiDjuLFIht94D1/x4evanFtBzUyXK3HUy10849a4P5DDwa+tUzMm DoYdzXrW0LGwGe+Jqc5v7SWv9BHbuNCuFUEYQwMhetftF7i5eySCSCclPrmkA4t0cNpI kbUsdwY722an5VqZDnc9t9W0IB87r2MsZAstjN8j1nZ1EE/0htDpUiHwk4gyh8iio2s3 U9WQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=vT8J+5xe8+a83KFHodncMBgwSSqGKELQF/J0hFsWGtA=; b=JfQNZkXFzQutdtHDMWk2DIE0YH9/Yf5EC7v/NpxJ9aZLr9y8SCUyeNSkcBiPfkhEBJ PZHInS0c/3y87g81XcK0mvOYliNBrVro/9yYlivT/DJQo6CCB6IzTOS8wZL5+s8bky8Z qkw+WL/NmiVGXnB0VCKrP5kunyN62CAqLw0LnvN7C3tJXHnYyp73XfMToX44DRdoLtcy N5P6HoeX4m8jpg57OhFC/w+owCiUMAmeoBWMiLxdz0FTtb90thFOdXIEW0YjOEpsjM9M nsXJeLfusjv6Zs0PvacVLwdphMIBON/RumLMFj/hujnFCgTBS77PIhm2G8cupymF0z6+ jqiA== X-Gm-Message-State: APjAAAVFU77qHIgHL+fyu5KS+6kmlbDQJaj7B1iW/c1z6H0KG+IkaRYJ UroImobV1RWP3nTsh7O/DRo= X-Received: by 2002:aa7:9109:: with SMTP id 9mr11557887pfh.244.1557470214902; Thu, 09 May 2019 23:36:54 -0700 (PDT) Received: from bridge.localdomain ([119.28.31.106]) by smtp.gmail.com with ESMTPSA id v6sm4469263pgi.88.2019.05.09.23.36.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 May 2019 23:36:54 -0700 (PDT) From: Wenbin Zeng X-Google-Original-From: Wenbin Zeng To: bfields@fieldses.org, viro@zeniv.linux.org.uk, davem@davemloft.net Cc: jlayton@kernel.org, trond.myklebust@hammerspace.com, anna.schumaker@netapp.com, wenbinzeng@tencent.com, dsahern@gmail.com, nicolas.dichtel@6wind.com, willy@infradead.org, edumazet@google.com, jakub.kicinski@netronome.com, tyhicks@canonical.com, chuck.lever@oracle.com, neilb@suse.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-nfs@vger.kernel.org Subject: [PATCH v2 0/3] auth_gss: netns refcount leaks when use-gss-proxy==1 Date: Fri, 10 May 2019 14:36:00 +0800 Message-Id: <1557470163-30071-1-git-send-email-wenbinzeng@tencent.com> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <1556692945-3996-1-git-send-email-wenbinzeng@tencent.com> References: <1556692945-3996-1-git-send-email-wenbinzeng@tencent.com> Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org This patch series fixes an auth_gss bug that results in netns refcount leaks when use-gss-proxy is set to 1. The problem was found in privileged docker containers with gssproxy service enabled and /proc/net/rpc/use-gss-proxy set to 1, the corresponding struct net->count ends up at 2 after container gets killed, the consequence is that the struct net cannot be freed. It turns out that write_gssp() called gssp_rpc_create() to create a rpc client, this increases net->count by 2; rpcsec_gss_exit_net() is supposed to decrease net->count but it never gets called because its call-path is: net->count==0 -> cleanup_net -> ops_exit_list -> rpcsec_gss_exit_net Before rpcsec_gss_exit_net() gets called, net->count cannot reach 0, this is a deadlock situation. To fix the problem, we must break the deadlock, rpcsec_gss_exit_net() should move out of the put() path and find another chance to get called, I think nsfs_evict() is a good place to go, when netns inode gets evicted we call rpcsec_gss_exit_net() to free the rpc client, this requires a new callback i.e. evict to be added in struct proc_ns_operations, and add netns_evict() as one of netns_operations as well. v1->v2: * in nsfs_evict(), move ->evict() in front of ->put() Wenbin Zeng (3): nsfs: add evict callback into struct proc_ns_operations netns: add netns_evict into netns_operations auth_gss: fix deadlock that blocks rpcsec_gss_exit_net when use-gss-proxy==1 fs/nsfs.c | 2 ++ include/linux/proc_ns.h | 1 + include/net/net_namespace.h | 1 + net/core/net_namespace.c | 12 ++++++++++++ net/sunrpc/auth_gss/auth_gss.c | 9 ++++++--- 5 files changed, 22 insertions(+), 3 deletions(-) -- 1.8.3.1