From: "chenjun (AM)" <chenjun102@huawei.com>
To: Feng Tang <feng.tang@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mhocko@suse.com" <mhocko@suse.com>,
"Xiangrui (Euler)" <rui.xiang@huawei.com>
Subject: Re: [PATCH v2 1/1] mm: Fix the uninitialized use in overcommit_policy_handler
Date: Thu, 23 Sep 2021 01:56:27 +0000 [thread overview]
Message-ID: <6776dd3a8d9e4618b36110604d1e58dd@huawei.com> (raw)
In-Reply-To: <20210922153425.GB68763@shbuild999.sh.intel.com>
Hi Tang,
在 2021/9/22 23:34, Feng Tang 写道:
> Hi Jun,
>
> On Wed, Sep 22, 2021 at 01:41:22AM +0000, Chen Jun wrote:
>> An unexpected value of /proc/sys/vm/panic_on_oom we will get,
>> after running the following program.
>>
>> int main()
>> {
>> int fd = open("/proc/sys/vm/panic_on_oom", O_RDWR)
>
> should this be "/proc/sys/vm/overcommit_memory"
>
Sorry, that is my mistake, I will correct it in v3. Thanks.
>> 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.
>
> Other than the nit above, it looks good to me, thanks!
>
> Reviewed-by: Feng Tang <feng.tang@intel.com>
>
>> Fixes: 56f3547bfa4d ("mm: adjust vm_committed_as_batch according to vm overcommit policy"
>> Signed-off-by: Chen Jun <chenjun102@huawei.com>
>> ---
>>
>> v2:
>> * Check whether new_policy has been changed by proc_dointvec_minmax.
>>
>> mm/util.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/util.c b/mm/util.c
>> index 4ddb6e186dd5..d5be67771850 100644
>> --- a/mm/util.c
>> +++ b/mm/util.c
>> @@ -756,7 +756,7 @@ int overcommit_policy_handler(struct ctl_table *table, int write, void *buffer,
>> size_t *lenp, loff_t *ppos)
>> {
>> struct ctl_table t;
>> - int new_policy;
>> + int new_policy = -1;
>> int ret;
>>
>> /*
>> @@ -774,7 +774,7 @@ int overcommit_policy_handler(struct ctl_table *table, int write, void *buffer,
>> t = *table;
>> t.data = &new_policy;
>> ret = proc_dointvec_minmax(&t, write, buffer, lenp, ppos);
>> - if (ret)
>> + if (ret || new_policy == -1)
>> return ret;
>>
>> mm_compute_batch(new_policy);
>> --
>> 2.17.1
>>
>
--
Regards
Chen Jun
prev parent reply other threads:[~2021-09-23 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 1:41 Chen Jun
2021-09-22 8:35 ` Michal Hocko
2021-09-22 15:34 ` Feng Tang
2021-09-23 1:56 ` chenjun (AM) [this message]
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=6776dd3a8d9e4618b36110604d1e58dd@huawei.com \
--to=chenjun102@huawei.com \
--cc=akpm@linux-foundation.org \
--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