Home
last modified time | relevance | path

Searched refs:to (Results 1 – 25 of 227) sorted by relevance

12345678910

/fs/xfs/libxfs/
Dxfs_sb.c548 struct xfs_sb *to, in __xfs_sb_from_disk() argument
552 to->sb_magicnum = be32_to_cpu(from->sb_magicnum); in __xfs_sb_from_disk()
553 to->sb_blocksize = be32_to_cpu(from->sb_blocksize); in __xfs_sb_from_disk()
554 to->sb_dblocks = be64_to_cpu(from->sb_dblocks); in __xfs_sb_from_disk()
555 to->sb_rblocks = be64_to_cpu(from->sb_rblocks); in __xfs_sb_from_disk()
556 to->sb_rextents = be64_to_cpu(from->sb_rextents); in __xfs_sb_from_disk()
557 memcpy(&to->sb_uuid, &from->sb_uuid, sizeof(to->sb_uuid)); in __xfs_sb_from_disk()
558 to->sb_logstart = be64_to_cpu(from->sb_logstart); in __xfs_sb_from_disk()
559 to->sb_rootino = be64_to_cpu(from->sb_rootino); in __xfs_sb_from_disk()
560 to->sb_rbmino = be64_to_cpu(from->sb_rbmino); in __xfs_sb_from_disk()
[all …]
Dxfs_inode_buf.c285 struct xfs_dinode *to, in xfs_inode_to_disk() argument
290 to->di_magic = cpu_to_be16(XFS_DINODE_MAGIC); in xfs_inode_to_disk()
291 to->di_onlink = 0; in xfs_inode_to_disk()
293 to->di_format = xfs_ifork_format(&ip->i_df); in xfs_inode_to_disk()
294 to->di_uid = cpu_to_be32(i_uid_read(inode)); in xfs_inode_to_disk()
295 to->di_gid = cpu_to_be32(i_gid_read(inode)); in xfs_inode_to_disk()
296 to->di_projid_lo = cpu_to_be16(ip->i_projid & 0xffff); in xfs_inode_to_disk()
297 to->di_projid_hi = cpu_to_be16(ip->i_projid >> 16); in xfs_inode_to_disk()
299 memset(to->di_pad, 0, sizeof(to->di_pad)); in xfs_inode_to_disk()
300 to->di_atime = xfs_inode_to_disk_ts(ip, inode->i_atime); in xfs_inode_to_disk()
[all …]
/fs/nls/
DKconfig11 as the ability of some filesystems to use native languages
27 system (if different) to store data (filenames) on a disk.
45 in so-called DOS codepages. You need to include the appropriate
46 codepage if you want to be able to read/write these filenames on
47 DOS/Windows partitions correctly. This does apply to the filenames
48 only, not to the file contents. You can include several codepages;
49 say Y here if you want to include the DOS codepage that is used in
57 in so-called DOS codepages. You need to include the appropriate
58 codepage if you want to be able to read/write these filenames on
59 DOS/Windows partitions correctly. This does apply to the filenames
[all …]
/fs/xfs/
Dxfs_inode_item_recover.c148 struct xfs_dinode *to, in xfs_log_dinode_to_disk() argument
151 to->di_magic = cpu_to_be16(from->di_magic); in xfs_log_dinode_to_disk()
152 to->di_mode = cpu_to_be16(from->di_mode); in xfs_log_dinode_to_disk()
153 to->di_version = from->di_version; in xfs_log_dinode_to_disk()
154 to->di_format = from->di_format; in xfs_log_dinode_to_disk()
155 to->di_onlink = 0; in xfs_log_dinode_to_disk()
156 to->di_uid = cpu_to_be32(from->di_uid); in xfs_log_dinode_to_disk()
157 to->di_gid = cpu_to_be32(from->di_gid); in xfs_log_dinode_to_disk()
158 to->di_nlink = cpu_to_be32(from->di_nlink); in xfs_log_dinode_to_disk()
159 to->di_projid_lo = cpu_to_be16(from->di_projid_lo); in xfs_log_dinode_to_disk()
[all …]
Dxfs_inode_item.c345 struct xfs_log_dinode *to) in xfs_copy_dm_fields_to_log_dinode() argument
353 to->di_dmevmask = be32_to_cpu(dip->di_dmevmask); in xfs_copy_dm_fields_to_log_dinode()
354 to->di_dmstate = be16_to_cpu(dip->di_dmstate); in xfs_copy_dm_fields_to_log_dinode()
356 to->di_dmevmask = 0; in xfs_copy_dm_fields_to_log_dinode()
357 to->di_dmstate = 0; in xfs_copy_dm_fields_to_log_dinode()
364 struct xfs_log_dinode *to, in xfs_inode_to_log_dinode() argument
369 to->di_magic = XFS_DINODE_MAGIC; in xfs_inode_to_log_dinode()
370 to->di_format = xfs_ifork_format(&ip->i_df); in xfs_inode_to_log_dinode()
371 to->di_uid = i_uid_read(inode); in xfs_inode_to_log_dinode()
372 to->di_gid = i_gid_read(inode); in xfs_inode_to_log_dinode()
[all …]
DKconfig13 Btrees (directories, extents, free space) to aid both performance
16 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
23 to use an initial ramdisk (initrd) to boot.
32 metadata verification, and the ability to store timestamps past the
41 upgrade xfsprogs to the latest version and try again.
45 can say N here to withdraw support earlier.
55 If you say Y here, you will be able to set limits for disk usage on
57 information as filesystem metadata and uses journaling to provide a
60 filesystem to be migrated between Linux and IRIX without any need
82 If you say Y here you will be able to mount and use XFS filesystems
[all …]
/fs/reiserfs/
DREADME9 Reiser, or authorized to be licensed by him, have been in the past,
10 and likely will be in the future, licensed to other parties under
11 other licenses. If you add your code to governed files, and don't
12 want it to be owned by Hans Reiser, put your copyright label on that
15 Reiser, and by adding your code to it, widely distributing it to
19 to license code labeled as owned by you on your behalf other than
20 under the GPL, because he wants to know if it is okay to do so and put
21 a check in the mail to you (for non-trivial improvements) when he
22 makes his next sale. He makes no guarantees as to the amount if any,
23 though he feels motivated to motivate contributors, and you can surely
[all …]
/fs/jffs2/
DREADME.Locking5 This document attempts to describe the existing locking rules for
6 JFFS2. It is not expected to remain perfectly up to date, but ought to
13 The alloc_sem is a per-filesystem mutex, used primarily to ensure
23 have been properly linked into the data structures for the inode to
25 nodes to an inode may obsolete old ones, and by holding the alloc_sem
29 don't actually get erased until the write-buffer has been flushed to
33 the alloc_sem is also used to protect the wbuf-related members of the
34 jffs2_sb_info structure. Atomically reading the wbuf_len member to see
48 The reason that the i_sem itself isn't used for this purpose is to
50 before calling a function which may need to allocate space. The
[all …]
/fs/cifs/
DKconfig26 to the original dialect, the Server Message Block (SMB) protocol, the
40 for mounting to SMB3 (and CIFS) compliant servers. It includes
49 Note that when mounting to Samba, due to the CIFS POSIX extensions,
52 slightly simpler (compared to CIFS) due to protocol improvements.
54 If you need to mount to Samba, Azure, Macs or Windows from this machine, say Y.
62 request timing to be displayed in /proc/fs/cifs/DebugData and also
63 allow optional logging of slow responses to dmesg (depending on the
90 utilities to provide SPNEGO packaged (RFC 4178) Kerberos tickets
91 which are needed to mount to certain secure servers (for which more
101 namespace prefix to SMB/CIFS EAs. EAs are stored on Windows
[all …]
/fs/sysv/
Dinode.c109 unsigned char * from, unsigned char * to) in read3byte() argument
112 to[0] = from[0]; in read3byte()
113 to[1] = 0; in read3byte()
114 to[2] = from[1]; in read3byte()
115 to[3] = from[2]; in read3byte()
117 to[0] = from[0]; in read3byte()
118 to[1] = from[1]; in read3byte()
119 to[2] = from[2]; in read3byte()
120 to[3] = 0; in read3byte()
122 to[0] = 0; in read3byte()
[all …]
/fs/affs/
DChanges14 Alas, I've got no alpha to debug. :-(
20 - The feature to automatically make the fs clean
24 - When a file is truncated to a size that is not
27 this fs never claimed to be Posix conformant.
29 Please direct bug reports to: zippel@linux-m68k.org
45 - change to global min macro + warning fixes
65 - disable link to directories until we can properly support them.
94 - Converted to use 2.3.x page cache [Dave Jones]
100 - Changed partition checker to allow devices
104 word at 0xd0 that Windows likes to write to.
[all …]
/fs/befs/
DChangeLog15 Thanks to Laszlo Boszormenyi for pointing this out to me.
19 * Added Sergey S. Kostyliov's patch to eliminate memcpy() overhead
33 wouldn't work on older (<2.4.10) kernels due to an unresolved symbol.
37 * Sergey S. Kostyliov made befs_find_key() use a binary search to find
53 names like file1 and file2 to mysteriously be duplicates of each other
54 (because they have the same inode number). Many thanks to Pavel Roskin
76 * Made functions in endian.h to do the correct byteswapping, no matter
83 * Added byteswapping to all metadata reads from disk.
86 * Remove the typedef of struct super_block to vfs_sb, as it offended
101 * Added mount option to control debug printing.
[all …]
/fs/nfsd/
DKconfig13 Choose Y here if you want to allow other computers to access
18 You may choose to use a user-space NFS server instead, in which
21 To export local file systems using NFS, you also need to install
28 available to clients mounting the NFS server on this system.
54 This protocol extension allows applications on NFS clients to
60 NFSv3 ACL protocol extension allowing NFS clients to manipulate
65 To store ACLs on your NFS server, you also need to enable ACL-
85 To export files using NFSv4, you need to install additional user
102 clients to directly perform I/O to block devices accessible to both
116 clients to directly perform I/O to SCSI devices accessible to both
[all …]
/fs/
Dselect.c273 int poll_select_set_timeout(struct timespec64 *to, time64_t sec, long nsec) in poll_select_set_timeout() argument
282 to->tv_sec = to->tv_nsec = 0; in poll_select_set_timeout()
284 ktime_get_ts64(to); in poll_select_set_timeout()
285 *to = timespec64_add_safe(*to, ts); in poll_select_set_timeout()
480 ktime_t expire, *to = NULL; in do_select() local
601 if (end_time && !to) { in do_select()
603 to = &expire; in do_select()
607 to, slack)) in do_select()
706 struct timespec64 end_time, *to = NULL; in kern_select() local
714 to = &end_time; in kern_select()
[all …]
DKconfig.binfmt13 systems. Saying Y here will enable your kernel to run ELF binaries
17 to run executables from different architectures or operating systems
20 want to say Y here.
27 you'll have to install the newest ELF runtime libraries, including
55 segments of a binary to be located in memory independently of each
57 MMU is available as it still permits text segments to be shared,
60 It is also possible to run FDPIC ELF binaries on MMU linux also.
77 the first page of the file in a core dump makes it possible to
79 cost and disk space to dump all the text. However, versions of
93 Say Y here if you want to execute interpreted scripts starting with
[all …]
/fs/fat/
DKconfig6 If you want to use one of the FAT-based file systems (the MS-DOS and
8 to include FAT support. You will then be able to mount partitions or
14 the foundation for the other file systems. You will have to say Y or
15 M to at least one of "MSDOS fs support" or "VFAT fs support" in
16 order to make use of it.
18 Another way to read and write MSDOS floppies and hard drive
20 mtools ("man mtools") program suite. You don't need to say Y here in
21 order to do that.
23 If you need to move large files on floppies between a DOS and a
34 -- they will have to be modules as well.
[all …]
/fs/jfs/
Djfs_unicode.c19 int jfs_strfromUCS_le(char *to, const __le16 * from, in jfs_strfromUCS_le() argument
32 &to[outlen], in jfs_strfromUCS_le()
37 to[outlen++] = '?'; in jfs_strfromUCS_le()
42 to[i] = '?'; in jfs_strfromUCS_le()
55 to[i] = (char) (le16_to_cpu(from[i])); in jfs_strfromUCS_le()
59 to[outlen] = 0; in jfs_strfromUCS_le()
69 static int jfs_strtoUCS(wchar_t * to, const unsigned char *from, int len, in jfs_strtoUCS() argument
78 charlen = codepage->char2uni(from, len, &to[i]); in jfs_strtoUCS()
89 to[i] = (wchar_t) from[i]; in jfs_strtoUCS()
92 to[i] = 0; in jfs_strtoUCS()
/fs/cramfs/
DREADME23 null-padded to a multiple of 4 bytes.
25 The order of inode traversal is described as "width-first" (not to be
33 allows cramfs_lookup to return more quickly when a filename does not
44 padding to multiple of 4 bytes
61 aligned to a 4-byte boundary. The block size is either blksize
64 the block data. This is used to allow discontiguous data layout
74 applied to the i'th blksize-sized chunk of the input data if the
99 kernels up to at least 2.3.39 didn't support holes. Run mkcramfs
100 with -z if you want it to create files that can have holes in them.
116 (Block size in cramfs refers to the size of input data that is
[all …]
/fs/sysfs/
DKconfig7 The sysfs filesystem is a virtual filesystem that the kernel uses to
9 relationships to one another.
11 Users can use sysfs to ascertain useful information about the running
13 which driver each is bound to. sysfs can also be used to tune devices
16 Some system agents rely on the information in sysfs to operate.
17 /sbin/hotplug uses device and object attributes in sysfs to assist in
20 sysfs is currently used by the block subsystem to mount the root
25 Designers of embedded systems may wish to say N here to conserve space.
/fs/ufs/
DKconfig9 this file system as well. Saying Y here will allow you to read from
10 these partitions; if you also want to write to them, say Y to the
18 good portable way to transport files and directories between unixes
22 When accessing NeXTstep files, you may need to convert them from the
23 NeXT character set to the Latin1 character set; use the program
29 If you haven't heard about all of this before, it's safe to say N.
35 Say Y here if you want to try writing to UFS partitions. This is
43 Y here. This will result in _many_ additional debugging messages to be
44 written to the system log.
/fs/fuse/
DKconfig6 With FUSE it is possible to implement a fully functional filesystem
18 If you want to develop a userspace FS, or if you want to use
25 This FUSE extension allows character devices to be
28 If you want to develop or use a userspace character device
36 The Virtio Filesystem allows guests to mount file systems from the
39 If you want to share files between guests or with the host, answer Y
53 If you want to allow mounting a Virtio Filesystem with the "dax"
57 bool "Adds BPF to fuse"
61 Extends FUSE by adding BPF to prefilter calls and potentially pass to a
/fs/pstore/
DKconfig7 This option enables generic access to platform level
10 a platform level driver that registers with pstore to
12 (or "M") to a platform specific persistent store driver
23 Can be enlarged if needed, not recommended to shrink it.
132 interface /dev/pmsg0 to log user space messages. On reboot
145 pstore filesystem. It can be used to determine what function
151 tristate "Log panic/oops to a RAM buffer"
158 This enables panic and oops messages to be logged to a circular
171 to manage storage in zones.
174 tristate "Log panic/oops to a block device"
[all …]
/fs/gfs2/
DKconfig12 Allows a cluster of computers to simultaneously use a block device
14 and writes to the block device like a local filesystem, but also uses
15 a lock module to allow the computers coordinate their I/O so
17 GFS is perfect consistency -- changes made to the filesystem on one
20 To use the GFS2 filesystem in a cluster, you will need to enable
24 The "nolock" lock module is now built in to GFS2 by default. If
25 you want to use the DLM, be sure to enable IPv4/6 networking.
35 interface between GFS2 and the DLM, which is required to use GFS2
/fs/ocfs2/
DKconfig12 system with many similarities to ext3. It supports 64 bit inode
16 You'll want to install the ocfs2-tools package in order to at least
33 to configure it. This comes with the standard ocfs2-tools package.
34 O2CB is limited to maintaining a cluster for OCFS2 file systems.
37 It is always safe to say Y here, as the clustering method is
45 This option will allow OCFS2 to use userspace clustering services
49 It is safe to say Y, as the clustering method is run-time
57 This option allows some fs statistics to be captured. Enabling
66 allows selection of events to log via files in /sys/o2cb/logmask/.
76 this option for debugging only as it is likely to decrease
/fs/ntfs/
DKconfig10 say Y to "NTFS write support" below.
17 the old NTFS code starting with Linux 2.5.11. A backport to
27 If you are not using Windows NT, 2000, XP or 2003 in addition to
28 Linux on your computer it is safe to say N.
35 Y here. This will result in additional consistency checks to be
36 performed by the driver as well as additional debugging messages to
37 be written to the system log. Note that debugging messages are
40 to insmod when loading the ntfs module. Once the driver is active,
49 When reporting bugs, please try to have available a full dump of
60 renaming is possible. Note only non-resident files can be written to
[all …]

12345678910