All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Theodore Tso <tytso@mit.edu>, Ingo Molnar <mingo@elte.hu>,
	Jan Kara <jack@suse.cz>, Arjan van de Ven <arjan@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Top 10 bugs/warnings for the week of March 23rd, 2008
Date: Mon, 26 May 2008 20:49:14 -0700	[thread overview]
Message-ID: <20080527034914.GA20295@kroah.com> (raw)
In-Reply-To: <20080526170147.GB9893@mit.edu>

On Mon, May 26, 2008 at 01:01:48PM -0400, Theodore Tso wrote:
> On Mon, May 26, 2008 at 06:48:58PM +0200, Ingo Molnar wrote:
> > 
> > What if the USB stick was pulled mistakenly, the user notices her 
> > mistake later on and plugs the USB stick back in and expects all the 
> > data to not be corrupted?
> 
> If the USB stack folks would like to work on how to recognize that
> it's the same USB stick that had been previously pulled, so that it
> gets the same block device, and we can decide for how long we should
> keep dirty buffers around associated with a pulled USB stick, we can
> certainly have that conversation.  :-)

We do that already on suspend/resume, so it should not be hard to move
that to a disconnect/connect model as well, it's the same code path :)

Bring it up on the linux-usb list if you are interested in persuing
this.

In the meanwhile, getting rid of the warning would be a good idea.

thanks,

greg k-h

  parent reply	other threads:[~2008-05-27  3:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 16:19 Top 10 bugs/warnings for the week of March 23rd, 2008 Arjan van de Ven
2008-05-23 16:23 ` Top 10 bugs/warnings for the week of May " Arjan van de Ven
2008-05-23 16:42 ` Top 10 bugs/warnings for the week of March " Linus Torvalds
2008-05-23 17:35   ` Arjan van de Ven
2008-05-23 19:31 ` Alan Cox
2008-05-24  0:15 ` Chris Wright
2008-05-24  5:07   ` Arjan van de Ven
2008-05-26  9:36     ` Ingo Molnar
2008-05-24  5:32 ` Greg KH
2008-05-24 22:23 ` Jan Kara
2008-05-24 22:30   ` Arjan van de Ven
2008-05-24 22:45     ` Theodore Tso
2008-05-25 11:58       ` Stefan Richter
2008-05-26  9:39       ` Ingo Molnar
2008-05-26 10:16         ` Theodore Tso
2008-05-26 10:48           ` Ingo Molnar
2008-05-26 16:20             ` Jan Kara
2008-05-26 16:48               ` Ingo Molnar
2008-05-26 17:01                 ` Theodore Tso
2008-05-26 17:09                   ` Oliver Neukum
2008-05-26 17:28                     ` Bart Van Assche
2008-05-26 17:38                       ` Jan Kara
2008-05-26 17:50                         ` Theodore Tso
2008-05-26 18:23                           ` Ingo Molnar
2008-05-27  6:12                       ` Oliver Neukum
2008-05-27 11:41                     ` Pavel Machek
2008-05-27  3:49                   ` Greg KH [this message]
2008-05-27 11:40             ` Pavel Machek
2008-05-26 14:52           ` Stefan Richter

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=20080527034914.GA20295@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.