similar to: [klibc:master] losetup: Fix char signedness mismatches with <linux/loop.h>

hello hpa, please review this unsorted patch queue, as I wasn't sure about them they didn't land yet in todays pull request. thanks max git clone git://git.debian.org/users/maks/klibc.git test Thomas B?chler (1): klcc: compile shared by default jeremy buisson (1): [klibc] sparc64: fix bad 32 bits socket syscalls maximilian attems (1): [klibc] add losetup utils the

Commit-ID: 209676c9a3d057c0eba48f633eb541b17c7d1eba Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=209676c9a3d057c0eba48f633eb541b17c7d1eba Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 5 Nov 2019 00:33:37 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 19:55:37 +0000 [klibc] losetup: Delete fallbacks to

linux/loop.h header is exported by linux, for userspace to consume. This would prevent issues with struct sizes incompatibilities. References: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184 Signed-off-by: Michael Hudson-Doyle <michael.hudson at ubuntu.com> Signed-off-by: Adam Conrad <adconrad at ubuntu.com> Signed-off-by: Dimitri John Ledkov <xnox at ubuntu.com>

Commit-ID: 547b7cf241d4bcf518759d06cff694b9738c57b0 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=547b7cf241d4bcf518759d06cff694b9738c57b0 Author: Dimitri John Ledkov <xnox at ubuntu.com> AuthorDate: Thu, 31 Oct 2019 15:59:02 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 00:42:26 +0000 [klibc] loop: switch to

Otherwise, stack can be corrupted resulting in incorrect runtime behaviour. For example, overriding argc from main(). References: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184 Signed-off-by: Michael Hudson-Doyle <michael.hudson at ubuntu.com> Signed-off-by: Adam Conrad <adconrad at ubuntu.com> Signed-off-by: Dimitri John Ledkov <xnox at ubuntu.com> ---

From: Karel Zak <kzak at redhat.com> ported to klibc losetup version from util-linux 108591d2b7860ca0b8d27d114bed1e504a31fa72, also add -h option. -maks Reported-by: Kamalesh Babulal <kamalesh at linux.vnet.ibm.com> Signed-off-by: Karel Zak <kzak at redhat.com> Signed-off-by: maximilian attems <max at stro.at> --- Other patches might be useful too, that one just

The structure definition in the header, does not match the kernel's definition (on most architectures) which leads to undefined behaviour. References: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184 Signed-off-by: Michael Hudson-Doyle <michael.hudson at ubuntu.com> Signed-off-by: Adam Conrad <adconrad at ubuntu.com> Signed-off-by: Dimitri John Ledkov <xnox at

Hi, I have a legacy AES excrypted file system with a 256 key size. RHEL kernel is cryptoloop enabled but the losetup package is not. It needs additional patch. Does anybody have a patched losetup rpm I could use? Thank you! A. Georgiev

I have problem with smbmount and losetup working together. The data seems to be corrupted. Description: I have an NT4 server with a share. On my linux box i use smbmount to mount the share. I have created a big file on the share and use losetup to configure a loop-back device on which i try to create/use a filesystem. It seems to work at first with ext2fs, but after copying some files to the

Commit-ID: 333ef3af1dcef61a6bc5dba531453e5e0cb27da1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=333ef3af1dcef61a6bc5dba531453e5e0cb27da1 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 5 Nov 2019 19:52:19 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 20:03:26 +0000 [klibc] losetup: Use

Hi, I have Xen 3.3.1 dom0 on Debian with 2.6.26-2-xen-amd64 kernel and I had to "xm destroy" my domU. Now when I try to start it again it fails like this: # xm list | grep n39 # # xm create -c /xen/conf/n39 Using config file "/xen/conf/n39". ROOT xen1:~> Error: Device 4 (vbd) could not be connected. losetup -r /dev/loop1 /xen/iso/amd64-netbsd-6.iso failed # losetup -a

Hi, I wanted to create a new btrfs fs for my backups. When trying to mkfs.btrfs for that device, I''m getting "error checking /dev/loop2 mount status" With strace I see where the problem is: lstat("/dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO939201JX160AGN-par", 0x7fffa30b3cf0) = -1 ENOENT (No such file or directory) The problem is there is something missing