Result for 2D30BE1AE7BB565979450A544151D958836676B1

Query result

Key Value
FileName./usr/bin/tcmu-runner
FileSize149856
MD5FD6EF5A7502B51755AA9E8B5C1AF8A69
SHA-12D30BE1AE7BB565979450A544151D958836676B1
SHA-25689D3E454945994190A04469F913CD4AB744A7C6D9048C7420A497F602BA79CFA
SSDEEP1536:RqBMUbk/qmlP3CreVYYdpFxmhAPAIadybCeIGZ2Q/k9x9hVWXnBvWtoPkj+o:RqqUYHqrI5+sAnwy9xrVWXnBetmk+
TLSHT1ABE3F89BFA39CDDBC0F16A76511AB7B0827F7E3666905508FFACF3084832B418629570
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