From: Andrew Morton <akpm@linux-foundation.org>
To: Chen Jun <chenjun102@huawei.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<feng.tang@intel.com>, <mhocko@suse.com>, <rui.xiang@huawei.com>
Subject: Re: [PATCH v3 1/1] mm: Fix the uninitialized use in overcommit_policy_handler
Date: Thu, 23 Sep 2021 19:23:12 -0700 [thread overview]
Message-ID: <20210923192312.53dbe65db0375038c99defaa@linux-foundation.org> (raw)
In-Reply-To: <20210923020524.13289-1-chenjun102@huawei.com>
On Thu, 23 Sep 2021 02:05:24 +0000 Chen Jun <chenjun102@huawei.com> wrote:
> An unexpected value of /proc/sys/vm/overcommit_memory we will get,
> after running the following program.
>
> int main()
> {
> int fd = open("/proc/sys/vm/overcommit_memory", O_RDWR)
> write(fd, "1", 1);
> write(fd, "2", 1);
> close(fd);
> }
>
> write(fd, "2", 1) will pass *ppos = 1 to proc_dointvec_minmax.
> proc_dointvec_minmax will return 0 without setting new_policy.
>
> t.data = &new_policy;
> ret = proc_dointvec_minmax(&t, write, buffer, lenp, ppos)
> -->do_proc_dointvec
> -->__do_proc_dointvec
> if (write) {
> if (proc_first_pos_non_zero_ignore(ppos, table))
> goto out;
>
> sysctl_overcommit_memory = new_policy;
>
> so sysctl_overcommit_memory will be set to an uninitialized value.
>
> Check whether new_policy has been changed by proc_dointvec_minmax.
>
Thanks. I added a cc:stable to this, so the fix will be backported
into earlier kernels.
next prev parent reply other threads:[~2021-09-24 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 2:05 [PATCH v3 1/1] mm: Fix the uninitialized use in overcommit_policy_handler Chen Jun
2021-09-24 2:23 ` Andrew Morton [this message]
2021-09-24 2:41 ` Kefeng Wang
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=20210923192312.53dbe65db0375038c99defaa@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chenjun102@huawei.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rui.xiang@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 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).