public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: l1138897701 <l1138897701@163.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	luoqing@kylinos.cn, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Re: Re: [PATCH] rdma: infiniband: Added __alloc_cq request value Return value non-zero value determination
Date: Wed, 23 Apr 2025 10:14:01 +0300	[thread overview]
Message-ID: <20250423071401.GG48485@unreal> (raw)
In-Reply-To: <2ac5915f.14aa.196604a64b6.Coremail.l1138897701@163.com>

On Wed, Apr 23, 2025 at 09:36:50AM +0800, l1138897701 wrote:
> 
> 
> 
> Thank you for your reply. 
> 
> 
> 
> 
> The ultimate goal of this patch is to confirm that if there are design flaws in the outbox driver, 
> 
> when compiling and installing it in the kernel, I personally consider that the kernel should issue a warning or report an error instead of directly panicking. 
> 
> 
> 
> 
> It is worth considering whether the kernel needs such a fault-proofing mechanism

Kernel code doesn't have such protections by design. Panic is a perfect
thing to teach users don't use out-of-tree broken modules.

Thanks

      parent reply	other threads:[~2025-04-23  7:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  9:33 [PATCH] rdma: infiniband: Added __alloc_cq request value Return value non-zero value determination luoqing
2025-04-07 16:25 ` Jason Gunthorpe
     [not found]   ` <7afc834e.5498.1965c20f9f0.Coremail.l1138897701@163.com>
2025-04-22 11:58     ` Leon Romanovsky
     [not found]       ` <2ac5915f.14aa.196604a64b6.Coremail.l1138897701@163.com>
2025-04-23  7:14         ` Leon Romanovsky [this message]

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=20250423071401.GG48485@unreal \
    --to=leon@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=l1138897701@163.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=luoqing@kylinos.cn \
    /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