linux-kernel - RE: [PATCH 1/2] f2fs: reorganize __f2fs_add

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 for Android: free password hash cracker in your pocket

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

Message-id: <00e401d0c91f$f301b950$d9052bf0$@samsung.com>
Date:	Tue, 28 Jul 2015 18:26:25 +0800
From:	Chao Yu <chao2.yu@...sung.com>
To:	'Jaegeuk Kim' <jaegeuk@...nel.org>
Cc:	linux-f2fs-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: RE: [PATCH 1/2] f2fs: reorganize __f2fs_add_link

Hi Jaegeuk,

> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@...nel.org]
> Sent: Saturday, July 25, 2015 12:11 AM
> To: Chao Yu
> Cc: linux-f2fs-devel@...ts.sourceforge.net; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH 1/2] f2fs: reorganize __f2fs_add_link
> 
> Hi Chao,
> 
> BTW, isn't there any problem on update_inode/mark_inode_dirty stuffs?

Any problem here?

> And, is there a hole to write uncompleted node pages unnecessarily?
> 

Yes, the hole can be filled.

> > Let me think about this for a while.
> > I think two patches are clean-ups with a little bit big changes.
> > Currently, we've touched many parts including extent_cache, so I need to focus
> > on stabilizing them first.
> > After then, I'd like to dig two clean-up patches. Ok?

It's OK. :)

Thanks,

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/