From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jaegeuk Kim Subject: Re: [PATCH 5/5] f2fs: Fix for parent inode information during server cache eviction Date: Mon, 10 Dec 2012 09:43:55 +0900 Message-ID: <1355100235.7291.52.camel@kjgkr> References: <1354946143-7730-1-git-send-email-linkinjeon@gmail.com> Reply-To: jaegeuk.kim@samsung.com Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-BhDVvD8dEXrubsJ+DeJh" Cc: linux-fsdevel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Namjae Jeon , Amit Sahrawat To: Namjae Jeon Return-path: Received: from mailout1.samsung.com ([203.254.224.24]:19573 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753018Ab2LJAoD (ORCPT ); Sun, 9 Dec 2012 19:44:03 -0500 Received: from epcpsbgm2.samsung.com (epcpsbgm2 [203.254.230.27]) by mailout1.samsung.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTP id <0MES0047OHZI4B90@mailout1.samsung.com> for linux-fsdevel@vger.kernel.org; Mon, 10 Dec 2012 09:44:00 +0900 (KST) Received: from [12.52.126.105] by mmp2.samsung.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPA id <0MES00IXRI1CVZ40@mmp2.samsung.com> for linux-fsdevel@vger.kernel.org; Mon, 10 Dec 2012 09:44:00 +0900 (KST) In-reply-to: <1354946143-7730-1-git-send-email-linkinjeon@gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: --=-BhDVvD8dEXrubsJ+DeJh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 2012-12-08 (=ED=86=A0), 14:55 +0900, Namjae Jeon: > From: Namjae Jeon >=20 > Test Case: > [NFS Client] > ls -lR . >=20 > [NFS Server] > while [ 1 ] > do > echo 3 > /proc/sys/vm/drop_caches > done >=20 > Error: "No such file or directory" >=20 > When cache is dropped at the server, it results in lookup failure at the > NFS client. Even though the file exists. Looking at the code to rebuild= =20 > the inode in case of cache eviction. It tries to initiate a lookup operat= ion > for ".." to get the parent information using the on-disk inode number. >=20 Could you describe why this patch resolves that bug? Before applying this, we need to figure out why that bug is occurred. IMO, from the viewpoint of functionality, ".." resolution should work too. Thanks, --=20 Jaegeuk Kim Samsung --=-BhDVvD8dEXrubsJ+DeJh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAABAgAGBQJQxTBLAAoJEEAUqH6CSFDSR+QP/1fK970o9i3IhG2JcIRcwyVv axMZxL6YYDiA/r51kSSIDUfwjfWlxztU7PWO5FdgVk7e2oHchuVTf/wRlke0M8wQ hAJJ6hVxt0ZtOONEZq3GJXkxlFLoe6VCLP2EZwuGcQCBSHJtzvvWbQhMra3wtsQR HGIicjfxZrvYqh+4Qzltgzd+pFnB98Q9qWPT0kHEARSagAC6r8EwIGaAcB8MnMoT JbOlK3h9+Rz4JH0AFupyZ6tCVon+nY7JDwA0BEEC0vT8LNPkIWoRfTi4GgRsZGon ZJcZALocMDCNZ/lTMRA/ucjgkalHa9dFEw+KW/CIRdFQlSkPSjZZQD9YKZUWrMgr 4dJfmfB5zsP7km4vDpYRXkFnfcjAp4Zy6BkP4hotw9dL6XNlz8hT4WpT94vWSyNd dyDh2zkCQfJAvzuD3FcPXn0fbN9bXQFJhB9w1vysmdZjqvNIcL14YyjcEZcWjqcl nFRr6fqrJ9pOapmw9orLR4nREnTStGt1ik71M8Il8Guno6FCMFQ6Bzmc+SNJmpxX AXixYA5oeadt/ghkn6nqUf0llzde6ncH1uD+q8e18QJXMjTFZzE/9mCg9NJNZKpm Js12fP78RjrpbGRwpgjMqToLEAiPZYhRrW5Wg4MuK5oD8SF1UHkZGExxAl2iImir s/ErMimJpy8z7UkDNdKT =ScAR -----END PGP SIGNATURE----- --=-BhDVvD8dEXrubsJ+DeJh--