Received: by 10.213.65.68 with SMTP id h4csp472254imn; Wed, 4 Apr 2018 01:35:10 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+JeILDaO+Ens4GIHNYmdB4yJ122MmvUvwpJ/McCLkfN0OQskVdcl4ZQQEPjpFnmmP4pF0I X-Received: by 2002:a17:902:362:: with SMTP id 89-v6mr17443508pld.270.1522830910930; Wed, 04 Apr 2018 01:35:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522830910; cv=none; d=google.com; s=arc-20160816; b=tV03d+hdrsbSD1qcQ47ddFc9rntBqeHoam+dhko5mL9Bpqvzn3MnNYAvKJi2/34RQN LYYP9HcSDnYTq1JzidGF502gpT+1Vfh+xkC+KeY7RcWgCr7dl/0DJ47zku4YlwfddHrx YXUJb4UUC0yqPTCnKi/GKdzHctYCSJGKks4errUR+OKgV4vA17Z6oTKSlXEhnpIqv4Ds 8nfAZbLILdY2/mXX+a7gU876w0jXx7t4F3FaYg2xglBTpVnZmSl5J2Wf2EvEpfYAz33I xwJ8sl7w8bldF+DigPHzTALXY/2ZQ9qQOWtj7zBAXGbZpXLNLs3g0QoyY4RXcBF5g9Af GwAg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=tu/5a2I3SgdbZdk0jB+aSSkRwWX7c5uA5YIdib1RpTc=; b=kvUkTlQYsTAUcGnFIrVsmqCltSb2aLPPXDaC9hDfReMo8Rwrls/04n5q7ph85/RhhA AVhOY8ouwwLAGir4pAI8AbvJouazVjphIbjspuHMtJJDe/Iy0bUEYP/rE/56XlRXWCYZ hTnuOxUnDjfqEqZ+B1x/ARrgCbvqNgmdW13VciyJiIvYgIl6veSFVTt6B9zSHsnH5bdC yqxfM25pVLARsnku4LJ4YZuOlPT0UUHIz1PQGf4cGyj1Y9bYjKfDi4jpZptv13aukjxn ojq2JQkescwoifgIHb+6G2uR6FpSaeO0Vn6vCZzqBCuSsoXF5OdqOHPw/87td/v1NBh/ p+wg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x5si3349289pgb.365.2018.04.04.01.34.57; Wed, 04 Apr 2018 01:35:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751591AbeDDIbi (ORCPT + 99 others); Wed, 4 Apr 2018 04:31:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:60465 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751280AbeDDIbh (ORCPT ); Wed, 4 Apr 2018 04:31:37 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id BB80EAFF8; Wed, 4 Apr 2018 08:31:35 +0000 (UTC) Message-ID: <1522830330.30374.3.camel@suse.com> Subject: Re: [PATCH] usbip: vhc_hcd: prevent module being removed while device are attached From: Oliver Neukum To: Shuah Khan , Greg KH Cc: valentina.manea.m@gmail.com, shuah@kernel.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Date: Wed, 04 Apr 2018 10:25:30 +0200 In-Reply-To: <6022b8f0-821a-2d1c-8032-4b298835feae@osg.samsung.com> References: <20180402205232.21659-1-shuahkh@osg.samsung.com> <20180403065618.GA1093@kroah.com> <6022b8f0-821a-2d1c-8032-4b298835feae@osg.samsung.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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