linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [RFC PATCH 0/1] fpga: bridge improve protection against low-level control module unloading
@ 2024-02-06 10:56 Marco Pagani
  2024-02-06 10:56 ` [RFC PATCH 1/1] fpga: bridge: " Marco Pagani
  0 siblings, 1 reply; 2+ messages in thread
From: Marco Pagani @ 2024-02-06 10:56 UTC (permalink / raw)
  To: Moritz Fischer, Wu Hao, Xu Yilun, Tom Rix, Jonathan Corbet,
	Greg Kroah-Hartman, Alan Tull
  Cc: Marco Pagani, linux-kernel, linux-doc, linux-fpga

This RFC proposes a solution to keep protecting the fpga bridge against
the unloading of the low-level control modules while addressing the
limitations of the current implementation. Currently, the code assumes
that the low-level module registers a driver for the parent device that
is later used to take the module's refcount. This proposal removes this
limitation by adding a module owner field to the fpga_bridge struct that
can be set while registering the bridge.

The RFC patch is based on top of ("fpga: remove redundant checks for
bridge ops").

https://lore.kernel.org/linux-fpga/20240201155713.82898-1-marpagan@redhat.com/

Marco Pagani (1):
  fpga: bridge: improve protection against low-level control module
    unloading

 Documentation/driver-api/fpga/fpga-bridge.rst |  7 ++-
 drivers/fpga/fpga-bridge.c                    | 61 +++++++++++--------
 include/linux/fpga/fpga-bridge.h              | 10 ++-
 3 files changed, 47 insertions(+), 31 deletions(-)

-- 
2.43.0


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-02-06 10:57 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-02-06 10:56 [RFC PATCH 0/1] fpga: bridge improve protection against low-level control module unloading Marco Pagani
2024-02-06 10:56 ` [RFC PATCH 1/1] fpga: bridge: " Marco Pagani

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).