Result for 6922F7F25ED22631DD3AFB66234BDB2595A1A972

Query result

Key Value
FileName./usr/lib/tcmu-runner/handler_qcow.so
FileSize26172
MD5419D34A732336146374479B034E7E8D2
SHA-16922F7F25ED22631DD3AFB66234BDB2595A1A972
SHA-256A700FF3CFEF7EC08A923F3C197AE174B8301C74D54CC6C018A64B51FB0B09BAB
SSDEEP384:KH11FUufXDy9D7O0zSUijVLT3w+7HhycY7vVxmVYIK8YP8HMm9U:eSO+DffCv3w+7HFVdKDAU
TLSHT1C6C21712E1129B7BC2D1C231B98E026C33F353B6D7CBB3564A2599317AEA66D4C36B04
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
MD5647F15344273245DC383C338A2AE80E6
PackageArcharmv7hl
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-14FB6260FED79A4D4D100271AFB2005FFE92961F0
SHA-256AEB58278F13DA10B97953C15806ED5D86A3BA68A33C7240CBD59ACF75138DEF7