summaryrefslogtreecommitdiff
path: root/Documentation/usb/mass-storage.rst
diff options
context:
space:
mode:
authorMaxim Devaev <mdevaev@gmail.com>2022-07-11 13:29:57 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-07-14 16:06:42 +0200
commit421c8d9a20da92deed2dac227e7ebdee7eb3e88f (patch)
tree9dd7b02019b4500836d798ac73042c36735cfe6f /Documentation/usb/mass-storage.rst
parent8097cf2fb3b2205257f1c76f4808e3398d66b6d9 (diff)
usb: gadget: f_mass_storage: forced_eject attribute
It allows to reset prevent_medium_removal flag and "eject" the image. This can be useful to free the drive from a hunging host or if the host continues to use the drive even after unmounting (Linux does this). It's also a bit like using an unfolded paperclip on an optical drive. Previously, the undocumented method of sending SIGUSR1 to a special "file-storage" kernel thread could be used for these purposes, but when using multiple storages there was no way to distinguish one from the other, so we had to send a signal to everyone. Reviewed-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Maxim Devaev <mdevaev@gmail.com> Link: https://lore.kernel.org/r/20220711102956.19642-1-mdevaev@gmail.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/usb/mass-storage.rst')
-rw-r--r--Documentation/usb/mass-storage.rst9
1 files changed, 9 insertions, 0 deletions
diff --git a/Documentation/usb/mass-storage.rst b/Documentation/usb/mass-storage.rst
index d181b47c3cb6..f399ec631599 100644
--- a/Documentation/usb/mass-storage.rst
+++ b/Documentation/usb/mass-storage.rst
@@ -181,6 +181,15 @@ sysfs entries
Reflects the state of nofua flag for given logical unit. It can
be read and written.
+ - forced_eject
+
+ When written into, it causes the backing file to be forcibly
+ detached from the LUN, regardless of whether the host has allowed
+ it. The content doesn't matter, any non-zero number of bytes
+ written will result in ejection.
+
+ Can not be read.
+
Other then those, as usual, the values of module parameters can be
read from /sys/module/g_mass_storage/parameters/* files.