2007-10-19 10:41:07 +04:00
|
|
|
menuconfig SAMPLES
|
|
|
|
|
bool "Sample kernel code"
|
|
|
|
|
help
|
|
|
|
|
You can build and test sample kernel code here.
|
|
|
|
|
|
|
|
|
|
if SAMPLES
|
|
|
|
|
|
2009-04-15 05:37:03 +04:00
|
|
|
config SAMPLE_TRACE_EVENTS
|
2009-05-06 06:32:32 +04:00
|
|
|
tristate "Build trace_events examples -- loadable modules only"
|
|
|
|
|
depends on EVENT_TRACING && m
|
2009-04-15 05:37:03 +04:00
|
|
|
help
|
|
|
|
|
This build trace event example modules.
|
|
|
|
|
|
2016-06-17 21:50:23 +03:00
|
|
|
config SAMPLE_TRACE_PRINTK
|
|
|
|
|
tristate "Build trace_printk module - tests various trace_printk formats"
|
|
|
|
|
depends on EVENT_TRACING && m
|
|
|
|
|
help
|
|
|
|
|
This builds a module that calls trace_printk() and can be used to
|
|
|
|
|
test various trace_printk() calls from a module.
|
|
|
|
|
|
2007-11-27 22:28:26 +03:00
|
|
|
config SAMPLE_KOBJECT
|
2009-05-26 16:19:35 +04:00
|
|
|
tristate "Build kobject examples -- loadable modules only"
|
|
|
|
|
depends on m
|
2007-11-27 22:28:26 +03:00
|
|
|
help
|
|
|
|
|
This config option will allow you to build a number of
|
|
|
|
|
different kobject sample modules showing how to use kobjects,
|
|
|
|
|
ksets, and ktypes properly.
|
|
|
|
|
|
|
|
|
|
If in doubt, say "N" here.
|
|
|
|
|
|
2008-03-05 01:28:38 +03:00
|
|
|
config SAMPLE_KPROBES
|
|
|
|
|
tristate "Build kprobes examples -- loadable modules only"
|
|
|
|
|
depends on KPROBES && m
|
|
|
|
|
help
|
|
|
|
|
This build several kprobes example modules.
|
|
|
|
|
|
|
|
|
|
config SAMPLE_KRETPROBES
|
|
|
|
|
tristate "Build kretprobes example -- loadable modules only"
|
|
|
|
|
default m
|
|
|
|
|
depends on SAMPLE_KPROBES && KRETPROBES
|
|
|
|
|
|
2009-06-01 22:16:20 +04:00
|
|
|
config SAMPLE_HW_BREAKPOINT
|
|
|
|
|
tristate "Build kernel hardware breakpoint examples -- loadable module only"
|
|
|
|
|
depends on HAVE_HW_BREAKPOINT && m
|
|
|
|
|
help
|
|
|
|
|
This builds kernel hardware breakpoint example modules.
|
|
|
|
|
|
2010-08-11 05:03:39 +04:00
|
|
|
config SAMPLE_KFIFO
|
|
|
|
|
tristate "Build kfifo examples -- loadable modules only"
|
|
|
|
|
depends on m
|
|
|
|
|
help
|
|
|
|
|
This config option will allow you to build a number of
|
|
|
|
|
different kfifo sample modules showing how to use the
|
|
|
|
|
generic kfifo API.
|
|
|
|
|
|
|
|
|
|
If in doubt, say "N" here.
|
|
|
|
|
|
2010-10-25 19:14:05 +04:00
|
|
|
config SAMPLE_KDB
|
2011-03-31 05:57:33 +04:00
|
|
|
tristate "Build kdb command example -- loadable modules only"
|
2010-10-25 19:14:05 +04:00
|
|
|
depends on KGDB_KDB && m
|
|
|
|
|
help
|
|
|
|
|
Build an example of how to dynamically add the hello
|
|
|
|
|
command to the kdb shell.
|
|
|
|
|
|
2017-06-26 19:02:28 +03:00
|
|
|
config SAMPLE_QMI_CLIENT
|
|
|
|
|
tristate "Build qmi client sample -- loadable modules only"
|
|
|
|
|
depends on m
|
|
|
|
|
depends on ARCH_QCOM
|
2018-02-22 18:57:38 +03:00
|
|
|
depends on NET
|
2017-06-26 19:02:28 +03:00
|
|
|
select QCOM_QMI_HELPERS
|
|
|
|
|
help
|
|
|
|
|
Build an QMI client sample driver, which demonstrates how to
|
|
|
|
|
communicate with a remote QRTR service, using QMI encoded messages.
|
|
|
|
|
|
2011-10-20 23:41:24 +04:00
|
|
|
config SAMPLE_RPMSG_CLIENT
|
|
|
|
|
tristate "Build rpmsg client sample -- loadable modules only"
|
|
|
|
|
depends on RPMSG && m
|
|
|
|
|
help
|
|
|
|
|
Build an rpmsg client sample driver, which demonstrates how
|
|
|
|
|
to communicate with an AMP-configured remote processor over
|
|
|
|
|
the rpmsg bus.
|
|
|
|
|
|
2015-02-04 01:45:18 +03:00
|
|
|
config SAMPLE_LIVEPATCH
|
2017-08-31 23:37:41 +03:00
|
|
|
tristate "Build live patching samples -- loadable modules only"
|
2015-02-04 01:45:18 +03:00
|
|
|
depends on LIVEPATCH && m
|
2014-12-16 20:58:20 +03:00
|
|
|
help
|
2017-08-31 23:37:41 +03:00
|
|
|
Build sample live patch demonstrations.
|
2014-12-16 20:58:20 +03:00
|
|
|
|
2015-10-03 16:32:59 +03:00
|
|
|
config SAMPLE_CONFIGFS
|
|
|
|
|
tristate "Build configfs patching sample -- loadable modules only"
|
|
|
|
|
depends on CONFIGFS_FS && m
|
|
|
|
|
help
|
|
|
|
|
Builds a sample configfs interface.
|
|
|
|
|
|
2016-04-25 19:03:08 +03:00
|
|
|
config SAMPLE_CONNECTOR
|
|
|
|
|
tristate "Build connector sample -- loadable modules only"
|
|
|
|
|
depends on CONNECTOR && m
|
|
|
|
|
help
|
|
|
|
|
When enabled, this builds both a sample kernel module for
|
|
|
|
|
the connector interface and a user space tool to communicate
|
|
|
|
|
with it.
|
|
|
|
|
See also Documentation/connector/connector.txt
|
|
|
|
|
|
2016-07-06 09:53:19 +03:00
|
|
|
config SAMPLE_SECCOMP
|
|
|
|
|
tristate "Build seccomp sample code -- loadable modules only"
|
|
|
|
|
depends on SECCOMP_FILTER && m
|
|
|
|
|
help
|
|
|
|
|
Build samples of seccomp filters using various methods of
|
|
|
|
|
BPF filter construction.
|
|
|
|
|
|
2016-12-30 18:13:30 +03:00
|
|
|
config SAMPLE_VFIO_MDEV_MTTY
|
|
|
|
|
tristate "Build VFIO mtty example mediated device sample code -- loadable modules only"
|
|
|
|
|
depends on VFIO_MDEV_DEVICE && m
|
|
|
|
|
help
|
|
|
|
|
Build a virtual tty sample driver for use as a VFIO
|
|
|
|
|
mediated device
|
|
|
|
|
|
2018-05-11 18:05:03 +03:00
|
|
|
config SAMPLE_VFIO_MDEV_MDPY
|
|
|
|
|
tristate "Build VFIO mdpy example mediated device sample code -- loadable modules only"
|
|
|
|
|
depends on VFIO_MDEV_DEVICE && m
|
|
|
|
|
help
|
|
|
|
|
Build a virtual display sample driver for use as a VFIO
|
|
|
|
|
mediated device. It is a simple framebuffer and supports
|
|
|
|
|
the region display interface (VFIO_GFX_PLANE_TYPE_REGION).
|
|
|
|
|
|
2018-05-11 18:05:04 +03:00
|
|
|
config SAMPLE_VFIO_MDEV_MDPY_FB
|
|
|
|
|
tristate "Build VFIO mdpy example guest fbdev driver -- loadable module only"
|
|
|
|
|
depends on FB && m
|
|
|
|
|
select FB_CFB_FILLRECT
|
|
|
|
|
select FB_CFB_COPYAREA
|
|
|
|
|
select FB_CFB_IMAGEBLIT
|
|
|
|
|
help
|
|
|
|
|
Guest fbdev driver for the virtual display sample driver.
|
|
|
|
|
|
2018-05-11 18:05:04 +03:00
|
|
|
config SAMPLE_VFIO_MDEV_MBOCHS
|
|
|
|
|
tristate "Build VFIO mdpy example mediated device sample code -- loadable modules only"
|
|
|
|
|
depends on VFIO_MDEV_DEVICE && m
|
2018-05-31 00:37:31 +03:00
|
|
|
select DMA_SHARED_BUFFER
|
2018-05-11 18:05:04 +03:00
|
|
|
help
|
|
|
|
|
Build a virtual display sample driver for use as a VFIO
|
|
|
|
|
mediated device. It supports the region display interface
|
|
|
|
|
(VFIO_GFX_PLANE_TYPE_DMABUF).
|
|
|
|
|
Emulate enough of qemu stdvga to make bochs-drm.ko happy.
|
|
|
|
|
That is basically the vram memory bar and the bochs dispi
|
|
|
|
|
interface vbe registers in the mmio register bar.
|
|
|
|
|
Specifically it does *not* include any legacy vga stuff.
|
|
|
|
|
Device looks a lot like "qemu -device secondary-vga".
|
|
|
|
|
|
statx: Add a system call to make enhanced file info available
Add a system call to make extended file information available, including
file creation and some attribute flags where available through the
underlying filesystem.
The getattr inode operation is altered to take two additional arguments: a
u32 request_mask and an unsigned int flags that indicate the
synchronisation mode. This change is propagated to the vfs_getattr*()
function.
Functions like vfs_stat() are now inline wrappers around new functions
vfs_statx() and vfs_statx_fd() to reduce stack usage.
========
OVERVIEW
========
The idea was initially proposed as a set of xattrs that could be retrieved
with getxattr(), but the general preference proved to be for a new syscall
with an extended stat structure.
A number of requests were gathered for features to be included. The
following have been included:
(1) Make the fields a consistent size on all arches and make them large.
(2) Spare space, request flags and information flags are provided for
future expansion.
(3) Better support for the y2038 problem [Arnd Bergmann] (tv_sec is an
__s64).
(4) Creation time: The SMB protocol carries the creation time, which could
be exported by Samba, which will in turn help CIFS make use of
FS-Cache as that can be used for coherency data (stx_btime).
This is also specified in NFSv4 as a recommended attribute and could
be exported by NFSD [Steve French].
(5) Lightweight stat: Ask for just those details of interest, and allow a
netfs (such as NFS) to approximate anything not of interest, possibly
without going to the server [Trond Myklebust, Ulrich Drepper, Andreas
Dilger] (AT_STATX_DONT_SYNC).
(6) Heavyweight stat: Force a netfs to go to the server, even if it thinks
its cached attributes are up to date [Trond Myklebust]
(AT_STATX_FORCE_SYNC).
And the following have been left out for future extension:
(7) Data version number: Could be used by userspace NFS servers [Aneesh
Kumar].
Can also be used to modify fill_post_wcc() in NFSD which retrieves
i_version directly, but has just called vfs_getattr(). It could get
it from the kstat struct if it used vfs_xgetattr() instead.
(There's disagreement on the exact semantics of a single field, since
not all filesystems do this the same way).
(8) BSD stat compatibility: Including more fields from the BSD stat such
as creation time (st_btime) and inode generation number (st_gen)
[Jeremy Allison, Bernd Schubert].
(9) Inode generation number: Useful for FUSE and userspace NFS servers
[Bernd Schubert].
(This was asked for but later deemed unnecessary with the
open-by-handle capability available and caused disagreement as to
whether it's a security hole or not).
(10) Extra coherency data may be useful in making backups [Andreas Dilger].
(No particular data were offered, but things like last backup
timestamp, the data version number and the DOS archive bit would come
into this category).
(11) Allow the filesystem to indicate what it can/cannot provide: A
filesystem can now say it doesn't support a standard stat feature if
that isn't available, so if, for instance, inode numbers or UIDs don't
exist or are fabricated locally...
(This requires a separate system call - I have an fsinfo() call idea
for this).
(12) Store a 16-byte volume ID in the superblock that can be returned in
struct xstat [Steve French].
(Deferred to fsinfo).
(13) Include granularity fields in the time data to indicate the
granularity of each of the times (NFSv4 time_delta) [Steve French].
(Deferred to fsinfo).
(14) FS_IOC_GETFLAGS value. These could be translated to BSD's st_flags.
Note that the Linux IOC flags are a mess and filesystems such as Ext4
define flags that aren't in linux/fs.h, so translation in the kernel
may be a necessity (or, possibly, we provide the filesystem type too).
(Some attributes are made available in stx_attributes, but the general
feeling was that the IOC flags were to ext[234]-specific and shouldn't
be exposed through statx this way).
(15) Mask of features available on file (eg: ACLs, seclabel) [Brad Boyer,
Michael Kerrisk].
(Deferred, probably to fsinfo. Finding out if there's an ACL or
seclabal might require extra filesystem operations).
(16) Femtosecond-resolution timestamps [Dave Chinner].
(A __reserved field has been left in the statx_timestamp struct for
this - if there proves to be a need).
(17) A set multiple attributes syscall to go with this.
===============
NEW SYSTEM CALL
===============
The new system call is:
int ret = statx(int dfd,
const char *filename,
unsigned int flags,
unsigned int mask,
struct statx *buffer);
The dfd, filename and flags parameters indicate the file to query, in a
similar way to fstatat(). There is no equivalent of lstat() as that can be
emulated with statx() by passing AT_SYMLINK_NOFOLLOW in flags. There is
also no equivalent of fstat() as that can be emulated by passing a NULL
filename to statx() with the fd of interest in dfd.
Whether or not statx() synchronises the attributes with the backing store
can be controlled by OR'ing a value into the flags argument (this typically
only affects network filesystems):
(1) AT_STATX_SYNC_AS_STAT tells statx() to behave as stat() does in this
respect.
(2) AT_STATX_FORCE_SYNC will require a network filesystem to synchronise
its attributes with the server - which might require data writeback to
occur to get the timestamps correct.
(3) AT_STATX_DONT_SYNC will suppress synchronisation with the server in a
network filesystem. The resulting values should be considered
approximate.
mask is a bitmask indicating the fields in struct statx that are of
interest to the caller. The user should set this to STATX_BASIC_STATS to
get the basic set returned by stat(). It should be noted that asking for
more information may entail extra I/O operations.
buffer points to the destination for the data. This must be 256 bytes in
size.
======================
MAIN ATTRIBUTES RECORD
======================
The following structures are defined in which to return the main attribute
set:
struct statx_timestamp {
__s64 tv_sec;
__s32 tv_nsec;
__s32 __reserved;
};
struct statx {
__u32 stx_mask;
__u32 stx_blksize;
__u64 stx_attributes;
__u32 stx_nlink;
__u32 stx_uid;
__u32 stx_gid;
__u16 stx_mode;
__u16 __spare0[1];
__u64 stx_ino;
__u64 stx_size;
__u64 stx_blocks;
__u64 __spare1[1];
struct statx_timestamp stx_atime;
struct statx_timestamp stx_btime;
struct statx_timestamp stx_ctime;
struct statx_timestamp stx_mtime;
__u32 stx_rdev_major;
__u32 stx_rdev_minor;
__u32 stx_dev_major;
__u32 stx_dev_minor;
__u64 __spare2[14];
};
The defined bits in request_mask and stx_mask are:
STATX_TYPE Want/got stx_mode & S_IFMT
STATX_MODE Want/got stx_mode & ~S_IFMT
STATX_NLINK Want/got stx_nlink
STATX_UID Want/got stx_uid
STATX_GID Want/got stx_gid
STATX_ATIME Want/got stx_atime{,_ns}
STATX_MTIME Want/got stx_mtime{,_ns}
STATX_CTIME Want/got stx_ctime{,_ns}
STATX_INO Want/got stx_ino
STATX_SIZE Want/got stx_size
STATX_BLOCKS Want/got stx_blocks
STATX_BASIC_STATS [The stuff in the normal stat struct]
STATX_BTIME Want/got stx_btime{,_ns}
STATX_ALL [All currently available stuff]
stx_btime is the file creation time, stx_mask is a bitmask indicating the
data provided and __spares*[] are where as-yet undefined fields can be
placed.
Time fields are structures with separate seconds and nanoseconds fields
plus a reserved field in case we want to add even finer resolution. Note
that times will be negative if before 1970; in such a case, the nanosecond
fields will also be negative if not zero.
The bits defined in the stx_attributes field convey information about a
file, how it is accessed, where it is and what it does. The following
attributes map to FS_*_FL flags and are the same numerical value:
STATX_ATTR_COMPRESSED File is compressed by the fs
STATX_ATTR_IMMUTABLE File is marked immutable
STATX_ATTR_APPEND File is append-only
STATX_ATTR_NODUMP File is not to be dumped
STATX_ATTR_ENCRYPTED File requires key to decrypt in fs
Within the kernel, the supported flags are listed by:
KSTAT_ATTR_FS_IOC_FLAGS
[Are any other IOC flags of sufficient general interest to be exposed
through this interface?]
New flags include:
STATX_ATTR_AUTOMOUNT Object is an automount trigger
These are for the use of GUI tools that might want to mark files specially,
depending on what they are.
Fields in struct statx come in a number of classes:
(0) stx_dev_*, stx_blksize.
These are local system information and are always available.
(1) stx_mode, stx_nlinks, stx_uid, stx_gid, stx_[amc]time, stx_ino,
stx_size, stx_blocks.
These will be returned whether the caller asks for them or not. The
corresponding bits in stx_mask will be set to indicate whether they
actually have valid values.
If the caller didn't ask for them, then they may be approximated. For
example, NFS won't waste any time updating them from the server,
unless as a byproduct of updating something requested.
If the values don't actually exist for the underlying object (such as
UID or GID on a DOS file), then the bit won't be set in the stx_mask,
even if the caller asked for the value. In such a case, the returned
value will be a fabrication.
Note that there are instances where the type might not be valid, for
instance Windows reparse points.
(2) stx_rdev_*.
This will be set only if stx_mode indicates we're looking at a
blockdev or a chardev, otherwise will be 0.
(3) stx_btime.
Similar to (1), except this will be set to 0 if it doesn't exist.
=======
TESTING
=======
The following test program can be used to test the statx system call:
samples/statx/test-statx.c
Just compile and run, passing it paths to the files you want to examine.
The file is built automatically if CONFIG_SAMPLES is enabled.
Here's some example output. Firstly, an NFS directory that crosses to
another FSID. Note that the AUTOMOUNT attribute is set because transiting
this directory will cause d_automount to be invoked by the VFS.
[root@andromeda ~]# /tmp/test-statx -A /warthog/data
statx(/warthog/data) = 0
results=7ff
Size: 4096 Blocks: 8 IO Block: 1048576 directory
Device: 00:26 Inode: 1703937 Links: 125
Access: (3777/drwxrwxrwx) Uid: 0 Gid: 4041
Access: 2016-11-24 09:02:12.219699527+0000
Modify: 2016-11-17 10:44:36.225653653+0000
Change: 2016-11-17 10:44:36.225653653+0000
Attributes: 0000000000001000 (-------- -------- -------- -------- -------- -------- ---m---- --------)
Secondly, the result of automounting on that directory.
[root@andromeda ~]# /tmp/test-statx /warthog/data
statx(/warthog/data) = 0
results=7ff
Size: 4096 Blocks: 8 IO Block: 1048576 directory
Device: 00:27 Inode: 2 Links: 125
Access: (3777/drwxrwxrwx) Uid: 0 Gid: 4041
Access: 2016-11-24 09:02:12.219699527+0000
Modify: 2016-11-17 10:44:36.225653653+0000
Change: 2016-11-17 10:44:36.225653653+0000
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2017-01-31 19:46:22 +03:00
|
|
|
config SAMPLE_STATX
|
|
|
|
|
bool "Build example extended-stat using code"
|
|
|
|
|
depends on BROKEN
|
|
|
|
|
help
|
|
|
|
|
Build example userspace program to use the new extended-stat syscall.
|
|
|
|
|
|
2007-10-19 10:41:07 +04:00
|
|
|
endif # SAMPLES
|
