linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yang Shi <yang.shi@linux.alibaba.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-mm@kvack.org
Subject: Re: [bug report] mm: brk: downgrade mmap_sem to read when shrinking
Date: Wed, 10 Oct 2018 09:31:52 -0700	[thread overview]
Message-ID: <d2d0ed7b-5a5e-9263-7561-18d75ff354ac@linux.alibaba.com> (raw)
In-Reply-To: <20181010104420.GA15538@mwanda>

Hi Dan,


Thanks for reporting this bug. Colin Ian King reported the same issue a 
couple of days ago, please see 
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1780112.html.


And, the fixes have been merged into Andrew's -mm tree.


Regards,

Yang



On 10/10/18 3:44 AM, Dan Carpenter wrote:
> Hello Yang Shi,
>
> The patch ca761a3ea456: "mm: brk: downgrade mmap_sem to read when
> shrinking" from Oct 4, 2018, leads to the following static checker
> warning:
>
> 	mm/mmap.c:252 __do_sys_brk()
> 	warn: unsigned 'retval' is never less than zero.
>
> mm/mmap.c
>     223          /*
>     224           * Check against rlimit here. If this check is done later after the test
>     225           * of oldbrk with newbrk then it can escape the test and let the data
>     226           * segment grow beyond its set limit the in case where the limit is
>     227           * not page aligned -Ram Gupta
>     228           */
>     229          if (check_data_rlimit(rlimit(RLIMIT_DATA), brk, mm->start_brk,
>     230                                mm->end_data, mm->start_data))
>     231                  goto out;
>     232
>     233          newbrk = PAGE_ALIGN(brk);
>     234          oldbrk = PAGE_ALIGN(mm->brk);
>     235          if (oldbrk == newbrk) {
>     236                  mm->brk = brk;
>     237                  goto success;
>     238          }
>     239
>     240          /*
>     241           * Always allow shrinking brk.
>     242           * __do_munmap() may downgrade mmap_sem to read.
>     243           */
>     244          if (brk <= mm->brk) {
>     245                  /*
>     246                   * mm->brk must to be protected by write mmap_sem so update it
>     247                   * before downgrading mmap_sem. When __do_munmap() fails,
>     248                   * mm->brk will be restored from origbrk.
>     249                   */
>     250                  mm->brk = brk;
>     251                  retval = __do_munmap(mm, newbrk, oldbrk-newbrk, &uf, true);
>     252                  if (retval < 0) {
>                              ^^^^^^^^^^
> Impossible.
>
>     253                          mm->brk = origbrk;
>     254                          goto out;
>     255                  } else if (retval == 1)
>     256                          downgraded = true;
>     257                  goto success;
>     258          }
>     259
>
> See also:
> mm/mremap.c:571 __do_sys_mremap() warn: unsigned 'ret' is never less than zero.
>
> regards,
> dan carpenter

      reply	other threads:[~2018-10-10 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 10:44 Dan Carpenter
2018-10-10 16:31 ` Yang Shi [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=d2d0ed7b-5a5e-9263-7561-18d75ff354ac@linux.alibaba.com \
    --to=yang.shi@linux.alibaba.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