From: Krzysztof Kozlowski <k.kozlowski@samsung.com> To: Kukjin Kim <kgene@kernel.org>, Javier Martinez Canillas <javier@osg.samsung.com>, Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Kevin Hilman <khilman@kernel.org>, Krzysztof Kozlowski <k.kozlowski@samsung.com>, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> Subject: [PATCH 1/2] ARM: exynos_defconfig: Enable SECCOMP Date: Fri, 12 Aug 2016 14:34:02 +0200 [thread overview] Message-ID: <1471005243-6409-1-git-send-email-k.kozlowski@samsung.com> (raw) Systemd already supports seccomp. It seems some distros are building systemd with seccomp, e.g. Arch on ARM, thus leading to boot errors: systemd-logind.service: Failed at step SECCOMP spawning /usr/lib/systemd/systemd-logind: Invalid argument Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com> --- arch/arm/configs/exynos_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig index 81862a77dddf..5476be3be686 100644 --- a/arch/arm/configs/exynos_defconfig +++ b/arch/arm/configs/exynos_defconfig @@ -17,6 +17,7 @@ CONFIG_PREEMPT=y CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_CMA=y +CONFIG_SECCOMP=y CONFIG_ZBOOT_ROM_TEXT=0x0 CONFIG_ZBOOT_ROM_BSS=0x0 CONFIG_ARM_APPENDED_DTB=y -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/2] ARM: exynos_defconfig: Enable SECCOMP Date: Fri, 12 Aug 2016 14:34:02 +0200 [thread overview] Message-ID: <1471005243-6409-1-git-send-email-k.kozlowski@samsung.com> (raw) Systemd already supports seccomp. It seems some distros are building systemd with seccomp, e.g. Arch on ARM, thus leading to boot errors: systemd-logind.service: Failed at step SECCOMP spawning /usr/lib/systemd/systemd-logind: Invalid argument Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com> --- arch/arm/configs/exynos_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig index 81862a77dddf..5476be3be686 100644 --- a/arch/arm/configs/exynos_defconfig +++ b/arch/arm/configs/exynos_defconfig @@ -17,6 +17,7 @@ CONFIG_PREEMPT=y CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_CMA=y +CONFIG_SECCOMP=y CONFIG_ZBOOT_ROM_TEXT=0x0 CONFIG_ZBOOT_ROM_BSS=0x0 CONFIG_ARM_APPENDED_DTB=y -- 1.9.1
next reply other threads:[~2016-08-12 12:34 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-08-12 12:34 Krzysztof Kozlowski [this message] 2016-08-12 12:34 ` [PATCH 1/2] ARM: exynos_defconfig: Enable SECCOMP Krzysztof Kozlowski 2016-08-12 12:34 ` [PATCH 2/2] ARM: multi_v7_defconfig: " Krzysztof Kozlowski 2016-08-12 12:34 ` Krzysztof Kozlowski 2016-08-12 13:03 ` Javier Martinez Canillas 2016-08-12 13:03 ` Javier Martinez Canillas 2016-08-12 13:02 ` [PATCH 1/2] ARM: exynos_defconfig: " Javier Martinez Canillas 2016-08-12 13:02 ` Javier Martinez Canillas
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1471005243-6409-1-git-send-email-k.kozlowski@samsung.com \ --to=k.kozlowski@samsung.com \ --cc=arnd@arndb.de \ --cc=b.zolnierkie@samsung.com \ --cc=javier@osg.samsung.com \ --cc=kgene@kernel.org \ --cc=khilman@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=olof@lixom.net \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.