Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33;
Message-ID: <57ce70f7-2b5d-384d-d14e-b9e96e3ca636@huawei.com>
Date:   Tue, 26 Sep 2023 15:34:07 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.0
Subject: Re: [PATCH v2 0/2] static_call: Fix two wild-memory-access bugs in
 static_call_del_module()
Content-Language: en-US
To:     <peterz@infradead.org>, <tglx@linutronix.de>,
        <rostedt@goodmis.org>, <mingo@kernel.org>, <jpoimboe@kernel.org>,
        <christophe.leroy@csgroup.eu>, <linux-kernel@vger.kernel.org>
References: <20230915123605.3732345-1-ruanjinjie@huawei.com>
From:   Ruan Jinjie <ruanjinjie@huawei.com>
In-Reply-To: <20230915123605.3732345-1-ruanjinjie@huawei.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

Ping.

On 2023/9/15 20:36, Jinjie Ruan wrote:
> In __static_call_init(), any one of the kzalloc fails will cause
> wild-memory-access when traverse the site and subsequent sites in
> static_call_del_module().
> 
> Changes in v2:
> - Add a new patch which fix a a similar problem.
> - Update the commit message and simplify error stack for the first.
> 
> Jinjie Ruan (2):
>   static_call: Fix a wild-memory-access bug in static_call_del_module()
>   static_call: Fix a wild-memory-access bug when
>     static_call_key_sites(key) is true
> 
>  kernel/static_call_inline.c | 11 ++++++++---
>  1 file changed, 8 insertions(+), 3 deletions(-)
>