mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Zhu Yanjun" <yanjun.zhu@linux.dev>,
	"Arnd Bergmann" <arnd@kernel.org>,
	"Leon Romanovsky" <leon@kernel.org>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Parav Pandit" <parav@nvidia.com>
Cc: "Mark Bloch" <mbloch@nvidia.com>,
	"Patrisious Haddad" <phaddad@nvidia.com>,
	"Moshe Shemesh" <moshe@nvidia.com>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/mlx5: fix linking with CONFIG_INFINIBAND_USER_ACCESS=n
Date: Fri, 11 Jul 2025 07:39:00 +0200	[thread overview]
Message-ID: <a707f0d2-6514-45e2-b123-70013a18c633@app.fastmail.com> (raw)
In-Reply-To: <94e50246-5182-4b73-be59-9ce8e9afcfbb@linux.dev>

On Thu, Jul 10, 2025, at 22:12, yanjun.zhu wrote:
> On 7/10/25 1:09 AM, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>> 
>> The check for rdma_uattrs_has_raw_cap() is not possible if user
>> access is disabled:
>> 
>> ERROR: modpost: "rdma_uattrs_has_raw_cap" [drivers/infiniband/hw/mlx5/mlx5_ib.ko] undefined!
>
> https://patchwork.kernel.org/project/linux-rdma/patch/72dee6b379bd709255a5d8e8010b576d50e47170.1751967071.git.leon@kernel.org/
>
> The issue you described seems to be the same as the one discussed in the 
> link above. Could you try applying the commit from that link and see if 
> the problem still persists?

That one looks fine, I'm sure it's sufficient without my patch.

    Arnd

      reply	other threads:[~2025-07-11  5:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10  8:09 Arnd Bergmann
2025-07-10 20:12 ` yanjun.zhu
2025-07-11  5:39   ` Arnd Bergmann [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=a707f0d2-6514-45e2-b123-70013a18c633@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=moshe@nvidia.com \
    --cc=parav@nvidia.com \
    --cc=phaddad@nvidia.com \
    --cc=yanjun.zhu@linux.dev \
    /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

all inboxes | Powered by JetHome®