From: Li Zefan <lizefan@huawei.com>
To: Anurup m <anurup.m@huawei.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
shyju pv <shyju.pv@huawei.com>,
Sanil kumar <sanil.kumar@huawei.com>,
Nataraj m <nataraj.m@huawei.com>
Subject: Re: [ PATCH ] Memory leak fix for bug 57101.
Date: Thu, 25 Apr 2013 19:31:23 +0800 [thread overview]
Message-ID: <5179140B.3060002@huawei.com> (raw)
In-Reply-To: <D2393EB95A9993478029A6FE6A290A9F15F504C9@szxeml510-mbx.china.huawei.com>
On 2013/4/25 18:05, Anurup m wrote:
> Hi All,
>
> There is a kernel memory leak observed when the proc file /proc/fs/fscache/stats is read.
> The reason is that in fscache_stats_open, single_open is called and respective release function is not called during release.
> Hence fix with correct release function - single_release. The patch is as below
>
The fix is obviously corect, but the patch is mangled so you should configure your
email client properly. Read Documention/email-clients.txt.
And when you've done that, remember Cc maintainers when you resend this patch, i.e.
David Howells <dhowells@redhat.com> and Andrew Morton <akpm@linux-foundation.org>
in this case.
> diff -uprN -X linux-3.9-rc8-vanilla/Documentation/dontdiff linux-3.9-rc8-vanilla/fs/fscache/stats.c linux-3.9-rc8.mod/fs/fscache/stats.c
> --- linux-3.9-rc8-vanilla/fs/fscache/stats.c 2013-04-22 03:08:45.000000000 +0530
> +++ linux-3.9-rc8.mod/fs/fscache/stats.c 2013-04-24 23:03:31.531296160 +0530
> @@ -287,5 +287,5 @@ const struct file_operations fscache_sta
> .open = fscache_stats_open,
> .read = seq_read,
> .llseek = seq_lseek,
> - .release = seq_release,
> + .release = single_release,
Look the tab was replaced with spaces.
next prev parent reply other threads:[~2013-04-25 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 10:05 [ PATCH ] Memory leak fix for bug 57101 Anurup m
2013-04-25 11:31 ` Li Zefan [this message]
2013-04-25 13:49 ` Anurup m
2013-04-25 20:29 ` Andrew Morton
2013-04-26 9:18 ` Anurup m
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=5179140B.3060002@huawei.com \
--to=lizefan@huawei.com \
--cc=anurup.m@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nataraj.m@huawei.com \
--cc=sanil.kumar@huawei.com \
--cc=shyju.pv@huawei.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.