On 2017/10/31 16:57, Sheng Yong wrote:
> Hi, Chao
>
> On 2017/10/31 15:20, Chao Yu wrote:
>> On 2017/10/31 9:38, Sheng Yong wrote:
>>> Fixing corrupted data depends on c.fix_on. If it's not set, we should not
>>> force fixing corrupted data. So if nat entries are found invalid when
>>> building
Hi, Chao
On 2017/10/31 15:20, Chao Yu wrote:
On 2017/10/31 9:38, Sheng Yong wrote:
Fixing corrupted data depends on c.fix_on. If it's not set, we should not
force fixing corrupted data. So if nat entries are found invalid when
building nat_area_bitmap, we should just set c.bug_on, and fix it
On 2017/10/31 9:38, Sheng Yong wrote:
> Fixing corrupted data depends on c.fix_on. If it's not set, we should not
> force fixing corrupted data. So if nat entries are found invalid when
> building nat_area_bitmap, we should just set c.bug_on, and fix it later.
It looks comments and code change
Fixing corrupted data depends on c.fix_on. If it's not set, we should not
force fixing corrupted data. So if nat entries are found invalid when
building nat_area_bitmap, we should just set c.bug_on, and fix it later.
Signed-off-by: Sheng Yong
---
fsck/mount.c | 21