<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/Documentation/userspace-api/index.rst, branch linux-5.19.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.19.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.19.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2021-10-07T11:51:13Z</updated>
<entry>
<title>futex2: Documentation: Document sys_futex_waitv() uAPI</title>
<updated>2021-10-07T11:51:13Z</updated>
<author>
<name>André Almeida</name>
</author>
<published>2021-09-23T17:11:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dd0aa2cd2e9e3e49b8c3b43924dc1a1d4e22b4d1'/>
<id>urn:sha1:dd0aa2cd2e9e3e49b8c3b43924dc1a1d4e22b4d1</id>
<content type='text'>
Create userspace documentation for futex_waitv() syscall, detailing how
the arguments are used.

Signed-off-by: André Almeida &lt;andrealmeid@collabora.com&gt;
Signed-off-by: Peter Zijlstra (Intel) &lt;peterz@infradead.org&gt;
Link: https://lore.kernel.org/r/20210923171111.300673-23-andrealmeid@collabora.com
</content>
</entry>
<entry>
<title>Documentation: Add documentation for VDUSE</title>
<updated>2021-09-06T11:20:58Z</updated>
<author>
<name>Xie Yongji</name>
</author>
<published>2021-08-31T10:36:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7bc7f61897b66bef78bb5952e3d1e9f3aaf9ccca'/>
<id>urn:sha1:7bc7f61897b66bef78bb5952e3d1e9f3aaf9ccca</id>
<content type='text'>
VDUSE (vDPA Device in Userspace) is a framework to support
implementing software-emulated vDPA devices in userspace. This
document is intended to clarify the VDUSE design and usage.

Signed-off-by: Xie Yongji &lt;xieyongji@bytedance.com&gt;
Acked-by: Jason Wang &lt;jasowang@redhat.com&gt;
Link: https://lore.kernel.org/r/20210831103634.33-14-xieyongji@bytedance.com
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge tag 'landlock_v34' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security</title>
<updated>2021-05-02T01:50:44Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2021-05-02T01:50:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=17ae69aba89dbfa2139b7f8024b757ab3cc42f59'/>
<id>urn:sha1:17ae69aba89dbfa2139b7f8024b757ab3cc42f59</id>
<content type='text'>
Pull Landlock LSM from James Morris:
 "Add Landlock, a new LSM from Mickaël Salaün.

  Briefly, Landlock provides for unprivileged application sandboxing.

  From Mickaël's cover letter:
    "The goal of Landlock is to enable to restrict ambient rights (e.g.
     global filesystem access) for a set of processes. Because Landlock
     is a stackable LSM [1], it makes possible to create safe security
     sandboxes as new security layers in addition to the existing
     system-wide access-controls. This kind of sandbox is expected to
     help mitigate the security impact of bugs or unexpected/malicious
     behaviors in user-space applications. Landlock empowers any
     process, including unprivileged ones, to securely restrict
     themselves.

     Landlock is inspired by seccomp-bpf but instead of filtering
     syscalls and their raw arguments, a Landlock rule can restrict the
     use of kernel objects like file hierarchies, according to the
     kernel semantic. Landlock also takes inspiration from other OS
     sandbox mechanisms: XNU Sandbox, FreeBSD Capsicum or OpenBSD
     Pledge/Unveil.

     In this current form, Landlock misses some access-control features.
     This enables to minimize this patch series and ease review. This
     series still addresses multiple use cases, especially with the
     combined use of seccomp-bpf: applications with built-in sandboxing,
     init systems, security sandbox tools and security-oriented APIs [2]"

  The cover letter and v34 posting is here:

      https://lore.kernel.org/linux-security-module/20210422154123.13086-1-mic@digikod.net/

  See also:

      https://landlock.io/

  This code has had extensive design discussion and review over several
  years"

Link: https://lore.kernel.org/lkml/50db058a-7dde-441b-a7f9-f6837fe8b69f@schaufler-ca.com/ [1]
Link: https://lore.kernel.org/lkml/f646e1c7-33cf-333f-070c-0a40ad0468cd@digikod.net/ [2]

* tag 'landlock_v34' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security:
  landlock: Enable user space to infer supported features
  landlock: Add user and kernel documentation
  samples/landlock: Add a sandbox manager example
  selftests/landlock: Add user space tests
  landlock: Add syscall implementations
  arch: Wire up Landlock syscalls
  fs,security: Add sb_delete hook
  landlock: Support filesystem access-control
  LSM: Infrastructure management of the superblock
  landlock: Add ptrace restrictions
  landlock: Set up the security framework and manage credentials
  landlock: Add ruleset and domain management
  landlock: Add object management
</content>
</entry>
<entry>
<title>landlock: Add user and kernel documentation</title>
<updated>2021-04-22T19:22:11Z</updated>
<author>
<name>Mickaël Salaün</name>
</author>
<published>2021-04-22T15:41:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5526b450834331d9196cae26acef0bfd5afd9fc4'/>
<id>urn:sha1:5526b450834331d9196cae26acef0bfd5afd9fc4</id>
<content type='text'>
Add a first document describing userspace API: how to define and enforce
a Landlock security policy.  This is explained with a simple example.
The Landlock system calls are described with their expected behavior and
current limitations.

Another document is dedicated to kernel developers, describing guiding
principles and some important kernel structures.

This documentation can be built with the Sphinx framework.

Cc: James Morris &lt;jmorris@namei.org&gt;
Cc: Jann Horn &lt;jannh@google.com&gt;
Cc: Serge E. Hallyn &lt;serge@hallyn.com&gt;
Signed-off-by: Mickaël Salaün &lt;mic@linux.microsoft.com&gt;
Reviewed-by: Vincent Dagonneau &lt;vincent.dagonneau@ssi.gouv.fr&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
Link: https://lore.kernel.org/r/20210422154123.13086-13-mic@digikod.net
Signed-off-by: James Morris &lt;jamorris@linux.microsoft.com&gt;
</content>
</entry>
<entry>
<title>docs/bpf: Add bpf() syscall command reference</title>
<updated>2021-03-05T02:39:46Z</updated>
<author>
<name>Joe Stringer</name>
</author>
<published>2021-03-02T17:19:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6197e5b7b1b5acd1e9b04bdf3527c694d84a27e2'/>
<id>urn:sha1:6197e5b7b1b5acd1e9b04bdf3527c694d84a27e2</id>
<content type='text'>
Generate the syscall command reference from the UAPI header file and
include it in the main bpf docs page.

Signed-off-by: Joe Stringer &lt;joe@cilium.io&gt;
Signed-off-by: Alexei Starovoitov &lt;ast@kernel.org&gt;
Reviewed-by: Quentin Monnet &lt;quentin@isovalent.com&gt;
Acked-by: Toke Høiland-Jørgensen &lt;toke@redhat.com&gt;
Link: https://lore.kernel.org/bpf/20210302171947.2268128-15-joe@cilium.io
</content>
</entry>
<entry>
<title>Documentation: Add documentation for new platform_profile sysfs attribute</title>
<updated>2020-12-30T17:28:57Z</updated>
<author>
<name>Mark Pearson</name>
</author>
<published>2020-12-30T00:18:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8e0cbf356377fabac47a027dd176cd1cacc5fc01'/>
<id>urn:sha1:8e0cbf356377fabac47a027dd176cd1cacc5fc01</id>
<content type='text'>
On modern systems the platform performance, temperature, fan and other
hardware related characteristics are often dynamically configurable. The
profile is often automatically adjusted to the load by some
automatic-mechanism (which may very well live outside the kernel).

These auto platform-adjustment mechanisms often can be configured with
one of several 'platform-profiles', with either a bias towards low-power
consumption or towards performance (and higher power consumption and
thermals).

Introduce a new platform_profile sysfs API which offers a generic API for
selecting the performance-profile of these automatic-mechanisms.

Co-developed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Mark Pearson &lt;markpearson@lenovo.com&gt;
Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;
</content>
</entry>
<entry>
<title>docs: userspace-api: add iommu.rst to the index file</title>
<updated>2020-10-28T17:26:10Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2020-10-27T09:51:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=de39012afa7fd119fd6387c11a6ce33590717866'/>
<id>urn:sha1:de39012afa7fd119fd6387c11a6ce33590717866</id>
<content type='text'>
There's a new uAPI doc for IOMMU. Add it to the index file.
Should address this warning:

	.../Documentation/userspace-api/iommu.rst: WARNING: document isn't included in any toctree

Fixes: d0023e3ee28d ("docs: IOMMU user API")
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
Link: https://lore.kernel.org/r/cc55219a551e29848e2282cd8939a4115067234c.1603791716.git.mchehab+huawei@kernel.org
Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>media: docs: get rid of Documentation/media/</title>
<updated>2020-04-14T08:36:50Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2020-03-10T12:57:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d29e1ef4d638a6be59a8859b4994b457bb7348c5'/>
<id>urn:sha1:d29e1ef4d638a6be59a8859b4994b457bb7348c5</id>
<content type='text'>
Now that everything got moved, we can get rid of the
old media directory.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>docs: Move the user-space ioctl() docs to userspace-api</title>
<updated>2019-10-10T17:21:54Z</updated>
<author>
<name>Jonathan Corbet</name>
</author>
<published>2019-10-03T19:02:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=049500715e7aed436c3dfac7071d7f17c18b463b'/>
<id>urn:sha1:049500715e7aed436c3dfac7071d7f17c18b463b</id>
<content type='text'>
This is strictly user-space material at this point, so put it with the
other user-space API documentation.

Signed-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;
</content>
</entry>
<entry>
<title>docs: ocxl.rst: add it to the uAPI book</title>
<updated>2019-07-15T14:03:02Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2019-06-18T14:39:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2dbc0838bcf24ca59cabc3130cf3b1d6809cdcd4'/>
<id>urn:sha1:2dbc0838bcf24ca59cabc3130cf3b1d6809cdcd4</id>
<content type='text'>
The content of this file is user-faced.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
Acked-by: Andrew Donnellan &lt;ajd@linux.ibm.com&gt;
</content>
</entry>
</feed>
