linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yu Zhao <yuzhao@google.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Linux-MM <linux-mm@kvack.org>
Subject: Re: [bug report] mm: multi-gen LRU: debugfs interface
Date: Mon, 22 Aug 2022 10:49:20 -0600	[thread overview]
Message-ID: <CAOUHufZoysZ+Yv4P6=L0jTtkb655ThOELJ5KLOu4veOgdq4dfQ@mail.gmail.com> (raw)
In-Reply-To: <YwNm06F4v7XF8zX5@kili>

On Mon, Aug 22, 2022 at 5:22 AM Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> Hello Yu Zhao,
>
> The patch e02f70ddcaca: "mm: multi-gen LRU: debugfs interface" from
> Aug 15, 2022, leads to the following Smatch static checker warning:
>
>         mm/vmscan.c:5706 lru_gen_seq_write()
>         warn: uncapped user index 'cur[end]'
>
> mm/vmscan.c
>     5654 static ssize_t lru_gen_seq_write(struct file *file, const char __user *src,
>     5655                                  size_t len, loff_t *pos)

...

>     5704                 n = sscanf(cur, "%c %u %u %lu %n %u %n %lu %n", &cmd, &memcg_id, &nid,
>     5705                            &seq, &end, &swappiness, &end, &opt, &end);
> --> 5706                 if (n < 4 || cur[end]) {
>                                       ^^^^^^^^
> The static checker is correct that "end" comes from the user and it
> can be any unsigned int.

Thanks. No, %n is not a conversion -- sscanf() stores the number of
chars consumed so far upon seeing it.

What would be the recommended way to suppress this warning, if there is one?

> This is debugfs code so there is no security
> impact.
>
>     5707                         err = -EINVAL;
>     5708                         break;
>     5709                 }


  reply	other threads:[~2022-08-22 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 11:21 Dan Carpenter
2022-08-22 16:49 ` Yu Zhao [this message]
2022-08-23  6:39   ` Dan Carpenter

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='CAOUHufZoysZ+Yv4P6=L0jTtkb655ThOELJ5KLOu4veOgdq4dfQ@mail.gmail.com' \
    --to=yuzhao@google.com \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-mm@kvack.org \
    /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