From: David Howells <dhowells@redhat.com> To: viro@zeniv.linux.org.uk Cc: dhowells@redhat.com, Casey Schaufler <casey@schaufler-ca.com>, Stephen Smalley <sds@tycho.nsa.gov>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, nicolas.dichtel@6wind.com, raven@themaw.net, Christian Brauner <christian@brauner.io>, keyrings@vger.kernel.org, linux-usb@vger.kernel.org, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org Subject: watch_devices(2) manpage Date: Fri, 30 Aug 2019 15:15:49 +0100 [thread overview] Message-ID: <4596.1567174549@warthog.procyon.org.uk> (raw) In-Reply-To: <156717343223.2204.15875738850129174524.stgit@warthog.procyon.org.uk> '\" t .\" Copyright (c) 2019 David Howells <dhowells@redhat.com> .\" .\" %%%LICENSE_START(VERBATIM) .\" Permission is granted to make and distribute verbatim copies of this .\" manual provided the copyright notice and this permission notice are .\" preserved on all copies. .\" .\" Permission is granted to copy and distribute modified versions of this .\" manual under the conditions for verbatim copying, provided that the .\" entire resulting derived work is distributed under the terms of a .\" permission notice identical to this one. .\" .\" Since the Linux kernel and libraries are constantly changing, this .\" manual page may be incorrect or out-of-date. The author(s) assume no .\" responsibility for errors or omissions, or for damages resulting from .\" the use of the information contained herein. The author(s) may not .\" have taken the same level of care in the production of this manual, .\" which is licensed free of charge, as they might when working .\" professionally. .\" .\" Formatted or processed versions of this manual, if unaccompanied by .\" the source, must acknowledge the copyright and authors of this work. .\" %%%LICENSE_END .\" .TH WATCH_DEVICES 2 2019-08-29 "Linux" "Linux Programmer's Manual" .SH NAME watch_devices \- Watch for global device notifications .SH SYNOPSIS .nf .B #include <linux/watch_queue.h> .br .B #include <unistd.h> .br .BI "int watch_devices(int " watch_fd ", int " watch_id ", unsigned int " flags ); .fi .PP .IR Note : There are no glibc wrappers for these system calls. .SH DESCRIPTION .PP .BR watch_devices () attaches a watch on the global device notification source to a previously opened and configured watch queue. See .BR watch_queue (7) for more information on how to set up and use those. .PP The global device notification source is provided with events from a number of sources, including block device errors and USB events. Each notification type has a specific format. .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .SS Block Device Notifications Events on block devices, such as I/O errors are posted to any watching queues. The message format is: .PP .in +4n .EX struct block_notification { struct watch_notification watch; __u64 dev; __u64 sector; }; .EE .in .PP The .I watch.type field will be set to .BR WATCH_TYPE_BLOCK_NOTIFY , the .I watch.subtype field will contain a constant that indicates the particular event that occurred and the watch_id passed to watch_devices() will be placed in .I watch.info in the ID field. .PP .I dev will contain the major and minor device numbers in .B dev_t form and .I sector will contain the first sector the notification pertains to. .PP The following events are defined: .PP .in +4n .TS lB l. NOTIFY_BLOCK_ERROR_TIMEOUT NOTIFY_BLOCK_ERROR_NO_SPACE NOTIFY_BLOCK_ERROR_RECOVERABLE_TRANSPORT NOTIFY_BLOCK_ERROR_CRITICAL_TARGET NOTIFY_BLOCK_ERROR_CRITICAL_NEXUS NOTIFY_BLOCK_ERROR_CRITICAL_MEDIUM NOTIFY_BLOCK_ERROR_PROTECTION NOTIFY_BLOCK_ERROR_KERNEL_RESOURCE NOTIFY_BLOCK_ERROR_DEVICE_RESOURCE NOTIFY_BLOCK_ERROR_IO .TE .in .PP All of which indicate error conditions. .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .SS USB Device Notifications Events on USB devices, such as I/O errors are posted to any watching queues. The message format is: .PP .in +4n .EX struct usb_notification { struct watch_notification watch; __u32 error; __u32 reserved; __u8 name_len; __u8 name[0]; }; .EE .in .PP The .I watch.type field will be set to .BR WATCH_TYPE_USB_NOTIFY , the .I watch.subtype field will contain a constant that indicates the particular event that occurred and the watch_id passed to watch_devices() will be placed in .I watch.info in the ID field. .PP .IR name " and " name_len indicates the textual name of the USB device that originated the notification. The name will be truncated to .B USB_NOTIFICATION_MAX_NAME_LEN if it is longer than that. .PP The following subtypes are currently defined: .TP .B NOTIFY_USB_DEVICE_ADD A new USB device has been plugged in. .TP .B NOTIFY_USB_DEVICE_REMOVE A USB device has been unplugged. .TP .B NOTIFY_USB_BUS_ADD A new USB bus is now available. .TP .B NOTIFY_USB_BUS_REMOVE A USB bus has been removed. .TP .B NOTIFY_USB_DEVICE_RESET A USB device has been reset. .TP .B NOTIFY_USB_DEVICE_ERROR A USB device has generated an error; a suitable error code will have been placed in .IR error . .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .SH RETURN VALUE On success, the function returns 0. On error, \-1 is returned, and .I errno is set appropriately. .SH ERRORS The following errors may be returned: .TP .B EBADF .I watch_fd is an invalid file descriptor. .TP .B EBADSLT The watch does not exist and so cannot be removed. .TP .B EBUSY The source is already attached to the watch device instance specified by .I watch_fd and so cannot be added. .TP .B EINVAL .I watch_fd does not refer to a watch_queue device file. .TP .B EINVAL .IR watch_fd " or " watch_id is out of range. .TP .B EINVAL Unsupported .I flags set. .TP .B ENOMEM Insufficient memory available to allocate a watch record. .TP .B EPERM The caller does not have the required privileges. .SH CONFORMING TO These functions are Linux-specific and should not be used in programs intended to be portable. .SH VERSIONS The notification queue driver first appeared in v??? of the Linux kernel. .SH NOTES Glibc does not (yet) provide a wrapper for the .BR watch_devices "()" system call; call it using .BR syscall (2). .SH SEE ALSO .BR watch_queue (7)
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com> To: viro@zeniv.linux.org.uk Cc: dhowells@redhat.com, Casey Schaufler <casey@schaufler-ca.com>, Stephen Smalley <sds@tycho.nsa.gov>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, nicolas.dichtel@6wind.com, raven@themaw.net, Christian Brauner <christian@brauner.io>, keyrings@vger.kernel.org, linux-usb@vger.kernel.org, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org Subject: watch_devices(2) manpage Date: Fri, 30 Aug 2019 14:15:49 +0000 [thread overview] Message-ID: <4596.1567174549@warthog.procyon.org.uk> (raw) In-Reply-To: <156717343223.2204.15875738850129174524.stgit@warthog.procyon.org.uk> '\" t .\" Copyright (c) 2019 David Howells <dhowells@redhat.com> .\" .\" %%%LICENSE_START(VERBATIM) .\" Permission is granted to make and distribute verbatim copies of this .\" manual provided the copyright notice and this permission notice are .\" preserved on all copies. .\" .\" Permission is granted to copy and distribute modified versions of this .\" manual under the conditions for verbatim copying, provided that the .\" entire resulting derived work is distributed under the terms of a .\" permission notice identical to this one. .\" .\" Since the Linux kernel and libraries are constantly changing, this .\" manual page may be incorrect or out-of-date. The author(s) assume no .\" responsibility for errors or omissions, or for damages resulting from .\" the use of the information contained herein. The author(s) may not .\" have taken the same level of care in the production of this manual, .\" which is licensed free of charge, as they might when working .\" professionally. .\" .\" Formatted or processed versions of this manual, if unaccompanied by .\" the source, must acknowledge the copyright and authors of this work. .\" %%%LICENSE_END .\" .TH WATCH_DEVICES 2 2019-08-29 "Linux" "Linux Programmer's Manual" .SH NAME watch_devices \- Watch for global device notifications .SH SYNOPSIS .nf .B #include <linux/watch_queue.h> .br .B #include <unistd.h> .br .BI "int watch_devices(int " watch_fd ", int " watch_id ", unsigned int " flags ); .fi .PP .IR Note : There are no glibc wrappers for these system calls. .SH DESCRIPTION .PP .BR watch_devices () attaches a watch on the global device notification source to a previously opened and configured watch queue. See .BR watch_queue (7) for more information on how to set up and use those. .PP The global device notification source is provided with events from a number of sources, including block device errors and USB events. Each notification type has a specific format. .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .SS Block Device Notifications Events on block devices, such as I/O errors are posted to any watching queues. The message format is: .PP .in +4n .EX struct block_notification { struct watch_notification watch; __u64 dev; __u64 sector; }; .EE .in .PP The .I watch.type field will be set to .BR WATCH_TYPE_BLOCK_NOTIFY , the .I watch.subtype field will contain a constant that indicates the particular event that occurred and the watch_id passed to watch_devices() will be placed in .I watch.info in the ID field. .PP .I dev will contain the major and minor device numbers in .B dev_t form and .I sector will contain the first sector the notification pertains to. .PP The following events are defined: .PP .in +4n .TS lB l. NOTIFY_BLOCK_ERROR_TIMEOUT NOTIFY_BLOCK_ERROR_NO_SPACE NOTIFY_BLOCK_ERROR_RECOVERABLE_TRANSPORT NOTIFY_BLOCK_ERROR_CRITICAL_TARGET NOTIFY_BLOCK_ERROR_CRITICAL_NEXUS NOTIFY_BLOCK_ERROR_CRITICAL_MEDIUM NOTIFY_BLOCK_ERROR_PROTECTION NOTIFY_BLOCK_ERROR_KERNEL_RESOURCE NOTIFY_BLOCK_ERROR_DEVICE_RESOURCE NOTIFY_BLOCK_ERROR_IO .TE .in .PP All of which indicate error conditions. .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .SS USB Device Notifications Events on USB devices, such as I/O errors are posted to any watching queues. The message format is: .PP .in +4n .EX struct usb_notification { struct watch_notification watch; __u32 error; __u32 reserved; __u8 name_len; __u8 name[0]; }; .EE .in .PP The .I watch.type field will be set to .BR WATCH_TYPE_USB_NOTIFY , the .I watch.subtype field will contain a constant that indicates the particular event that occurred and the watch_id passed to watch_devices() will be placed in .I watch.info in the ID field. .PP .IR name " and " name_len indicates the textual name of the USB device that originated the notification. The name will be truncated to .B USB_NOTIFICATION_MAX_NAME_LEN if it is longer than that. .PP The following subtypes are currently defined: .TP .B NOTIFY_USB_DEVICE_ADD A new USB device has been plugged in. .TP .B NOTIFY_USB_DEVICE_REMOVE A USB device has been unplugged. .TP .B NOTIFY_USB_BUS_ADD A new USB bus is now available. .TP .B NOTIFY_USB_BUS_REMOVE A USB bus has been removed. .TP .B NOTIFY_USB_DEVICE_RESET A USB device has been reset. .TP .B NOTIFY_USB_DEVICE_ERROR A USB device has generated an error; a suitable error code will have been placed in .IR error . .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" .SH RETURN VALUE On success, the function returns 0. On error, \-1 is returned, and .I errno is set appropriately. .SH ERRORS The following errors may be returned: .TP .B EBADF .I watch_fd is an invalid file descriptor. .TP .B EBADSLT The watch does not exist and so cannot be removed. .TP .B EBUSY The source is already attached to the watch device instance specified by .I watch_fd and so cannot be added. .TP .B EINVAL .I watch_fd does not refer to a watch_queue device file. .TP .B EINVAL .IR watch_fd " or " watch_id is out of range. .TP .B EINVAL Unsupported .I flags set. .TP .B ENOMEM Insufficient memory available to allocate a watch record. .TP .B EPERM The caller does not have the required privileges. .SH CONFORMING TO These functions are Linux-specific and should not be used in programs intended to be portable. .SH VERSIONS The notification queue driver first appeared in v??? of the Linux kernel. .SH NOTES Glibc does not (yet) provide a wrapper for the .BR watch_devices "()" system call; call it using .BR syscall (2). .SH SEE ALSO .BR watch_queue (7)
next prev parent reply other threads:[~2019-08-30 14:15 UTC|newest] Thread overview: 234+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20190903085706.7700-1-hdanton@sina.com> 2019-08-30 13:57 ` [PATCH 00/11] Keyrings, Block and USB notifications [ver #7] David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` [PATCH 01/11] uapi: General notification ring definitions " David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` [PATCH 02/11] security: Add hooks to rule on setting a watch " David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` [PATCH 03/11] security: Add a hook for the point of notification insertion " David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` [PATCH 04/11] General notification queue with user mmap()'able ring buffer " David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` [PATCH 05/11] keys: Add a notification facility " David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:57 ` David Howells 2019-08-30 13:58 ` [PATCH 06/11] Add a general, global device notification watch list " David Howells 2019-08-30 13:58 ` David Howells 2019-08-30 13:58 ` David Howells 2019-09-03 8:34 ` Yoshihiro Shimoda 2019-09-03 8:34 ` Yoshihiro Shimoda 2019-09-03 8:34 ` Yoshihiro Shimoda 2019-09-03 16:41 ` David Howells 2019-09-03 16:41 ` David Howells 2019-09-03 16:41 ` David Howells 2019-08-30 13:58 ` [PATCH 07/11] block: Add block layer notifications " David Howells 2019-08-30 13:58 ` David Howells 2019-08-30 13:58 ` David Howells 2019-08-30 13:58 ` [PATCH 08/11] usb: Add USB subsystem " David Howells 2019-08-30 13:58 ` David Howells 2019-08-30 13:58 ` David Howells 2019-09-03 8:53 ` Yoshihiro Shimoda 2019-09-03 8:53 ` Yoshihiro Shimoda 2019-09-03 8:53 ` Yoshihiro Shimoda 2019-09-03 9:37 ` Greg Kroah-Hartman 2019-09-03 9:37 ` Greg Kroah-Hartman 2019-09-03 9:37 ` Greg Kroah-Hartman 2019-09-04 1:53 ` Yoshihiro Shimoda 2019-09-04 1:53 ` Yoshihiro Shimoda 2019-09-04 1:53 ` Yoshihiro Shimoda 2019-09-03 12:51 ` Guenter Roeck 2019-09-03 12:51 ` Guenter Roeck 2019-09-03 16:07 ` David Howells 2019-09-03 16:07 ` David Howells 2019-09-03 16:12 ` Guenter Roeck 2019-09-03 16:12 ` Guenter Roeck 2019-09-03 16:29 ` David Howells 2019-09-03 16:29 ` David Howells 2019-09-03 17:06 ` Alan Stern 2019-09-03 17:06 ` Alan Stern 2019-09-03 17:06 ` Alan Stern 2019-09-03 17:17 ` Alan Stern 2019-09-03 17:17 ` Alan Stern 2019-09-03 17:17 ` Alan Stern 2019-09-04 15:17 ` David Howells 2019-09-04 15:17 ` David Howells 2019-08-30 13:58 ` [PATCH 09/11] Add sample notification program " David Howells 2019-08-30 13:58 ` David Howells 2019-08-30 13:58 ` David Howells 2019-08-30 13:58 ` [PATCH 10/11] selinux: Implement the watch_key security hook " David Howells 2019-08-30 13:58 ` David Howells 2019-08-30 13:58 ` David Howells 2019-08-30 14:15 ` Stephen Smalley 2019-08-30 14:15 ` Stephen Smalley 2019-08-30 14:23 ` David Howells 2019-08-30 14:23 ` David Howells 2019-08-30 14:41 ` David Howells 2019-08-30 14:41 ` David Howells 2019-08-30 15:41 ` Stephen Smalley 2019-08-30 15:41 ` Stephen Smalley 2019-08-30 13:58 ` [PATCH 11/11] smack: Implement the watch_key and post_notification hooks [untested] " David Howells 2019-08-30 13:58 ` David Howells 2019-08-30 13:58 ` David Howells 2019-09-03 15:20 ` Casey Schaufler 2019-09-03 15:20 ` Casey Schaufler 2019-09-03 15:41 ` David Howells 2019-09-03 15:41 ` David Howells 2019-09-03 17:40 ` Casey Schaufler 2019-09-03 17:40 ` Casey Schaufler 2019-09-03 18:06 ` David Howells 2019-09-03 18:06 ` David Howells 2019-09-03 22:16 ` Casey Schaufler 2019-09-03 22:16 ` Casey Schaufler 2019-09-03 22:39 ` David Howells 2019-09-03 22:39 ` David Howells 2019-09-04 12:08 ` David Howells 2019-09-04 12:08 ` David Howells 2019-09-04 14:56 ` Casey Schaufler 2019-09-04 14:56 ` Casey Schaufler 2019-08-30 14:15 ` watch_queue(7) manpage David Howells 2019-08-30 14:15 ` David Howells 2019-08-30 14:15 ` David Howells 2019-08-30 14:15 ` David Howells [this message] 2019-08-30 14:15 ` watch_devices(2) manpage David Howells 2019-08-30 14:16 ` keyctl_watch_key.3 manpage David Howells 2019-08-30 14:16 ` David Howells 2019-08-30 22:09 ` [PATCH 00/11] Keyrings, Block and USB notifications [ver #7] Casey Schaufler 2019-08-30 22:09 ` Casey Schaufler 2019-09-02 12:39 ` David Howells 2019-09-02 12:39 ` David Howells 2019-09-02 13:26 ` David Howells 2019-09-02 13:26 ` David Howells 2019-09-03 16:06 ` [PATCH 04/11] General notification queue with user mmap()'able ring buffer " David Howells 2019-09-03 16:06 ` David Howells 2019-09-03 16:37 ` David Howells 2019-09-03 16:37 ` David Howells 2019-09-04 22:15 [PATCH 00/11] Keyrings, Block and USB notifications [ver #8] David Howells 2019-09-04 22:15 ` David Howells 2019-09-04 22:15 ` David Howells 2019-09-04 22:15 ` [PATCH 01/11] uapi: General notification ring definitions " David Howells 2019-09-04 22:15 ` David Howells 2019-09-04 22:15 ` David Howells 2019-09-04 22:16 ` [PATCH 02/11] security: Add hooks to rule on setting a watch " David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` [PATCH 03/11] security: Add a hook for the point of notification insertion " David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` [PATCH 04/11] General notification queue with user mmap()'able ring buffer " David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` [PATCH 05/11] keys: Add a notification facility " David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` [PATCH 06/11] Add a general, global device notification watch list " David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` [PATCH 07/11] block: Add block layer notifications " David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` [PATCH 08/11] usb: Add USB subsystem " David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:16 ` David Howells 2019-09-04 22:17 ` [PATCH 09/11] Add sample notification program " David Howells 2019-09-04 22:17 ` David Howells 2019-09-04 22:17 ` David Howells 2019-09-04 22:17 ` [PATCH 10/11] selinux: Implement the watch_key security hook " David Howells 2019-09-04 22:17 ` David Howells 2019-09-04 22:17 ` David Howells 2019-09-04 22:17 ` [PATCH 11/11] smack: Implement the watch_key and post_notification hooks " David Howells 2019-09-04 22:17 ` David Howells 2019-09-04 22:17 ` David Howells 2019-09-04 22:28 ` [PATCH 00/11] Keyrings, Block and USB notifications " Linus Torvalds 2019-09-04 22:28 ` Linus Torvalds 2019-09-05 17:01 ` Why add the general notification queue and its sources David Howells 2019-09-05 17:01 ` David Howells 2019-09-05 17:19 ` Linus Torvalds 2019-09-05 17:19 ` Linus Torvalds 2019-09-05 18:32 ` Ray Strode 2019-09-05 18:32 ` Ray Strode 2019-09-05 18:32 ` Ray Strode 2019-09-05 20:39 ` Linus Torvalds 2019-09-05 20:39 ` Linus Torvalds 2019-09-06 19:32 ` Ray Strode 2019-09-06 19:32 ` Ray Strode 2019-09-06 19:41 ` Ray Strode 2019-09-06 19:41 ` Ray Strode 2019-09-06 19:53 ` Robbie Harwood 2019-09-06 19:53 ` Robbie Harwood 2019-09-06 19:53 ` Robbie Harwood 2019-09-05 21:32 ` David Howells 2019-09-05 21:32 ` David Howells 2019-09-05 22:08 ` Linus Torvalds 2019-09-05 22:08 ` Linus Torvalds 2019-09-05 23:18 ` David Howells 2019-09-05 23:18 ` David Howells 2019-09-06 0:07 ` Linus Torvalds 2019-09-06 0:07 ` Linus Torvalds 2019-09-06 10:09 ` David Howells 2019-09-06 10:09 ` David Howells 2019-09-06 15:35 ` Linus Torvalds 2019-09-06 15:35 ` Linus Torvalds 2019-09-06 15:53 ` Linus Torvalds 2019-09-06 15:53 ` Linus Torvalds 2019-09-06 16:12 ` Steven Whitehouse 2019-09-06 16:12 ` Steven Whitehouse 2019-09-06 17:07 ` Linus Torvalds 2019-09-06 17:07 ` Linus Torvalds 2019-09-06 17:14 ` Linus Torvalds 2019-09-06 17:14 ` Linus Torvalds 2019-09-06 21:19 ` David Howells 2019-09-06 21:19 ` David Howells 2019-09-06 17:14 ` Andy Lutomirski 2019-09-06 17:14 ` Andy Lutomirski 2019-09-05 18:37 ` Steven Whitehouse 2019-09-05 18:37 ` Steven Whitehouse 2019-09-05 18:51 ` Ray Strode 2019-09-05 18:51 ` Ray Strode 2019-09-05 20:09 ` David Lehman 2019-09-05 20:09 ` David Lehman 2019-09-05 18:33 ` Greg Kroah-Hartman 2019-09-05 18:33 ` Greg Kroah-Hartman -- strict thread matches above, loose matches on Subject: below -- 2019-08-29 18:29 [PATCH 00/11] Keyrings, Block and USB notifications [ver #6] David Howells 2019-08-29 18:29 ` David Howells 2019-08-29 18:29 ` David Howells 2019-08-29 18:29 ` [PATCH 01/11] uapi: General notification ring definitions " David Howells 2019-08-29 18:29 ` David Howells 2019-08-29 18:29 ` David Howells 2019-08-29 18:30 ` [PATCH 02/11] security: Add hooks to rule on setting a watch " David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` [PATCH 03/11] security: Add a hook for the point of notification insertion " David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` [PATCH 04/11] General notification queue with user mmap()'able ring buffer " David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` [PATCH 05/11] keys: Add a notification facility " David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` [PATCH 06/11] Add a general, global device notification watch list " David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` [PATCH 07/11] block: Add block layer notifications " David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:30 ` David Howells 2019-08-29 18:31 ` [PATCH 08/11] usb: Add USB subsystem " David Howells 2019-08-29 18:31 ` David Howells 2019-08-29 18:31 ` David Howells 2019-08-29 18:31 ` [PATCH 09/11] Add sample notification program " David Howells 2019-08-29 18:31 ` David Howells 2019-08-29 18:31 ` David Howells 2019-08-29 18:31 ` [PATCH 10/11] selinux: Implement the watch_key security hook " David Howells 2019-08-29 18:31 ` David Howells 2019-08-29 18:31 ` David Howells 2019-08-29 18:44 ` Stephen Smalley 2019-08-29 18:44 ` Stephen Smalley 2019-08-29 19:11 ` David Howells 2019-08-29 19:11 ` David Howells 2019-08-29 18:31 ` [PATCH 11/11] smack: Implement the watch_key and post_notification hooks [untested] " David Howells 2019-08-29 18:31 ` David Howells 2019-08-29 18:31 ` David Howells
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4596.1567174549@warthog.procyon.org.uk \ --to=dhowells@redhat.com \ --cc=casey@schaufler-ca.com \ --cc=christian@brauner.io \ --cc=gregkh@linuxfoundation.org \ --cc=keyrings@vger.kernel.org \ --cc=linux-api@vger.kernel.org \ --cc=linux-block@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=linux-usb@vger.kernel.org \ --cc=nicolas.dichtel@6wind.com \ --cc=raven@themaw.net \ --cc=sds@tycho.nsa.gov \ --cc=viro@zeniv.linux.org.uk \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.