lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210709153316.a81214a453920dbcc2714ae6@linux-foundation.org>
Date:   Fri, 9 Jul 2021 15:33:16 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Yang Huan <link@...o.com>
Cc:     linux-kernel@...r.kernel.org, linux-mm@...ck.org, kernel@...o.com,
        syzbot+b07d8440edb5f8988eea@...kaller.appspotmail.com,
        Wang Qing <wangqing@...o.com>
Subject: Re: [PATCH] mm/page_alloc: fix alloc_pages_bulk/set_page_owner
 panic on irq disabled

On Fri,  9 Jul 2021 17:05:59 +0800 Yang Huan <link@...o.com> wrote:

> The problem is caused by set_page_owner alloc memory to save stack with
> GFP_KERNEL in local_riq disabled.
> So, we just can't assume that alloc flags should be same with new page,
> let's split it. But in most situation, same is ok, in alloc_pages_bulk,
> input GFP_ATOMIC when prep_new_pages

Please more fully describe the bug which is being fixed.  A link to the
sysbot report would be helpful.  I assume there was a stack backtrace
available?  Seeing the will help others to understand the bug.

And if you are able to identify the patch which introduced the bug, a
Fixes: tag would be helpful as well.

Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ