Result for 2624634713A2A04F95D4B633A9C06F84F6DF945A

Query result

Key Value
FileName./usr/bin/tcmu-runner
FileSize137768
MD5DCA01FA9310F6B4BC0749767C6D85BB7
SHA-12624634713A2A04F95D4B633A9C06F84F6DF945A
SHA-256918030ADA6D22D9AAE0BFA5F01D57EA8C75B7FF4E4E5FC3FC3A372F3B9937535
SSDEEP3072:LqCp2A/j3noVG4R/d4txw8sNPQDNo8Om:WCpx/0V3d4tx7sNY
TLSHT1E5D3386F72A549FEC1C9857086DBC6613A307840D2226A3F7964B3751E16FAE4F0F722
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
MD5CA8F72009E08C00F31AE3DD18F3E4C5A
PackageArchx86_64
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.
PackageMaintainerhttps://www.suse.com/
PackageNametcmu-runner
PackageRelease150400.1.5
PackageVersion1.5.4
SHA-1128B028D6DF130F4CE761BDA601B45CD7DFCCF56
SHA-25616AE496AE3BAE99572A6935370AF3E6DADD7490E3E8168EF0A85E9B2A44440E0