Result for 3CEC5A3202FA80056E1856481371BF632FA5DD62

Query result

Key Value
FileName./usr/bin/tcmu-runner
FileSize149864
MD52955E44C4E3BB4F54D9B810E753ED255
SHA-13CEC5A3202FA80056E1856481371BF632FA5DD62
SHA-2565CAE4EB81A5354FE0000DB772064C7004C15EB63F27D968A89092F0FB8C13155
SSDEEP3072:gxq/I0CzkH5tXSJFh5oySiZjEYAag79FQVYOnBwoB4:x/IvzkHaF+9FQWOn6oB
TLSHT1B9E31D4BFA3ACE9AD4F0AAB6910A77F1827B3E3566C15544BFACF3080C727418635671
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD59CF801849A9954F553CCB220D65BE805
PackageArchs390x
PackageDescriptionLIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel. The TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each userspace handler having to write boilerplate code. tcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called "TCMU handlers". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like.
PackageMaintainerhttps://www.suse.com/
PackageNametcmu-runner
PackageRelease150400.1.5
PackageVersion1.5.4
SHA-124D50E5B09B937F2BC0B57468B86D78CC1A01451
SHA-2567137B8C93D0956F0A84B92ED6B7969BCA296656801D9CB592E06AF31E3727474