/fs/9p/ |
D | vfs_dir.c | 71 int over; in v9fs_dir_readdir() local 107 over = filldir(dirent, st.name, strlen(st.name), in v9fs_dir_readdir() 114 if (over) { in v9fs_dir_readdir()
|
/fs/freevxfs/ |
D | vxfs_lookup.c | 303 int over; in vxfs_readdir() local 311 over = filler(retp, de->d_name, de->d_namelen, in vxfs_readdir() 314 if (over) { in vxfs_readdir()
|
/fs/sysv/ |
D | dir.c | 95 int over; in sysv_readdir() local 102 over = filldir(dirent, name, strnlen(name,SYSV_NAMELEN), in sysv_readdir() 106 if (over) { in sysv_readdir()
|
D | Kconfig | 20 If you only intend to mount files from some other Unix over the
|
/fs/ubifs/ |
D | dir.c | 364 int err, over = 0; in ubifs_readdir() local 383 over = filldir(dirent, ".", 1, 0, dir->i_ino, DT_DIR); in ubifs_readdir() 384 if (over) in ubifs_readdir() 391 over = filldir(dirent, "..", 2, 1, in ubifs_readdir() 393 if (over) in ubifs_readdir() 435 over = filldir(dirent, dent->name, nm.len, file->f_pos, in ubifs_readdir() 438 if (over) in ubifs_readdir()
|
/fs/ |
D | file_table.c | 115 goto over; in get_empty_filp() 134 over: in get_empty_filp()
|
/fs/minix/ |
D | dir.c | 131 int over; in minix_readdir() local 135 over = filldir(dirent, name, l, in minix_readdir() 138 if (over) { in minix_readdir()
|
/fs/coda/ |
D | Kconfig | 8 disk. Coda has several advantages over NFS: support for
|
/fs/ufs/ |
D | dir.c | 484 int over; in ufs_readdir() local 496 over = filldir(dirent, de->d_name, in ufs_readdir() 500 if (over) { in ufs_readdir()
|
/fs/ext2/ |
D | dir.c | 330 int over; in ext2_readdir() local 337 over = filldir(dirent, de->name, de->name_len, in ext2_readdir() 340 if (over) { in ext2_readdir()
|
/fs/smbfs/ |
D | Kconfig | 8 files and printers over local networks. Saying Y here allows you to
|
/fs/cramfs/ |
D | README | 151 The main advantage of option 3 over 1, 2, is better compression. The 157 Another cost of 2 and 3 over 1 is making mkcramfs use a different
|
/fs/cifs/ |
D | CHANGES | 105 Fix NTLMv2 signing. NFS server mounted over cifs works (if cifs mount is 126 to match what documentation said. Support for very large reads, over 127K, 221 read responses when buffer size over 64K and also fix wrap of 222 max smb buffer size when CIFSMaxBufSize over 64K. Fix oops in 224 on socket is returned over and over). Add POSIX (advisory) byte range 253 over GigE is better. Do not hang thread on illegal byte range lock response 532 testcases (including fsx, and even large file copy) to fail over time. 812 over 16K to allow negotiation of up to Samba and Windows server default read 836 Includes support for deleting of open files and renaming over existing files (per POSIX
|
D | TODO | 89 y) Fix Samba 3 to handle reads/writes over 127K (and remove the cifs mount
|
D | README | 84 To permit users to mount and unmount over directories they own is possible 502 causes encryption of data sent over this mounted share but other
|
/fs/reiserfs/ |
D | Kconfig | 34 have forgotten that this was on, and then gone despondent over the
|
/fs/ncpfs/ |
D | Kconfig | 8 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
|
/fs/btrfs/ |
D | inode.c | 3142 int over = 0; in btrfs_real_readdir() local 3157 over = filldir(dirent, ".", 1, in btrfs_real_readdir() 3160 if (over) in btrfs_real_readdir() 3167 over = filldir(dirent, "..", 2, in btrfs_real_readdir() 3169 if (over) in btrfs_real_readdir() 3244 over = 0; in btrfs_real_readdir() 3247 over = filldir(dirent, name_ptr, name_len, in btrfs_real_readdir() 3255 if (over) in btrfs_real_readdir()
|
/fs/fuse/ |
D | dir.c | 995 int over; in parse_dirfile() local 1001 over = filldir(dstbuf, dirent->name, dirent->namelen, in parse_dirfile() 1003 if (over) in parse_dirfile()
|
/fs/affs/ |
D | Changes | 176 - Remove some more superfluous code left over from
|
/fs/ntfs/ |
D | ChangeLog | 204 lock protection over the buffer submission for i/o which allows the 220 - Fix sparse warnings that have crept in over time. 229 all over the system's ram. 1020 - Fix ntfs over loopback for compressed files by adding an 1022 - Miscellaneous cleanups all over the code and a fix or two in error 1607 export is necessary over the base kernel. 1667 without any error messages on a over 1GiB sized partition with >16k
|