driverdev-devel.linuxdriverproject.org archive mirror
 help / color / mirror / Atom feed
From: Christian Gromm <christian.gromm@microchip.com>
To: <gregkh@linuxfoundation.org>
Cc: Christian Gromm <christian.gromm@microchip.com>,
	driverdev-devel@linuxdriverproject.org
Subject: [PATCH 0/2] staging: most: prevent module removal if configfs directory is populated
Date: Fri, 8 Nov 2019 17:21:06 +0100	[thread overview]
Message-ID: <1573230068-27658-1-git-send-email-christian.gromm@microchip.com> (raw)

Currently the core module does not hold any reference to component modules.
Hence, a component could be unloaded from the system anytime. Even if the
configuration interface is still being populated with configfs
items/groups.
User space then has no chance to fix the usage count by calling rmdir on
such a config item/group, as the respective directory does not exist
anymore. In this situation the core module cannot be unloaded anymore.
This patch set fixes this issue by holding a reference as long as the
configfs items exist.

Christian Gromm (2):
  staging: most: configfs: move configfs subsystems to container struct
  staging: most: block module removal while having active configfs items

 drivers/staging/most/cdev/cdev.c   |   1 +
 drivers/staging/most/configfs.c    | 118 +++++++++++++++++++++++++------------
 drivers/staging/most/core.h        |   1 +
 drivers/staging/most/net/net.c     |   1 +
 drivers/staging/most/sound/sound.c |   1 +
 drivers/staging/most/video/video.c |   1 +
 6 files changed, 85 insertions(+), 38 deletions(-)

-- 
2.7.4

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

             reply	other threads:[~2019-11-08 16:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 16:21 Christian Gromm [this message]
2019-11-08 16:21 ` [PATCH 1/2] staging: most: configfs: move configfs subsystems to container struct Christian Gromm
2019-11-08 16:21 ` [PATCH 2/2] staging: most: block module removal while having active configfs items Christian Gromm

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=1573230068-27658-1-git-send-email-christian.gromm@microchip.com \
    --to=christian.gromm@microchip.com \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.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).