public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Gushchin <roman.gushchin@linux.dev>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Parav Pandit <parav@mellanox.com>,
	Leon Romanovsky <leon@kernel.org>,
	Maher Sanalla <msanalla@nvidia.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RDMA/core: fix a NULL-pointer dereference in hw_stat_device_show()
Date: Tue, 25 Feb 2025 03:42:28 +0000	[thread overview]
Message-ID: <Z708JNt6-vPIuDBm@google.com> (raw)
In-Reply-To: <20250224233004.GD520155@nvidia.com>

On Mon, Feb 24, 2025 at 07:30:04PM -0400, Jason Gunthorpe wrote:
> On Mon, Feb 24, 2025 at 11:22:29PM +0000, Roman Gushchin wrote:
> > On Mon, Feb 24, 2025 at 03:16:46PM +0000, Parav Pandit wrote:
> > > 
> > > 
> > > > From: Jason Gunthorpe <jgg@nvidia.com>
> > > > Sent: Monday, February 24, 2025 8:41 PM
> > > > 
> > > > On Sat, Feb 22, 2025 at 06:34:21PM +0000, Parav Pandit wrote:
> > > > > ib_setup_device_attrs() should be merged to ib_setup_port_attrs() by
> > > > > renaming ib_setup_port_attrs() to be generic.  To utilize the group
> > > > > initialization ib_setup_port_attrs() needs to move up before
> > > > > device_add().
> > > > 
> > > > It needs more than that, somehow you have to maintain two groups list or
> > > > somehow remove the coredev->dev.groups assignment..
> > > > 
> > > I was thinking that if both device and port attr setup is done in
> > > same function, there is knowledge of is_full_dev that can be used
> > > for device level hw_stats setup. (similar to how its done at port
> > > level).
> > 
> > Given that there is a bit of discussion on how to move forward with this,
> > can we please merge the trivial fix in the mean time? (Just sent out v2 with
> > the fixed commit log).
> 
> Well, the issue now is the ABI break
> 
> If the right answer is to remove the sysfs entirely then it doesn't
> make sense to make it work in the stable and LTS kernels since that
> would create users. Currently it is fully broken so there are no
> users. Can we say that so certainly after it is fixed?

It's a good point.

Ok, then we need something like this (obviously, coded more nicely):

diff --git a/drivers/infiniband/core/device.c b/drivers/infiniband/core/device.c
index 0ded91f056f3..6998907fc779 100644
--- a/drivers/infiniband/core/device.c
+++ b/drivers/infiniband/core/device.c
@@ -956,6 +956,7 @@ static int add_one_compat_dev(struct ib_device *device,
        ret = device_add(&cdev->dev);
        if (ret)
                goto add_err;
+       device->groups[2] = NULL;
        ret = ib_setup_port_attrs(cdev);
        if (ret)
                goto port_err;

  reply	other threads:[~2025-02-25  3:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21  2:05 [PATCH] RDMA/core: fix a NULL-pointer dereference in hw_stat_device_show() Roman Gushchin
2025-02-21  3:14 ` Parav Pandit
2025-02-21  4:25   ` Roman Gushchin
2025-02-21  4:34     ` Parav Pandit
2025-02-21  4:49       ` Roman Gushchin
2025-02-21  8:03         ` Parav Pandit
2025-02-21 20:02           ` Roman Gushchin
2025-02-22 18:36             ` Parav Pandit
2025-02-22 20:50               ` Roman Gushchin
2025-02-21 17:43       ` Jason Gunthorpe
2025-02-22 18:34         ` Parav Pandit
2025-02-24 15:11           ` Jason Gunthorpe
2025-02-24 15:16             ` Parav Pandit
2025-02-24 23:22               ` Roman Gushchin
2025-02-24 23:30                 ` Jason Gunthorpe
2025-02-25  3:42                   ` Roman Gushchin [this message]
2025-02-25  4:34                     ` Parav Pandit
2025-02-26  3:41                       ` Roman Gushchin
2025-02-25 13:16                     ` Jason Gunthorpe
2025-02-26  3:37                       ` Roman Gushchin
2025-02-24 23:31               ` Jason Gunthorpe
2025-02-25 10:38                 ` Parav Pandit

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=Z708JNt6-vPIuDBm@google.com \
    --to=roman.gushchin@linux.dev \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=msanalla@nvidia.com \
    --cc=parav@mellanox.com \
    /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