BUSE icon indicating copy to clipboard operation
BUSE copied to clipboard

A block device in user space for Linux

Results 19 BUSE issues
Sort by recently updated
recently updated
newest added

This fixes build warnings on armv7l (a 32bit ARM). Also tested on x86_64 – still works, and there are no new warnings.

Additional cast buse.c to support building with C++ compiler or "-Werror=c++-compat" parameter.

1: write_all always returned a bogus 0, so it might as well return nothing, also the return value was never used for anything. 2: bytes_written should be ssize_t not int...

https://github.com/NetworkBlockDevice/nbd/blob/master/doc/proto.md I think buse uses oldstyle negotiation and the spec says server sends these five data. ``` S: 64 bits, 0x4e42444d41474943 (ASCII 'NBDMAGIC') (also known as the INIT_PASSWD) S: 64...

Hi, Currently trying to go through this code, is there any chance to add some notes maybe? or documentation? Thanks and Merry Xmas

Hello, I would like to use BUSE over ethernet like in a standard nbd protocol. It seems that it can run only in local setting a pair of local connected...

Create jobs! Guys. I have used BUSE to export a userspace block device (a SPDK defined block device) into kernel space, and it's easy to make it. But the I/O...

Currently all errors are set like this: ``` reply.error = aop->write(chunk, len, from, userdata); ``` which requires to use `ntohl` inside user `buse_operations`. I suggest to handle byte order on...

I think the only correct way of terminating BUSE-based NBD server is to disconnect the NBD device: ``` nbd-client -d /dev/nbd0 ``` It would be nice to properly handle Ctrl+C...