From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: weird bash autocomplete issue Date: Wed, 17 Dec 2008 18:58:09 -0500 Message-ID: <1229558289.27170.109.camel@think.oraclecorp.com> References: <545246795@web.de> <1229482522.7574.6.camel@nga> <120501c96025$3bfca7c0$0301a8c0@bui.materna.com> <1229523456.27170.4.camel@think.oraclecorp.com> Mime-Version: 1.0 Content-Type: text/plain Cc: Roland , linux-btrfs@vger.kernel.org To: Kay Sievers Return-path: In-Reply-To: List-ID: On Wed, 2008-12-17 at 23:15 +0100, Kay Sievers wrote: > > There are other filesystems doing the same, usually with 32bit int max > > instead of 64 bit int max, I guess that should work fine. > > > >> This should be fixed in git by now, so I can drop it if that really is > >> causing problems in bash. > > > > I'll come back if I can reproduce it with the same environment Roland is using. > > I see the same issue on x86 32 bit, with the additional __llseek() > between the getdents64(), and the last entry returned by readdir > ignored. > > If I change the returned LLONG_MAX to LONG_MAX in inode.c, it all > works fine, and the __llseek() disappears. Ok, thanks I'll work up a patch. -chris