lp:fuse

Created by Jelmer Vernooij and last modified
Get this branch:
bzr branch lp:fuse

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
VCS imports
Project:
FUSE
Status:
Development

Import details

Import Status: Failed

This branch is an import of the HEAD branch of the Git repository at git://fuse.git.sourceforge.net/gitroot/fuse/fuse.

The import has been suspended because it failed 5 or more times in succession.

Last successful import was .

Import started on galapagos and finished taking 1 minute — see the log
Import started on pear and finished taking 20 seconds — see the log
Import started on neumayer and finished taking 50 seconds — see the log
Import started on pear and finished taking 20 seconds — see the log

Recent revisions

1004. By Nikolaus Rath

libfuse: fix readdirplus doc

Returning entry in readdir does not result in bump of lookup count.

Returning entry in readdirplus DOES result in increase of lookup count by
1. You need to provide valid nodeid and valid stat structure (with at least
valid type) for each entry.

1003. By Miklos Szeredi <email address hidden>

fuse: synchronize fuse_kernel.h header with the linux kernel

Check for __KERNEL__ instead of __linux__ and use the standard int
types instead of the linux specific ones.

1002. By Miklos Szeredi <email address hidden>

Merge branch 'fuse_2_9_bugfix'

1001. By Miklos Szeredi <email address hidden>

remove real fuse_main() symbol

1000. By Miklos Szeredi <email address hidden>

clean fuse_chan_receive from versionscript

999. By Miklos Szeredi <email address hidden>

fix fi->fh format strings

998. By Miklos Szeredi <email address hidden>

Fix nodeid format strings

997. By Richard Jones

libfuse: don't force -D_FILE_OFFSET_BITS=64 in pkgconfig file.

FUSE_CFLAGS defines -D_FILE_OFFSET_BITS=64. There are three problems
with this:

(1) A larger program using libfuse might have modules compiled with
and without FUSE_CFLAGS, which, if LFS is not enabled and the platform
is 32 bit, would result in a fatal mix of 32 and 64 bit off_t. (This
would, of course, be a bug, but I think there is a better way to
detect this -- see below)

(2) Programs may need to be adjusted to support LFS. It's the
intention of the LFS standard that the _programmer_ enables LFS once
the program has been checked/adjusted.

(3) _FILE_OFFSET_BITS does not need to be defined at all on 64 bit
Linux. 64 bit off_t is the default there.

So I think it's better not to force -D_FILE_OFFSET_BITS=64, and
because of (3) I also think you shouldn't test for it.

However off_t must still be 64 bits, so how to enforce that? C1X will
define static assertions[1], and these can be used to check the size
of off_t.

Not all compilers support static assertions yet, although several do.
Therefore I have surrounded the static assertion with a conservative
check that the compiler is GCC >= 4.6. In the long run, this test can
be removed and you can just use 'static_assert'.

996. By Miklos Szeredi <email address hidden>

cuse: clean includes

995. By Richard Jones

libfuse: use O_CLOEXEC flag when opening /dev/fuse device

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.

Subscribers

No subscribers.