Result for 583A1A0DDCD5B70ACD90A816F134CBF637EAC666

Query result

Key Value
FileName./usr/bin/tcmu-runner
FileSize120508
MD5E8EDDE5E511004EBDEC13D907E8E4F2E
SHA-1583A1A0DDCD5B70ACD90A816F134CBF637EAC666
SHA-256A538157B0F8A533E25801200367F8A0BC85C7437D66D8C3697D4DA3DA5FEF03C
SSDEEP3072:AFHJz7nwpJAPu+s0xyjQk8ozv+80U7jnzWeKU/KaU:AFHJz7wpJAP65zg8qvUyaU
TLSHT1A6C32A9BF48A8B67C5C203B577590734313357F2C3DA3322C518E7342E6AA9F852A766
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