From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marco Pagani <marpagan@redhat.com>
Cc: Moritz Fischer <mdf@kernel.org>, Wu Hao <hao.wu@intel.com>,
Xu Yilun <yilun.xu@intel.com>, Tom Rix <trix@redhat.com>,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org
Subject: Re: [RFC PATCH v3 2/2] fpga: set owner of fpga_manager_ops for existing low-level modules
Date: Tue, 19 Dec 2023 16:10:02 +0100 [thread overview]
Message-ID: <2023121924-extent-defender-fb06@gregkh> (raw)
In-Reply-To: <9296941c-a3c8-4d55-9e52-f1277f1c3fc7@redhat.com>
On Tue, Dec 19, 2023 at 03:54:25PM +0100, Marco Pagani wrote:
>
>
> On 2023-12-18 21:33, Greg Kroah-Hartman wrote:
> > On Mon, Dec 18, 2023 at 09:28:09PM +0100, Marco Pagani wrote:
> >> This patch tentatively set the owner field of fpga_manager_ops to
> >> THIS_MODULE for existing fpga manager low-level control modules.
> >>
> >> Signed-off-by: Marco Pagani <marpagan@redhat.com>
> >> ---
> >> drivers/fpga/altera-cvp.c | 1 +
> >> drivers/fpga/altera-pr-ip-core.c | 1 +
> >> drivers/fpga/altera-ps-spi.c | 1 +
> >> drivers/fpga/dfl-fme-mgr.c | 1 +
> >> drivers/fpga/ice40-spi.c | 1 +
> >> drivers/fpga/lattice-sysconfig.c | 1 +
> >> drivers/fpga/machxo2-spi.c | 1 +
> >> drivers/fpga/microchip-spi.c | 1 +
> >> drivers/fpga/socfpga-a10.c | 1 +
> >> drivers/fpga/socfpga.c | 1 +
> >> drivers/fpga/stratix10-soc.c | 1 +
> >> drivers/fpga/tests/fpga-mgr-test.c | 1 +
> >> drivers/fpga/tests/fpga-region-test.c | 1 +
> >> drivers/fpga/ts73xx-fpga.c | 1 +
> >> drivers/fpga/versal-fpga.c | 1 +
> >> drivers/fpga/xilinx-spi.c | 1 +
> >> drivers/fpga/zynq-fpga.c | 1 +
> >> drivers/fpga/zynqmp-fpga.c | 1 +
> >> 18 files changed, 18 insertions(+)
> >>
> >> diff --git a/drivers/fpga/altera-cvp.c b/drivers/fpga/altera-cvp.c
> >> index 4ffb9da537d8..aeb913547dd8 100644
> >> --- a/drivers/fpga/altera-cvp.c
> >> +++ b/drivers/fpga/altera-cvp.c
> >> @@ -520,6 +520,7 @@ static const struct fpga_manager_ops altera_cvp_ops = {
> >> .write_init = altera_cvp_write_init,
> >> .write = altera_cvp_write,
> >> .write_complete = altera_cvp_write_complete,
> >> + .owner = THIS_MODULE,
> >
> > Note, this is not how to do this, force the compiler to set this for you
> > automatically, otherwise everyone will always forget to do it. Look at
> > how functions like usb_register_driver() works.
> >
> > Also, are you _sure_ that you need a module owner in this structure? I
> > still don't know why...
> >
>
> Do you mean moving the module owner field to the manager context and setting
> it during registration with a helper macro?
I mean set it during registration with a helper macro.
> Something like:
>
> struct fpga_manager {
> ...
> struct module *owner;
> };
>
> #define fpga_mgr_register(parent, ...) \
> __fpga_mgr_register(parent,..., THIS_MODULE)
>
> struct fpga_manager *
> __fpga_mgr_register(struct device *parent, ..., struct module *owner)
> {
> ...
> mgr->owner = owner;
> }
Yes.
But again, is a module owner even needed? I don't think you all have
proven that yet...
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-19 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 20:28 [RFC PATCH v3 0/2] fpga: improve protection against low-level control module unloading Marco Pagani
2023-12-18 20:28 ` [RFC PATCH v3 1/2] fpga: add an owner field and use it to take the low-level module's refcount Marco Pagani
2023-12-25 6:58 ` Xu Yilun
2024-01-03 15:02 ` Marco Pagani
2023-12-18 20:28 ` [RFC PATCH v3 2/2] fpga: set owner of fpga_manager_ops for existing low-level modules Marco Pagani
2023-12-18 20:33 ` Greg Kroah-Hartman
2023-12-19 14:54 ` Marco Pagani
2023-12-19 15:10 ` Greg Kroah-Hartman [this message]
2023-12-19 17:17 ` Marco Pagani
2023-12-19 18:11 ` Greg Kroah-Hartman
2023-12-20 22:24 ` Marco Pagani
2023-12-21 8:22 ` Greg Kroah-Hartman
2023-12-22 20:52 ` Marco Pagani
2023-12-21 9:26 ` Xu Yilun
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=2023121924-extent-defender-fb06@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marpagan@redhat.com \
--cc=mdf@kernel.org \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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;
as well as URLs for NNTP newsgroup(s).