Result for 9DA2130817F23C5F7F6F0753CDD20286374DA24F

Query result

Key Value
FileName./usr/lib64/tcmu-runner/handler_qcow.so
FileSize22952
MD5E7183843E7D398C94DFE83997310344E
SHA-19DA2130817F23C5F7F6F0753CDD20286374DA24F
SHA-256867C362226DDDF907E80CB88413F9947A980BE4B9FC29D590A6D83733914AC2B
SSDEEP384:hYyEoJNjxIUEnLqnhnEz05p71OOjk2Ci8NcmGkWs:hYZo1IUEunEzSp78Oo0ts
TLSHT193A22B11FE24DA07CA851370D91A8D3C7672864ABB39738226B65E3D3E5335F8B5EB40
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
MD5528F6D208F83D38423DB820AED325E4F
PackageArchriscv64
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-11BB155F321776B355AA5563697FC13F96DA58955
SHA-256451517BE931D03BAF4DF4F5893ACBF54E81302827F1A621594634F589A2148AF