From: Pavel Machek <pavel@ucw.cz>
To: Maxim <maximlevitsky@gmail.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
Alan Stern <stern@rowland.harvard.edu>,
gregkh@suse.de,
Kernel development list <linux-kernel@vger.kernel.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
davidz@redhat.com
Subject: Re: USB: on suspend to ram/disk all usb devices are replugged
Date: Sun, 1 Apr 2007 15:29:57 +0000 [thread overview]
Message-ID: <20070401152957.GA5068@ucw.cz> (raw)
In-Reply-To: <200703280129.10197.maximlevitsky@gmail.com>
Hi!
> > > In that case the user would see data corruption - just as if he mounts a piece
> > > of removable media in a USB card reader; yanks out the card and modifies it
> > > elsewhere, and then puts it back in.
> >
> > > I my opinion we can't really defend ourselves against such users... We can of
> > > course add checks in the file system drivers in the resume hooks to validate the
> > > super block and mount read-only if something change.
> >
> > The GNOME hath spoken?
> I also thought about that,
>
> I think that the best solution is still to hide connect/disconnect of usb devices from userspace (now it also causes corruption)
> But to refuse suspend with any usb mass storage device connected with mounted systems (and add a module param override
> for users who know what they are doing)
>
> What do you think ?
Agreed... and notice how easy is to do that in userspace :-))).
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-04-01 15:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 16:24 USB: on suspend to ram/disk all usb devices are replugged Maxim Levitsky
2007-03-27 17:15 ` Alan Stern
2007-03-27 17:54 ` Maxim
2007-03-27 18:05 ` Pete Zaitcev
2007-03-27 23:29 ` Maxim
2007-04-01 15:29 ` Pavel Machek [this message]
2007-04-01 17:42 ` David Zeuthen
2007-04-01 17:50 ` Pavel Machek
2007-04-01 18:01 ` David Zeuthen
2007-04-01 18:29 ` Pavel Machek
2007-04-01 18:26 ` Alan Stern
2007-04-01 18:34 ` Pavel Machek
2007-04-01 20:53 ` Rafael J. Wysocki
2007-04-02 2:54 ` Alan Stern
2007-04-02 20:37 ` Rafael J. Wysocki
2007-04-02 18:38 ` Chuck Ebbert
2007-04-02 19:36 ` Pavel Machek
2007-04-06 22:23 ` Nigel Cunningham
2007-04-02 14:49 ` Mark Lord
2007-04-02 18:28 ` Pavel Machek
2007-03-29 13:19 ` Mark Lord
2007-03-29 15:56 ` Alan Stern
2007-03-29 16:03 ` Mark Lord
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=20070401152957.GA5068@ucw.cz \
--to=pavel@ucw.cz \
--cc=davidz@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=maximlevitsky@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=zaitcev@redhat.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