Result for 633D0D16CDF45F19A1EF5EF91110D6B3C20F8380

Query result

Key Value
FileName./usr/bin/tcmu-runner
FileSize157372
MD5464161BA4DFE5740EF68127BF56A0D4D
SHA-1633D0D16CDF45F19A1EF5EF91110D6B3C20F8380
SHA-2568D8CD4D2E37CCF8277FD2836562BCF630909251EAE09A274402AC6E3404ED7AE
SSDEEP3072:ihHbN1W7v5K2oL3igDR9GaTad74rZaCqCJt9pp:cHbN1OhKr7d9Id74daxmHp
TLSHT1A2F3295AE396D8F0F3D302F51A0B932298745645C763FBB2EF4D33A868B835A5D12325
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
MD5D3E2170F8A7F91C2452B94FD27874C1E
PackageArchi586
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://bugs.opensuse.org
PackageNametcmu-runner
PackageRelease1.2
PackageVersion1.5.4
SHA-11EE163138F2BC445C6CC5E587D2D10D934C07D73
SHA-256F413EE1EF046D65DB9332058A760B60497430F590590D12668C7CED02B9E416B