Is memory management ready for this? Can't deadlock like this happen? - displaying dialog window needs memory, so it waits until memory will be available - system decides to write some write-back cached data in order to free memory - 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 linux doesn't discard write-cached data and reminds them to replug the device --- and one day, randomly, they lose their data because of some memory management condition...
Mikulas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] Use of getblk differs between locations
- From: Pavel Machek <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Jamie Lokier <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Anton Altaparmakov <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- References:
- [PATCH] Use of getblk differs between locations
- From: Glauber de Oliveira Costa <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Anton Altaparmakov <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Glauber de Oliveira Costa <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Mikulas Patocka <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Anton Altaparmakov <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Mikulas Patocka <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Anton Altaparmakov <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Jeff Mahoney <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Mikulas Patocka <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Jeff Mahoney <[email protected]>
- [PATCH] Use of getblk differs between locations
- Prev by Date: Re: [PATCH 2.6.14-rc4] Maintainers one entry removed
- Next by Date: Re: 2.6.14-rc* / xinetd
- Previous by thread: Re: [PATCH] Use of getblk differs between locations
- Next by thread: Re: [PATCH] Use of getblk differs between locations
- Index(es):
 |