From: Oliver Neukum <oneukum@suse.com>
To: Shuah Khan <shuahkh@osg.samsung.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: valentina.manea.m@gmail.com, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: usbip: vhc_hcd: prevent module being removed while device are attached
Date: Wed, 04 Apr 2018 10:25:30 +0200 [thread overview]
Message-ID: <1522830330.30374.3.camel@suse.com> (raw)
Am Dienstag, den 03.04.2018, 09:56 -0600 schrieb Shuah Khan:
> This is a virtual device associated to a real physical device on a different
> system. My concern is that if the module gets removed accidentally then it
> could disrupt access to the remote device. The remote nature of the device
> with several players involved makes this scenario a bit more complex than
Hi,
you would doubtlessly lose connection to that device. Yet you would
also lose connections if you down your network. You need to be root
to unload a module. You could overwrite your root filesystems or flash
your firmware. In general we cannot and don't try to protect root
from such accidents.
Regards
Oliver
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-04-04 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 8:25 Oliver Neukum [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-18 16:43 usbip: vhc_hcd: prevent module being removed while device are attached Sasha Levin
2018-04-05 19:11 Greg KH
2018-04-05 17:09 Sasha Levin
2018-04-05 16:54 Shuah Khan
2018-04-05 16:42 Sasha Levin
2018-04-04 15:14 Shuah Khan
2018-04-03 15:56 Shuah Khan
2018-04-03 6:56 Greg Kroah-Hartman
2018-04-02 20:52 Shuah Khan
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=1522830330.30374.3.camel@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=valentina.manea.m@gmail.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).