delta/systemd.git/src/basic/missing_loop.h, branch main github.com: systemd/systemd.git basic/missing_loop.h: fix missing lo_flags LO_FLAGS_DIRECT_IO 2022-09-08T17:46:19+00:00 Guillaume W. Bres guillaume.bressaix@gmail.com 2022-09-08T13:54:57+00:00 b3fe33ff52ece458a5b990a4a68d59aef7cae10b 






basic/missing: move BLKGETDISKSEQ to missing_fs.h
2022-04-01T06:13:18+00:00

Yu Watanabe
watanabe.yu+github@gmail.com

2022-03-30T18:23:33+00:00

2076612f843a2276207df34d2f6b6efbadfc4d21

As it is defined at linux/fs.h.





As it is defined at linux/fs.h.







loop-util: enable LO_FLAGS_DIRECT_IO by default on loopback devices
2021-10-19T13:38:21+00:00

Lennart Poettering
lennart@poettering.net

2021-10-18T15:23:30+00:00

e8c7c4d9d145e0ab1ca75457390fcc698c7e55af

Fixes: #21003





Fixes: #21003







loop: parse and store disk sequence number
2021-07-28T18:59:38+00:00

Luca Boccassi
luca.boccassi@microsoft.com

2021-07-20T14:25:06+00:00

bcef1743a5e9e972df6c38e0b263bbd9de7fac44

When loop devices are re-used, the disk sequence number is increased.
Parse it when creating a loop device and store it.
The kernel will never return DISKSEQ=0, so use it to signal that it's
not supported by the current kernel.





When loop devices are re-used, the disk sequence number is increased.
Parse it when creating a loop device and store it.
The kernel will never return DISKSEQ=0, so use it to signal that it's
not supported by the current kernel.







license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09T04:23:58+00:00

Yu Watanabe
watanabe.yu+github@gmail.com

2020-11-09T04:23:58+00:00

db9ecf050165fd1033c6f81485917e229c4be537












loop-util: use new LOOP_CONFIGURE ioctl
2020-08-11T13:24:18+00:00

Lennart Poettering
lennart@poettering.net

2020-08-06T07:47:14+00:00

86c1c1f34522b960724a6adda5425712bcfd95f7

LOOP_CONFIGURE allows us to configure a loopback device in one ioctl
instead of two, which is not just faster but also removes the race that
udev might start probing the device before we adjusted things properly.

Unfortunately LOOP_CONFIGURE is broken in regards to LO_FLAGS_PARTSCAN
as of kernel 5.8.0. This patch contains a work-around for that, to
fallback to old behaviour if partition scanning is requested but does
not work. Sucks a bit.

Proposed upstream fix for that issue:

https://lkml.org/lkml/2020/8/6/97





LOOP_CONFIGURE allows us to configure a loopback device in one ioctl
instead of two, which is not just faster but also removes the race that
udev might start probing the device before we adjusted things properly.

Unfortunately LOOP_CONFIGURE is broken in regards to LO_FLAGS_PARTSCAN
as of kernel 5.8.0. This patch contains a work-around for that, to
fallback to old behaviour if partition scanning is requested but does
not work. Sucks a bit.

Proposed upstream fix for that issue:

https://lkml.org/lkml/2020/8/6/97