From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Jason Gunthorpe <jgg@ziepe.ca>, Bernard Metzler <BMT@zurich.ibm.com>
Cc: "leon@kernel.org" <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH 0/5] Fix potential issues for siw
Date: Fri, 28 Jul 2023 10:29:16 +0800 [thread overview]
Message-ID: <684f6b40-8d02-a273-2192-9c2499bd555a@linux.dev> (raw)
In-Reply-To: <35286616-a53d-7aa5-b3b0-09ae44edf510@linux.dev>
On 7/28/23 09:16, Guoqing Jiang wrote:
>
>
> On 7/28/23 01:29, Jason Gunthorpe wrote:
>> On Thu, Jul 27, 2023 at 05:17:40PM +0000, Bernard Metzler wrote:
>>>
>>>> -----Original Message-----
>>>> From: Guoqing Jiang <guoqing.jiang@linux.dev>
>>>> Sent: Thursday, 27 July 2023 16:04
>>>> To: Bernard Metzler <BMT@zurich.ibm.com>; jgg@ziepe.ca;
>>>> leon@kernel.org
>>>> Cc: linux-rdma@vger.kernel.org
>>>> Subject: [EXTERNAL] [PATCH 0/5] Fix potential issues for siw
>>>>
>>>> Hi,
>>>>
>>>> Several issues appeared if we rmmod siw module after failed to insert
>>>> the module (with manual change like below).
>>>>
>>>> --- a/drivers/infiniband/sw/siw/siw_main.c
>>>> +++ b/drivers/infiniband/sw/siw/siw_main.c
>>>> @@ -577,6 +577,7 @@ static __init int siw_init_module(void)
>>>> if (rv)
>>>> goto out_error;
>>>>
>>>> + goto out_error;
>>>> rdma_link_register(&siw_link_ops);
>>>>
>>>> Basically, these issues are double free, use before initalization or
>>>> null pointer dereference. For more details, pls review the individual
>>>> patch.
>>>>
>>>> Thanks,
>>>> Guoqing
>>> Hi Guoqing,
>>>
>>> very good catch, thank you. I was under the wrong assumption a
>>> module is not loaded if the init_module() returns a value.
>> I think that is actually true, isn't it? I'm confused?
>
> Yes, you are right. Since rv is still 0, so the module appears in the
> kernel. Not sure if some tool could inject err like this. Feel free to
> ignore this.
The below trace happened if I run a stress test with load siw module and
unload siw in a loop, which should be fixed by patch 5, so I think we
need to apply it, what do you think?
[ 414.537961] BUG: spinlock bad magic on CPU#0, modprobe/3722
[ 414.537965] lock: 0xffff9d847bc380e8, .magic: 00000000, .owner:
<none>/-1, .owner_cpu: 0
[ 414.537969] CPU: 0 PID: 3722 Comm: modprobe Tainted: G OE
6.5.0-rc3+ #16
[ 414.537971] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
rel-1.16.0-0-gd239552c-rebuilt.opensuse.org 04/01/2014
[ 414.537973] Call Trace:
[ 414.537973] <TASK>
[ 414.537975] dump_stack_lvl+0x77/0xd0
[ 414.537979] dump_stack+0x10/0x20
[ 414.537981] spin_bug+0xa5/0xd0
[ 414.537984] do_raw_spin_lock+0x90/0xd0
[ 414.537985] _raw_spin_lock_irqsave+0x56/0x80
[ 414.537988] ? __wake_up_common_lock+0x63/0xd0
[ 414.537990] __wake_up_common_lock+0x63/0xd0
[ 414.537992] __wake_up+0x13/0x30
[ 414.537994] siw_stop_tx_thread+0x49/0x70 [siw]
[ 414.538000] siw_exit_module+0x30/0x620 [siw]
[ 414.538006] __do_sys_delete_module.constprop.0+0x18f/0x300
[ 414.538008] ? syscall_enter_from_user_mode+0x21/0x70
[ 414.538010] ? __this_cpu_preempt_check+0x13/0x20
[ 414.538012] ? lockdep_hardirqs_on+0x86/0x120
[ 414.538014] __x64_sys_delete_module+0x12/0x20
[ 414.538016] do_syscall_64+0x5c/0x90
[ 414.538019] ? do_syscall_64+0x69/0x90
[ 414.538020] ? __this_cpu_preempt_check+0x13/0x20
[ 414.538022] ? lockdep_hardirqs_on+0x86/0x120
[ 414.538024] ? syscall_exit_to_user_mode+0x37/0x50
[ 414.538025] ? do_syscall_64+0x69/0x90
[ 414.538026] ? syscall_exit_to_user_mode+0x37/0x50
[ 414.538027] ? do_syscall_64+0x69/0x90
[ 414.538029] ? syscall_exit_to_user_mode+0x37/0x50
[ 414.538030] ? do_syscall_64+0x69/0x90
[ 414.538032] ? irqentry_exit_to_user_mode+0x25/0x30
[ 414.538033] ? irqentry_exit+0x77/0xb0
[ 414.538034] ? exc_page_fault+0xae/0x240
[ 414.538036] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 414.538038] RIP: 0033:0x7f177eb26c9b
Thanks,
Guoqing
next prev parent reply other threads:[~2023-07-28 2:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 14:03 [PATCH 0/5] Fix potential issues for siw Guoqing Jiang
2023-07-27 14:03 ` [PATCH 1/5] RDMA/siw: Set siw_cm_wq to NULL after it is destroyed Guoqing Jiang
2023-07-27 14:03 ` [PATCH 2/5] RDMA/siw: Ensure siw_destroy_cpulist can be called more than once Guoqing Jiang
2023-07-27 14:03 ` [PATCH 3/5] RDMA/siw: Initialize siw_link_ops.list Guoqing Jiang
2023-07-27 14:03 ` [PATCH 4/5] RDMA/siw: Set siw_crypto_shash to NULL after it is freed Guoqing Jiang
2023-07-27 14:03 ` [PATCH 5/5] RDMA/siw: Don't call wake_up unconditionally in siw_stop_tx_thread Guoqing Jiang
2023-07-27 17:17 ` [PATCH 0/5] Fix potential issues for siw Bernard Metzler
2023-07-27 17:29 ` Jason Gunthorpe
2023-07-27 18:15 ` Bart Van Assche
2023-07-28 1:16 ` Guoqing Jiang
2023-07-28 2:29 ` Guoqing Jiang [this message]
2023-07-28 11:10 ` Bernard Metzler
2023-07-28 9:36 ` Bernard Metzler
2023-08-09 19:04 ` Jason Gunthorpe
2023-08-10 1:14 ` Guoqing Jiang
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=684f6b40-8d02-a273-2192-9c2499bd555a@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=BMT@zurich.ibm.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).