diff options
| author | Petr Štetiar <ynezz@true.cz> | 2019-03-27 11:31:14 +0100 |
|---|---|---|
| committer | Petr Štetiar <ynezz@true.cz> | 2019-06-25 14:12:21 +0000 |
| commit | 2109156b794fd94a94df358afad860bffc72d9d3 (patch) | |
| tree | 569abcfe7004c05d667171c64e3eefc505d66202 /target/linux/generic/pending-4.19/834-ledtrig-libata.patch | |
| parent | d03ef97c1b57b2b5588115d3b7c7355399874aa3 (diff) | |
| download | upstream-2109156b794fd94a94df358afad860bffc72d9d3.tar.gz upstream-2109156b794fd94a94df358afad860bffc72d9d3.tar.bz2 upstream-2109156b794fd94a94df358afad860bffc72d9d3.zip | |
x86: image: remove TARGET_IMAGES_PAD option and force padding
Currently we're producing unusable x86 combined squashfs images
(18.06.1, 18.06.2 and snapshots) as we don't enable TARGET_IMAGES_PAD,
thus providing very small space for the overlay filesystem, leading to
the following with OpenWrt 18.06.1 r7258-5eb055306f images on x86 QEMU:
root@(none):/# mount | egrep 'root|overlay'
/dev/root on /rom type squashfs
/dev/loop0 on /overlay type ext4
overlayfs:/overlay on / type overlay
root@(none):/# df -h | egrep 'root|overlay|Size'
Filesystem Size Used Available Use% Mounted on
/dev/root 2.5M 2.5M 0 100% /rom
/dev/loop0 113.0K 8.0K 97.0K 8% /overlay
overlayfs:/overlay 113.0K 8.0K 97.0K 8% /
We should rather ensure proper image padding in image generation code
and we shouldn't rely on config options in order to generate usable
images.
So this patch removes TARGET_IMAGES_PAD config option and enforces
padding on combined images.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Diffstat (limited to 'target/linux/generic/pending-4.19/834-ledtrig-libata.patch')
0 files changed, 0 insertions, 0 deletions