config NFSD tristate "NFS server support" depends on INET depends on FILE_LOCKING select LOCKD select SUNRPC select EXPORTFS select NFS_ACL_SUPPORT if NFSD_V2_ACL depends on MULTIUSER help Choose Y here if you want to allow other computers to access files residing on this system using Sun's Network File System protocol. To compile the NFS server support as a module, choose M here: the module will be called nfsd. You may choose to use a user-space NFS server instead, in which case you can choose N here. To export local file systems using NFS, you also need to install user space programs which can be found in the Linux nfs-utils package, available from http://linux-nfs.org/. More detail about the Linux NFS server implementation is available via the exports(5) man page. Below you can choose which versions of the NFS protocol are available to clients mounting the NFS server on this system. Support for NFS version 2 (RFC 1094) is always available when CONFIG_NFSD is selected. If unsure, say N. config NFSD_V2_ACL bool depends on NFSD config NFSD_V3 bool "NFS server support for NFS version 3" depends on NFSD help This option enables support in your system's NFS server for version 3 of the NFS protocol (RFC 1813). If unsure, say Y. config NFSD_V3_ACL bool "NFS server support for the NFSv3 ACL protocol extension" depends on NFSD_V3 select NFSD_V2_ACL help Solaris NFS servers support an auxiliary NFSv3 ACL protocol that never became an official part of the NFS version 3 protocol. This protocol extension allows applications on NFS clients to manipulate POSIX Access Control Lists on files residing on NFS servers. NFS servers enforce POSIX ACLs on local files whether this protocol is available or not. This option enables support in your system's NFS server for the NFSv3 ACL protocol extension allowing NFS clients to manipulate POSIX ACLs on files exported by your system's NFS server. NFS clients which support the Solaris NFSv3 ACL protocol can then access and modify ACLs on your NFS server. To store ACLs on your NFS server, you also need to enable ACL- related CONFIG options for your local file systems of choice. If unsure, say N. config NFSD_V4 bool "NFS server support for NFS version 4" depends on NFSD && PROC_FS select NFSD_V3 select FS_POSIX_ACL select SUNRPC_GSS select CRYPTO select GRACE_PERIOD help This option enables support in your system's NFS server for version 4 of the NFS protocol (RFC 3530). To export files using NFSv4, you need to install additional user space programs which can be found in the Linux nfs-utils package, available from http://linux-nfs.org/. If unsure, say N. config NFSD_PNFS bool config NFSD_BLOCKLAYOUT bool "NFSv4.1 server support for pNFS block layouts" depends on NFSD_V4 && BLOCK select NFSD_PNFS select EXPORTFS_BLOCK_OPS help This option enables support for the exporting pNFS block layouts in the kernel's NFS server. The pNFS block layout enables NFS clients to directly perform I/O to block devices accesible to both the server and the clients. See RFC 5663 for more details. If unsure, say N. config NFSD_SCSILAYOUT bool "NFSv4.1 server support for pNFS SCSI layouts" depends on NFSD_V4 && BLOCK select NFSD_PNFS select EXPORTFS_BLOCK_OPS help This option enables support for the exporting pNFS SCSI layouts in the kernel's NFS server. The pNFS SCSI layout enables NFS clients to directly perform I/O to SCSI devices accesible to both the server and the clients. See draft-ietf-nfsv4-scsi-layout for more details. If unsure, say N. config NFSD_FLEXFILELAYOUT bool "NFSv4.1 server support for pNFS Flex File layouts" depends on NFSD_V4 select NFSD_PNFS help This option enables support for the exporting pNFS Flex File layouts in the kernel's NFS server. The pNFS Flex File layout enables NFS clients to directly perform I/O to NFSv3 devices accesible to both the server and the clients. See draft-ietf-nfsv4-flex-files for more details. Warning, this server implements the bare minimum functionality to be a flex file server - it is for testing the client, not for use in production. If unsure, say N. config NFSD_V4_SECURITY_LABEL bool "Provide Security Label support for NFSv4 server" depends on NFSD_V4 && SECURITY help Say Y here if you want enable fine-grained security label attribute support for NFS version 4. Security labels allow security modules like SELinux and Smack to label files to facilitate enforcement of their policies. Without this an NFSv4 mount will have the same label on each file. If you do not wish to enable fine-grained security labels SELinux or Smack policies on NFSv4 files, say N. config NFSD_FAULT_INJECTION bool "NFS server manual fault injection" depends on NFSD_V4 && DEBUG_KERNEL && DEBUG_FS help This option enables support for manually injecting faults into the NFS server. This is intended to be used for testing error recovery on the NFS client. If unsure, say N. >2017-01-17 16:00:48 +0000 committerThomas Gleixner <tglx@linutronix.de>2017-01-30 15:18:56 +0100 commit08d85f3ea99f1eeafc4e8507936190e86a16ee8c (patch) tree410bb1acd0cd7dcfaad37ae7b63ff243b7fa4bee /sound/usb/line6/Kconfig parent566cf877a1fcb6d6dc0126b076aad062054c2637 (diff)
irqdomain: Avoid activating interrupts more than once
Since commit f3b0946d629c ("genirq/msi: Make sure PCI MSIs are activated early"), we can end-up activating a PCI/MSI twice (once at allocation time, and once at startup time). This is normally of no consequences, except that there is some HW out there that may misbehave if activate is used more than once (the GICv3 ITS, for example, uses the activate callback to issue the MAPVI command, and the architecture spec says that "If there is an existing mapping for the EventID-DeviceID combination, behavior is UNPREDICTABLE"). While this could be worked around in each individual driver, it may make more sense to tackle the issue at the core level. In order to avoid getting in that situation, let's have a per-interrupt flag to remember if we have already activated that interrupt or not. Fixes: f3b0946d629c ("genirq/msi: Make sure PCI MSIs are activated early") Reported-and-tested-by: Andre Przywara <andre.przywara@arm.com> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com> Cc: stable@vger.kernel.org Link: http://lkml.kernel.org/r/1484668848-24361-1-git-send-email-marc.zyngier@arm.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'sound/usb/line6/Kconfig')