From: Jason Gunthorpe <jgg@ziepe.ca>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, Leon Romanovsky <leon@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] IB/core: Fix two kernel warnings triggered by rxe registration
Date: Wed, 3 Jan 2018 20:04:14 -0700 [thread overview]
Message-ID: <20180104030414.GA663@ziepe.ca> (raw)
In-Reply-To: <20180103212818.10351-1-bart.vanassche@wdc.com>
On Wed, Jan 03, 2018 at 01:28:18PM -0800, Bart Van Assche wrote:
> Avoid that the following two warnings are reported when registering an
> rxe device:
>
> WARNING: CPU: 2 PID: 1005 at drivers/infiniband/core/device.c:449 ib_register_device+0x591/0x640 [ib_core]
> CPU: 2 PID: 1005 Comm: run_tests Not tainted 4.15.0-rc4-dbg+ #2
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.0.0-prebuilt.qemu-project.org 04/01/2014
> RIP: 0010:ib_register_device+0x591/0x640 [ib_core]
> Call Trace:
> rxe_register_device+0x3c6/0x470 [rdma_rxe]
> rxe_add+0x543/0x5e0 [rdma_rxe]
> rxe_net_add+0x37/0xb0 [rdma_rxe]
> rxe_param_set_add+0x5a/0x120 [rdma_rxe]
> param_attr_store+0x5e/0xc0
> module_attr_store+0x19/0x30
> sysfs_kf_write+0x3d/0x50
> kernfs_fop_write+0x116/0x1a0
> __vfs_write+0x23/0x120
> vfs_write+0xbe/0x1b0
> SyS_write+0x44/0xa0
> entry_SYSCALL_64_fastpath+0x23/0x9a
>
> WARNING: CPU: 2 PID: 1005 at drivers/infiniband/core/sysfs.c:1279 ib_device_register_sysfs+0x11d/0x160 [ib_core]
> CPU: 2 PID: 1005 Comm: run_tests Tainted: G W 4.15.0-rc4-dbg+ #2
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.0.0-prebuilt.qemu-project.org 04/01/2014
> RIP: 0010:ib_device_register_sysfs+0x11d/0x160 [ib_core]
> Call Trace:
> ib_register_device+0x3f7/0x640 [ib_core]
> rxe_register_device+0x3c6/0x470 [rdma_rxe]
> rxe_add+0x543/0x5e0 [rdma_rxe]
> rxe_net_add+0x37/0xb0 [rdma_rxe]
> rxe_param_set_add+0x5a/0x120 [rdma_rxe]
> param_attr_store+0x5e/0xc0
> module_attr_store+0x19/0x30
> sysfs_kf_write+0x3d/0x50
> kernfs_fop_write+0x116/0x1a0
> __vfs_write+0x23/0x120
> vfs_write+0xbe/0x1b0
> SyS_write+0x44/0xa0
> entry_SYSCALL_64_fastpath+0x23/0x9a
>
> Fixes: 99db9494035f ("IB/core: Remove ib_device.dma_device")
> Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>
> Cc: Leon Romanovsky <leon@kernel.org>
> Cc: stable@vger.kernel.org # v4.11
Applied to for-next thanks
Jason
prev parent reply other threads:[~2018-01-04 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 21:28 [PATCH v2] IB/core: Fix two kernel warnings triggered by rxe registration Bart Van Assche
2018-01-04 3:04 ` Jason Gunthorpe [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=20180104030414.GA663@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bart.vanassche@wdc.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=stable@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).