Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) client-ip=2620:137:e000::3:1;
From:   Jinjie Ruan <ruanjinjie@huawei.com>
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>
CC:     <ruanjinjie@huawei.com>
Subject: [PATCH v2 0/2] static_call: Fix two wild-memory-access bugs in static_call_del_module()
Date:   Fri, 15 Sep 2023 20:36:03 +0800
Message-ID: <20230915123605.3732345-1-ruanjinjie@huawei.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Content-Type:   text/plain; charset=US-ASCII
Precedence: bulk

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(-)

-- 
2.34.1