diff options
author | NeilBrown <neilb@suse.de> | 2011-01-14 09:14:34 +1100 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2011-01-14 09:14:34 +1100 |
commit | 75d3da43cb74d2e5fb87816dbfecb839cd97c7f4 (patch) | |
tree | 27074aceb801ada315329591f32c938b36150ed9 /drivers/parport | |
parent | a6ff7e089c7fca813c956ccbed824087e89a3a49 (diff) |
md: Don't let implementation detail of curr_resync leak out through sysfs.
mddev->curr_resync has artificial values of '1' and '2' which are used
by the code which ensures only one resync is happening at a time on
any given device.
These values are internal and should never be exposed to user-space
(except when translated appropriately as in the 'pending' status in
/proc/mdstat).
Unfortunately they are as ->curr_resync is assigned to
->curr_resync_completed and that value is directly visible through
sysfs.
So change the assignments to ->curr_resync_completed to get the same
valued from elsewhere in a form that doesn't have the magic '1' or '2'
values.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/parport')
0 files changed, 0 insertions, 0 deletions