From: Qi Zheng <zhengqi.arch@bytedance.com>
To: Yu Zhao <yuzhao@google.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Andi Kleen" <ak@linux.intel.com>,
"Aneesh Kumar" <aneesh.kumar@linux.ibm.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Hillf Danton" <hdanton@sina.com>, "Jens Axboe" <axboe@kernel.dk>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Matthew Wilcox" <willy@infradead.org>,
"Mel Gorman" <mgorman@suse.de>,
"Michael Larabel" <Michael@michaellarabel.com>,
"Michal Hocko" <mhocko@kernel.org>,
"Mike Rapoport" <rppt@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Tejun Heo" <tj@kernel.org>, "Vlastimil Babka" <vbabka@suse.cz>,
"Will Deacon" <will@kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Kernel Page Reclaim v2" <page-reclaim@google.com>,
"Brian Geffon" <bgeffon@google.com>,
"Jan Alexander Steffens" <heftig@archlinux.org>,
"Oleksandr Natalenko" <oleksandr@natalenko.name>,
"Steven Barrett" <steven@liquorix.net>,
"Suleiman Souhlal" <suleiman@google.com>,
"Daniel Byrne" <djbyrne@mtu.edu>,
"Donald Carr" <d@chaos-reins.com>,
"Holger Hoffstätte" <holger@applied-asynchrony.com>,
"Konstantin Kharlamov" <Hi-Angel@yandex.ru>,
"Shuang Zhai" <szhai2@cs.rochester.edu>,
"Sofia Trinh" <sofia.trinh@edi.works>,
"Vaibhav Jain" <vaibhav@linux.ibm.com>
Subject: Re: [PATCH v12 12/14] mm: multi-gen LRU: debugfs interface
Date: Thu, 23 Jun 2022 10:36:10 +0800 [thread overview]
Message-ID: <2d607f47-71fa-9505-b355-7203eb327bab@bytedance.com> (raw)
In-Reply-To: <CAOUHufZ8xaVKZD7LNeo8AZv_xywvwef4P8CjdO+npijLHEUfWg@mail.gmail.com>
On 2022/6/23 03:13, Yu Zhao wrote:
> On Wed, Jun 22, 2022 at 3:16 AM Qi Zheng <zhengqi.arch@bytedance.com> wrote:
>
>>> +static ssize_t lru_gen_seq_write(struct file *file, const char __user *src,
>>> + size_t len, loff_t *pos)
>>> +{
>>> + void *buf;
>>> + char *cur, *next;
>>> + unsigned int flags;
>>> + struct blk_plug plug;
>>> + int err = -EINVAL;
>>> + struct scan_control sc = {
>>> + .may_writepage = true,
>>> + .may_unmap = true,
>>> + .may_swap = true,
>>> + .reclaim_idx = MAX_NR_ZONES - 1,
>>> + .gfp_mask = GFP_KERNEL,
>>> + };
>>> +
>>> + buf = kvmalloc(len + 1, GFP_KERNEL);
>>> + if (!buf)
>>> + return -ENOMEM;
>>> +
>>> + if (copy_from_user(buf, src, len)) {
>>> + kvfree(buf);
>>> + return -EFAULT;
>>> + }
>>> +
>>> + if (!set_mm_walk(NULL)) {
>>
>> The current->reclaim_state will be dereferenced in set_mm_walk(), so
>> calling set_mm_walk() before set_task_reclaim_state(current,
>> &sc.reclaim_state) will cause panic:
>>
>> [ 1861.154916] BUG: kernel NULL pointer dereference, address:
>> 0000000000000008
>
> Thanks.
>
> Apparently I shot myself in the foot by one of the nits between v11 and v12.
>
>>> + kvfree(buf);
>>> + return -ENOMEM;
>>> + }
>>> +
>>> + set_task_reclaim_state(current, &sc.reclaim_state);
>>> + flags = memalloc_noreclaim_save();
>>> + blk_start_plug(&plug);
>>> +
>>> + next = buf;
>>> + next[len] = '\0';
>>> +
>>> + while ((cur = strsep(&next, ",;\n"))) {
>>> + int n;
>>> + int end;
>>> + char cmd;
>>> + unsigned int memcg_id;
>>> + unsigned int nid;
>>> + unsigned long seq;
>>> + unsigned int swappiness = -1;
>>> + unsigned long opt = -1;
>>> +
>>> + cur = skip_spaces(cur);
>>> + if (!*cur)
>>> + continue;
>>> +
>>> + n = sscanf(cur, "%c %u %u %lu %n %u %n %lu %n", &cmd, &memcg_id, &nid,
>>> + &seq, &end, &swappiness, &end, &opt, &end);
>>> + if (n < 4 || cur[end]) {
>>> + err = -EINVAL;
>>> + break;
>>> + }
>>> +
>>> + err = run_cmd(cmd, memcg_id, nid, seq, &sc, swappiness, opt);
>>> + if (err)
>>> + break;
>>> + }
>>> +
>>> + blk_finish_plug(&plug);
>>> + memalloc_noreclaim_restore(flags);
>>> + set_task_reclaim_state(current, NULL);
>>> +
>>> + clear_mm_walk();
>>
>> Ditto, we can't call clear_mm_walk() after
>> set_task_reclaim_state(current, NULL).
>>
>> Maybe it can be modified as follows:
>>
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index 2422edc786eb..552e6ae5243e 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -5569,12 +5569,12 @@ static ssize_t lru_gen_seq_write(struct file
>> *file, const char __user *src,
>> return -EFAULT;
>> }
>>
>> + set_task_reclaim_state(current, &sc.reclaim_state);
>> if (!set_mm_walk(NULL)) {
>> kvfree(buf);
>> return -ENOMEM;
>> }
>>
>> - set_task_reclaim_state(current, &sc.reclaim_state);
>
> We need a `goto` because otherwise we leave a dangling
Yes, right. With this:
Reviewed-by: Qi Zheng <zhengqi.arch@bytedance.com>
> `current->reclaim_state`. (I swear I had one.)
(I believe :))
--
Thanks,
Qi
next prev parent reply other threads:[~2022-06-23 2:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 7:16 [PATCH v12 00/14] Multi-Gen LRU Framework Yu Zhao
2022-06-14 7:16 ` [PATCH v12 01/14] mm: x86, arm64: add arch_has_hw_pte_young() Yu Zhao
2022-06-14 7:16 ` [PATCH v12 02/14] mm: x86: add CONFIG_ARCH_HAS_NONLEAF_PMD_YOUNG Yu Zhao
2022-06-14 7:16 ` [PATCH v12 03/14] mm/vmscan.c: refactor shrink_node() Yu Zhao
2022-06-14 7:16 ` [PATCH v12 04/14] Revert "include/linux/mm_inline.h: fold __update_lru_size() into its sole caller" Yu Zhao
2022-06-14 7:16 ` [PATCH v12 05/14] mm: multi-gen LRU: groundwork Yu Zhao
2022-06-14 7:16 ` [PATCH v12 06/14] mm: multi-gen LRU: minimal implementation Yu Zhao
2022-06-14 7:16 ` [PATCH v12 07/14] mm: multi-gen LRU: exploit locality in rmap Yu Zhao
2022-06-29 4:44 ` Barry Song
2022-06-14 7:16 ` [PATCH v12 08/14] mm: multi-gen LRU: support page table walks Yu Zhao
2022-06-14 7:23 ` Yu Zhao
2022-06-14 7:16 ` [PATCH v12 09/14] mm: multi-gen LRU: optimize multiple memcgs Yu Zhao
2022-06-14 7:16 ` [PATCH v12 10/14] mm: multi-gen LRU: kill switch Yu Zhao
2022-06-14 7:16 ` [PATCH v12 11/14] mm: multi-gen LRU: thrashing prevention Yu Zhao
2022-06-14 7:16 ` [PATCH v12 12/14] mm: multi-gen LRU: debugfs interface Yu Zhao
2022-06-22 9:16 ` Qi Zheng
2022-06-22 19:13 ` Yu Zhao
2022-06-23 2:36 ` Qi Zheng [this message]
2022-06-14 7:16 ` [PATCH v12 13/14] mm: multi-gen LRU: admin guide Yu Zhao
2022-06-14 7:16 ` [PATCH v12 14/14] mm: multi-gen LRU: design doc Yu Zhao
2022-06-22 6:21 ` [PATCH v12 00/14] Multi-Gen LRU Framework Yu Zhao
2022-06-22 18:45 ` Andrew Morton
2022-06-22 18:58 ` Yu Zhao
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=2d607f47-71fa-9505-b355-7203eb327bab@bytedance.com \
--to=zhengqi.arch@bytedance.com \
--cc=Hi-Angel@yandex.ru \
--cc=Michael@michaellarabel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=bgeffon@google.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=d@chaos-reins.com \
--cc=dave.hansen@linux.intel.com \
--cc=djbyrne@mtu.edu \
--cc=hannes@cmpxchg.org \
--cc=hdanton@sina.com \
--cc=heftig@archlinux.org \
--cc=holger@applied-asynchrony.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=oleksandr@natalenko.name \
--cc=page-reclaim@google.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=sofia.trinh@edi.works \
--cc=steven@liquorix.net \
--cc=suleiman@google.com \
--cc=szhai2@cs.rochester.edu \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vaibhav@linux.ibm.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=yuzhao@google.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