Messages in this thread | | | Date | Thu, 13 Oct 2005 13:17:07 +0200 | From | Pavel Machek <> | Subject | Re: [PATCH] Use of getblk differs between locations |
| |
Hi!
> >>- the write of these data waits until the dialog window is > >>displayed, > >>user inserts the device and clicks 'OK' > > > >No, it's not, and deadlock is definitely possible. However, if we're > >at > >the point where memory is tight enough that it's an issue, the timer > >can > >expire and all the pending i/o is dropped just as it would be without > >the multipath code enabled. > > > >I'm not saying it's a solution ready for production, just a good > >starting point. > > But discarding data sometimes on USB unplug is even worse than > discarding data always --- users will by experimenting learn that
*Good starting point*.
Anyway, one solution would be to simply mlockall() on that replugitd and/or make dirty data hdd based (not ram based) and/or restricting dirty buffers to 10MB for removable media.
Pavel -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |