diff options
author | Matthew R. Ochs <mrochs@linux.vnet.ibm.com> | 2016-08-09 18:39:52 -0500 |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2016-08-23 22:23:41 -0400 |
commit | cd34af40a09c678abad36304eb68e1774640e908 (patch) | |
tree | d376d13d6ff7304be180160b1ad63c5556f7577c /crypto/asymmetric_keys/asymmetric_keys.h | |
parent | 888baf069f49529f33c0b1dfb0fc4811dc0ca1d2 (diff) |
scsi: cxlflash: Transition to application close model
Caching the adapter file descriptor and performing a close on behalf of
an application is a poor design. This is due to the fact that once a
file descriptor in installed, it is free to be altered without the
knowledge of the cxlflash driver. This can lead to inconsistencies
between the application and kernel. Furthermore, the nature of the
former design is more exploitable and thus should be abandoned.
To support applications performing a close on the adapter file that is
associated with a context, a new flag is introduced to the user API to
indicate to applications that they are responsible for the close
following the cleanup (detach) of a context. The documentation is also
updated to reflect this change in behavior.
Inspired-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Matthew R. Ochs <mrochs@linux.vnet.ibm.com>
Acked-by: Manoj N. Kumar <manoj@linux.vnet.ibm.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'crypto/asymmetric_keys/asymmetric_keys.h')
0 files changed, 0 insertions, 0 deletions