linux-kernel - Re: [PATCH v2 2/2] kexec: Fix potential out of bounds in crash_exclude_mem

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: <5a791f12-9c88-4dca-ac9d-dee4ba36bf9c@easystack.cn>
Date: Fri, 22 Dec 2023 19:08:09 +0800
From: fuqiang wang <fuqiang.wang@...ystack.cn>
To: Baoquan He <bhe@...hat.com>
Cc: Vivek Goyal <vgoyal@...hat.com>, Dave Young <dyoung@...hat.com>,
 Yuntao Wang <ytcoode@...il.com>, kexec@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] kexec: Fix potential out of bounds in
 crash_exclude_mem_range()


在 2023/12/21 19:42, Baoquan He 写道:
> You may need rebase your work on next/master branch to avoid conflict.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>
> In the current, below commit exists, then code change in this patch may
> not be needed.
> 86d80cbb61ca crash_core: fix and simplify the logic of crash_exclude_mem_range()
>

Yes, Baoquan, you are right. It's my mistake. Thank you very much ~