linux-kernel - Re: [PATCH 2/2] f2fs: don't skip recovering inode depend on i

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sat, 5 Nov 2016 00:02:14 -0700
From:   Jaegeuk Kim <jaegeuk@...nel.org>
To:     Chao Yu <chao@...nel.org>
Cc:     Chao Yu <yuchao0@...wei.com>,
        linux-f2fs-devel@...ts.sourceforge.net,
        linux-kernel@...r.kernel.org, liushuoran@...wei.com
Subject: Re: [PATCH 2/2] f2fs: don't skip recovering inode depend on i_times

On Sat, Nov 05, 2016 at 11:12:00AM +0800, Chao Yu wrote:
> On 2016/11/5 6:53, Jaegeuk Kim wrote:
> > On Fri, Nov 04, 2016 at 04:30:09PM +0800, Chao Yu wrote:
> >> On 2016/11/4 2:02, Jaegeuk Kim wrote:
> >>> On Fri, Nov 04, 2016 at 12:26:56AM +0800, Chao Yu wrote:
> >>>> From: Chao Yu <yuchao0@...wei.com>
> >>>>
> >>>> i_times of inode will be set with current system time which can be
> >>>> configured through 'date', so it's not safe to judge dnode block as
> >>>> garbage data depend on i_times.
> >>>
> >>> This is not to detect garbage data, but to skip redundant unchanged inode.
> >>
> >> Oops, seems 807b1e1c8e08 ("f2fs: do not recover from previous remained wrong
> >> dnodes") did't describe like that. But after reading the codes, it looks like
> >> the purpose of this change is to skip unchanged inode. So, commit log in
> >> original is incorrect, right?
> > 
> > Oh, right. This indicats both of purposes: stale data and detecting same inodes.
> 
> Alright.
> 
> > Let me just revert the original patch.
> 
> I can see that you have did reverting it in your git tree, but seems commit
> number is not right.
> 
> Could you please merge my updated v2 patch instead?

Oops, yeah. :)

> 
> Thanks,
> 
> > 
> > Thanks,
> > 
> >>
> >> Thanks,