From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f43.google.com ([209.85.192.43]:34138 "EHLO mail-qg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751287AbcEaQZZ (ORCPT ); Tue, 31 May 2016 12:25:25 -0400 Received: by mail-qg0-f43.google.com with SMTP id p34so24285852qgp.1 for ; Tue, 31 May 2016 09:25:25 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <87shwy8b38.fsf@thinkpad.rath.org> References: <87shwy8b38.fsf@thinkpad.rath.org> Date: Tue, 31 May 2016 18:25:24 +0200 Message-ID: Subject: Re: [fuse-devel] Changes in 4.7. From: Stef Bon To: "fuse-devel@lists.sourceforge.net" , "linux-fsdevel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi, I've been thinking about the non serialized readdirs. I do not understand. Readdirs have to be serialized, since the offset of the next readdir (belonging to the opendir) is known when the current readdir is finished: "start where current left". So it means probably that lookup (which in fact is only a read only operation) of a name in a directory can be done while a readdir is active on the same directory. Or something else? Two readdirs (or more) belonging to different opendirs active on the same directory? Stef