From: Chris Mason <chris.mason@oracle.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Roland <devzero@web.de>, linux-btrfs@vger.kernel.org
Subject: Re: weird bash autocomplete issue
Date: Wed, 17 Dec 2008 18:58:09 -0500 [thread overview]
Message-ID: <1229558289.27170.109.camel@think.oraclecorp.com> (raw)
In-Reply-To: <ac3eb2510812171415u1b2fc166r2ba10999542808fe@mail.gmail.com>
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
next prev parent reply other threads:[~2008-12-17 23:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 20:46 weird bash autocomplete issue devzero
2008-12-16 21:41 ` Kay Sievers
2008-12-17 2:55 ` Kay Sievers
2008-12-17 8:45 ` Roland
2008-12-17 13:59 ` Kay Sievers
2008-12-17 14:17 ` Chris Mason
2008-12-17 14:46 ` Kay Sievers
2008-12-17 22:15 ` Kay Sievers
2008-12-17 23:58 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-19 9:15 devzero
2008-12-19 0:59 devzero
2008-12-19 1:27 ` Kay Sievers
2008-12-17 14:40 devzero
2008-12-16 19:37 Roland
2008-12-16 19:47 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1229558289.27170.109.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=devzero@web.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox