Result for 6FDE32A392F6AF30A713079496EFF72F0DA6A89C

Query result

Key Value
FileName./usr/lib64/tcmu-runner/handler_qcow.so
FileSize26800
MD5F81923A1C6FDBA6543639D504436BB0D
SHA-16FDE32A392F6AF30A713079496EFF72F0DA6A89C
SHA-256D19E0C6710503704910C054C84B022BBF9D0F419BEB1B25718AF2F1AA7D483FF
SSDEEP384:xghIGru3u5ACc4NFFWUUArVx+gOsmgmLr37Cn3ZsmpgB:xgh/C3sACtNHUABx+UDm38vgB
TLSHT101C21B46B93B4E4BC0F02B7161CBD3B8A3773536BB494A0CBA6CC31D64D33649666A71
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
MD5CF55A6210FADCCFBA71FE3755CD45E76
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.
PackageNametcmu-runner
PackageRelease39.18
PackageVersion1.5.4
SHA-13DCDB2E53F50E6D7919B25C5F7702727EA5CB96F
SHA-256986327C840971DDAF55690CA602FAF4789FB1784BC03F9F6C93CEA47DC3F4F71