Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp2334681imm; Sat, 9 Jun 2018 12:52:45 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKsVgCQdnbGXGmlfRg837pPZePKJQhQF4F2HSawHAW4emtYiUzLkHdolO7lrz/rs2QoNbCl X-Received: by 2002:a17:902:a518:: with SMTP id s24-v6mr9355058plq.144.1528573965511; Sat, 09 Jun 2018 12:52:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528573965; cv=none; d=google.com; s=arc-20160816; b=jmgl25/6B0tC+vO6w9HcKPtqneKIKLi1KBBD/942esPPCSgGVhXgZSlEezbyQNGWsr EkLGaGN4jRj2wU06ONtHzBjDNKtYifs76B12yvLCn0RzCbVbevbVGitR0TSU3qh1gKWd 5LD3J4boA9l4dfAgvxWNzf8gUOt/+1WqZvv/QZw78+dquRMg1v4xO/jOmp/1I3arK4xI +ufBerD9X/Np0veJmyvmF8xKGtkHHibVLOoy77oc0w7Yd2HzhubzgWnGu+RFBzW41cPv 9lHGUHngKKTydzw9SmVPLwd2EvXd3VFpaBZGmxJQYCT/2GHE/cQzNCi5o67e1XZF8y8S BUcg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=KHzXuxfY7u2yaZHR12/wA8K9WJ0ace6/2g7hmKohvK8=; b=hqVylrc9ew4w3KSupJeJOp4cf2uBAUjUTwtRFHeitz0wdHOT847nmC0MXv0lO89VxH DhcD8oMTbun1xlRMAE6FocLVPtRl4QQMwJ5Vb+uBBJKYuSmSJKtPij9It9nKwreCJcHa I8Lgmllr3ehFNZSB+GATCNwr65QCtWbvGGHxFal6PFcf0xunURyk590bb7zsHTyzRGLm L4nTEtDGAZvk+vbscsRYEDLhJ4Fcr9cyX7x7Yuxe3U9LEvFOYJiZ9g6Ww4J3EqASAd1Q ANWiMI81dzSNBPSHPwSMjh/vpsy8XQVh/+snGKysoZ0kCC7+5AhNu+zoRn14otmISv7V 5/DA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 31-v6si22086673pli.45.2018.06.09.12.52.31; Sat, 09 Jun 2018 12:52:45 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932489AbeFITvb (ORCPT + 99 others); Sat, 9 Jun 2018 15:51:31 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:49614 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753449AbeFITva (ORCPT ); Sat, 9 Jun 2018 15:51:30 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 899F0857A7; Sat, 9 Jun 2018 19:51:29 +0000 (UTC) Received: from dhcp-12-107.nay.redhat.com (unknown [10.66.12.107]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B4AC52156601; Sat, 9 Jun 2018 19:51:27 +0000 (UTC) From: Chunyu Hu To: viro@zeniv.linux.org.uk, hch@lst.de Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH] proc: add proc_seq_release Date: Sun, 10 Jun 2018 03:51:24 +0800 Message-Id: <1528573884-9133-1-git-send-email-chuhu@redhat.com> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Sat, 09 Jun 2018 19:51:29 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Sat, 09 Jun 2018 19:51:29 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'chuhu@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org kmemleak reported some memory leak on reading proc files. After adding some debug lines, find that proc_seq_fops is using seq_release as release handler, which won't handle the free of 'private' field of seq_file, while in fact the open handler proc_seq_open could create the private data with __seq_open_private when state_size is greater than zero. So after reading files created with proc_create_seq_private, such as /proc/timer_list and /proc/vmallocinfo, the private mem of a seq_file is not freed. Fix it by adding the paired proc_seq_release as the default release handler of proc_seq_ops instead of seq_release. Fixes: 44414d82cfe0 ("proc: introduce proc_create_seq_private") CC: Christoph Hellwig Signed-off-by: Chunyu Hu --- fs/proc/generic.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/fs/proc/generic.c b/fs/proc/generic.c index 7b4d971..021acc5 100644 --- a/fs/proc/generic.c +++ b/fs/proc/generic.c @@ -564,11 +564,20 @@ static int proc_seq_open(struct inode *inode, struct file *file) return seq_open(file, de->seq_ops); } +static int proc_seq_release(struct inode *inode, struct file *file) +{ + struct proc_dir_entry *de = PDE(inode); + + if (de->state_size) + return seq_release_private(inode, file); + return seq_release(inode, file); +} + static const struct file_operations proc_seq_fops = { .open = proc_seq_open, .read = seq_read, .llseek = seq_lseek, - .release = seq_release, + .release = proc_seq_release, }; struct proc_dir_entry *proc_create_seq_private(const char *name, umode_t mode, -- 1.8.3.1