Result for F7E68DDBCCD48A29084203B0BB9A223136621AFC

Query result

Key Value
FileName./usr/bin/tcmu-runner
FileSize141856
MD50D2C86CB707469915B6F1B2C02EF3E17
SHA-1F7E68DDBCCD48A29084203B0BB9A223136621AFC
SHA-256BDEEADCED5B6DF12F7FE574D4B36FB54F298AB1FD6E9B41EEA04B377911E9CD6
SSDEEP1536:8FGK2n8+vFRsvMQCdAl5AqZ7NFLLv4Iv7tzKYDFyE/uV8JFtrbO:8F12n8i6vM0X7tzKYByEm8JFtP
TLSHT1C4D3391F72A549FCC1C9C970C9CB8666B930B481D721BB3F7594A3B40D1ABAD4B0E762
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
MD54969E8C85B7CB3C31F831E7057D28B68
PackageArchx86_64
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.
PackageNametcmu-runner
PackageRelease39.18
PackageVersion1.5.4
SHA-117AE41F0F53C8ADA6E218E0B46702A4E7E31E58D
SHA-2562DE1A3868BB579548A6D556800C64ED0490FF3D4C3218CBC9A3CF486F98D489A