mirror of
https://github.com/home-assistant/operating-system.git
synced 2025-11-16 06:09:26 +00:00
a0871be6c0
* Update buildroot-patches for 2020.11-rc1 buildroot * Update buildroot to 2020.11-rc1 Signed-off-by: Stefan Agner <stefan@agner.ch> * Don't rely on sfdisk --list-free output The --list-free (-F) argument does not allow machine readable mode. And it seems that the output format changes over time (different spacing, using size postfixes instead of raw blocks). Use sfdisk json output and calculate free partition space ourselfs. This works for 2.35 and 2.36 and is more robust since we rely on output which is meant for scripts to parse. * Migrate defconfigs for Buildroot 2020.11-rc1 In particular, rename BR2_TARGET_UBOOT_BOOT_SCRIPT(_SOURCE) to BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT(_SOURCE). * Rebase/remove systemd patches for systemd 246 * Drop apparmor/libapparmor from buildroot-external * hassos-persists: use /run as directory for lockfiles The U-Boot tools use /var/lock by default which is not created any more by systemd by default (it is under tmpfiles legacy.conf, which we no longer install). * Disable systemd-update-done.service The service is not suited for pure read-only systems. In particular the service needs to be able to write a file in /etc and /var. Remove the service. Note: This is a static service and cannot be removed using systemd-preset. * Disable apparmor.service for now The service loads all default profiles. Some might actually cause problems. E.g. the profile for ping seems not to match our setup for /etc/resolv.conf: [85503.634653] audit: type=1400 audit(1605286002.684:236): apparmor="DENIED" operation="open" profile="ping" name="/run/resolv.conf" pid=27585 comm="ping" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
44 lines
1.6 KiB
Diff
44 lines
1.6 KiB
Diff
Message-Id: <07010a2ad79559c412949f0005dbe3cb03d8416e.1498504812.git.ps@pks.im>
|
|
From: Patrick Steinhardt <ps@pks.im>
|
|
Date: Mon, 26 Jun 2017 21:20:45 +0200
|
|
Subject: [PATCH] 9pfs: include <linux/limits.h> for XATTR_SIZE_MAX
|
|
|
|
The function `v9fs_xattrcreate` makes use of the define `XATTR_SIZE_MAX`
|
|
to reject attempts of creating xattrs with an invalid size, which is
|
|
defined in <linux/limits.h>. On glibc-based systems, this header is
|
|
indirectly included via <limits.h>, <bits/posix1_lim.h>,
|
|
<bitts/local_lim.h>, but on other platforms this is not guaranteed due
|
|
to not being part of the POSIX standard. One examples are systems based
|
|
on musl libc, which do not include the <linux/limits.h> indirectly,
|
|
which leads to `XATTR_SIZE_MAX` being undefined.
|
|
|
|
Fix this error by directly include <linux/limits.h>. As the 9P fs code
|
|
is being Linux-based either way, we can simply do so without breaking
|
|
other platforms. This enables building 9pfs on musl-based systems.
|
|
|
|
Signed-off-by: Patrick Steinhardt <ps@pks.im>
|
|
[ Changes by AF
|
|
- Apply to the QEMU tree inside of Xen
|
|
]
|
|
Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
|
|
---
|
|
Upstream Status: Pending review and acceptance
|
|
|
|
tools/qemu-xen/hw/9pfs/9p.c | 1 +
|
|
1 file changed, 1 insertion(+)
|
|
|
|
diff --git a/tools/qemu-xen/hw/9pfs/9p.c b/tools/qemu-xen/hw/9pfs/9p.c
|
|
index 96d2683348..48cd558e96 100644
|
|
--- a/tools/qemu-xen/hw/9pfs/9p.c
|
|
+++ b/tools/qemu-xen/hw/9pfs/9p.c
|
|
@@ -13,6 +13,7 @@
|
|
|
|
#include "qemu/osdep.h"
|
|
#include <glib/gprintf.h>
|
|
+#include <linux/limits.h>
|
|
#include "hw/virtio/virtio.h"
|
|
#include "qapi/error.h"
|
|
#include "qemu/error-report.h"
|
|
--
|
|
2.13.2
|