From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39234) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QEjDM-0003WD-VA for qemu-devel@nongnu.org; Tue, 26 Apr 2011 10:26:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QEjDL-00067I-U6 for qemu-devel@nongnu.org; Tue, 26 Apr 2011 10:26:08 -0400 Received: from e33.co.us.ibm.com ([32.97.110.151]:59409) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QEjDL-00066q-Ow for qemu-devel@nongnu.org; Tue, 26 Apr 2011 10:26:07 -0400 Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e33.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p3QEJ5D8013497 for ; Tue, 26 Apr 2011 08:19:05 -0600 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id p3QEPfJG138068 for ; Tue, 26 Apr 2011 08:25:42 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p3QEPEno021105 for ; Tue, 26 Apr 2011 08:25:14 -0600 Message-ID: <4DB6D5E3.8000100@linux.vnet.ibm.com> Date: Tue, 26 Apr 2011 07:25:39 -0700 From: Venkateswararao Jujjuri MIME-Version: 1.0 References: <1303820065-25262-1-git-send-email-sassan@sassan.me.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] Fix bug with virtio-9p fsync List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 04/26/2011 06:29 AM, Sassan Panahinejad wrote: > I will have to study XATTR and see how that will be affected. I don't > know whether it is possible for these functions to be called for > XATTR, and if it is then I do not know the proper way to handle it. > Perhaps we should have some function or macro to obtain the correct FD > from an fidp structure, which could be used for fsync, wstat, lock and > getlock? I agree; we need some level of macro for this. How about doing that as part of this patch itself? Thanks, JV