Attachment 97732 Details for Bug 77646 – new patch submit

new patch submit

0001-You-can-not-put-the-cached-result-of-use_smack-fct.patch (text/plain), 1.48 KB, created by Ronan22 on 2014-04-22 08:38:58 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Ronan22

Created: 2014-04-22 08:38:58 UTC

Size: 1.48 KB

patch

obsolete

>From 2f82413004d35a2ce2055466666f13a61f2446b0 Mon Sep 17 00:00:00 2001
>From: Ronan Le Martret <ronan@fridu.net>
>Date: Tue, 22 Apr 2014 10:33:25 +0200
>Subject: [PATCH 1/1] You can not put the cached result of use_smack fct, as we
> are not sure the "/sys" is mounted. So we should mount "sys" before "/proc".
>
>Change-Id: I2b1804cd91ddb729ba1ee192facd44d1ef3d2833
>Signed-off-by: Ronan Le Martret <ronan@fridu.net>
>---
> src/core/mount-setup.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/src/core/mount-setup.c b/src/core/mount-setup.c
>index 387030a..769bd4a 100644
>--- a/src/core/mount-setup.c
>+++ b/src/core/mount-setup.c
>@@ -67,10 +67,10 @@ typedef struct MountPoint {
> #define N_EARLY_MOUNT 5
> 
> static const MountPoint mount_table[] = {
>-        { "proc",       "/proc",                     "proc",       NULL, MS_NOSUID|MS_NOEXEC|MS_NODEV,
>-          NULL,       MNT_FATAL|MNT_IN_CONTAINER },
>         { "sysfs",      "/sys",                      "sysfs",      NULL, MS_NOSUID|MS_NOEXEC|MS_NODEV,
>           NULL,       MNT_FATAL|MNT_IN_CONTAINER },
>+        { "proc",       "/proc",                     "proc",       NULL, MS_NOSUID|MS_NOEXEC|MS_NODEV,
>+          NULL,       MNT_FATAL|MNT_IN_CONTAINER },
>         { "devtmpfs",   "/dev",                      "devtmpfs",   "mode=755", MS_NOSUID|MS_STRICTATIME,
>           NULL,       MNT_FATAL|MNT_IN_CONTAINER },
>         { "securityfs", "/sys/kernel/security",      "securityfs", NULL, MS_NOSUID|MS_NOEXEC|MS_NODEV,
>-- 
>1.8.1.4
>

Actions: View

Attachments on bug 77646: 97559 | 97732

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.