Result for 3D0B57EEFDB2E3D13D63FD79DF4C896483D44948

Query result

Key Value
FileName./usr/bin/tcmu-runner
FileSize123720
MD594F77E65F7737F3A8113C6F69A00D334
SHA-13D0B57EEFDB2E3D13D63FD79DF4C896483D44948
SHA-25662DAFB1DDC426924CE32E2ACECCFE484CE3A75CD85A01608480742DBEA5340B7
SSDEEP1536:HNNIHokxGtJrhOQ+jK7yKo8w6hDBrz08LJr7/EMWuDwLtCzwxjKrk+hgnB2PRNq:EHxgjppZA6hDec3/loLtCzwxjQk+hg
TLSHT19BC31826F458E98ACBC86171DC57CB54723B85DA43A07B6AAB30BF6C4C4578DDE4A3C0
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