Revision ca64cae96037de16e4af92678814f5d4bf0c1c65 authored by NeilBrown on 21 November 2012, 05:33:40 UTC, committed by NeilBrown on 21 November 2012, 22:14:13 UTC
commit 9e44476851e91c86c98eb92b9bc27fb801f89072 MD: raid5 avoid unnecessary zero page for trim change raid5 to clear R5_Discard when the complete request is handled rather than when submitting the per-device discard request. However it did not clear R5_Discard for the parity device. This means that if the stripe_head was reused before it expired from the cache, the setting would be wrong and a hang would result. Also if the R5_Uptodate bit happens to be set, R5_Discard again won't be cleared. But R5_Uptodate really should be clear at this point. So make sure R5_Discard is cleared in all cases, and clear R5_Uptodate when a 'discard' completes. Signed-off-by: NeilBrown <neilb@suse.de>
1 parent ef5b7c6
File | Mode | Size |
---|---|---|
Kconfig | -rw-r--r-- | 1.1 KB |
Makefile | -rw-r--r-- | 125 bytes |
patchlevel | -rw-r--r-- | 6 bytes |
wanmain.c | -rw-r--r-- | 19.0 KB |
wanproc.c | -rw-r--r-- | 9.1 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...