Searched hist:a3c751a5 (Results 1 – 4 of 4) sorted by relevance
/openbmc/linux/include/linux/ |
H A D | device_cgroup.h | a3c751a5 Thu May 14 09:44:23 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> vfs: allow unprivileged whiteout creation
Whiteouts, unlike real device node should not require privileges to create.
The general concern with device nodes is that opening them can have side effects. The kernel already avoids zero major (see Documentation/admin-guide/devices.txt). To be on the safe side the patch explicitly forbids registering a char device with 0/0 number (see cdev_add()).
This guarantees that a non-O_PATH open on a whiteout will fail with ENODEV; i.e. it won't have any side effect.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> a3c751a5 Thu May 14 09:44:23 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> vfs: allow unprivileged whiteout creation Whiteouts, unlike real device node should not require privileges to create. The general concern with device nodes is that opening them can have side effects. The kernel already avoids zero major (see Documentation/admin-guide/devices.txt). To be on the safe side the patch explicitly forbids registering a char device with 0/0 number (see cdev_add()). This guarantees that a non-O_PATH open on a whiteout will fail with ENODEV; i.e. it won't have any side effect. Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
|
H A D | fs.h | a3c751a5 Thu May 14 09:44:23 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> vfs: allow unprivileged whiteout creation
Whiteouts, unlike real device node should not require privileges to create.
The general concern with device nodes is that opening them can have side effects. The kernel already avoids zero major (see Documentation/admin-guide/devices.txt). To be on the safe side the patch explicitly forbids registering a char device with 0/0 number (see cdev_add()).
This guarantees that a non-O_PATH open on a whiteout will fail with ENODEV; i.e. it won't have any side effect.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> a3c751a5 Thu May 14 09:44:23 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> vfs: allow unprivileged whiteout creation Whiteouts, unlike real device node should not require privileges to create. The general concern with device nodes is that opening them can have side effects. The kernel already avoids zero major (see Documentation/admin-guide/devices.txt). To be on the safe side the patch explicitly forbids registering a char device with 0/0 number (see cdev_add()). This guarantees that a non-O_PATH open on a whiteout will fail with ENODEV; i.e. it won't have any side effect. Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
|
/openbmc/linux/fs/ |
H A D | char_dev.c | a3c751a5 Thu May 14 09:44:23 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> vfs: allow unprivileged whiteout creation
Whiteouts, unlike real device node should not require privileges to create.
The general concern with device nodes is that opening them can have side effects. The kernel already avoids zero major (see Documentation/admin-guide/devices.txt). To be on the safe side the patch explicitly forbids registering a char device with 0/0 number (see cdev_add()).
This guarantees that a non-O_PATH open on a whiteout will fail with ENODEV; i.e. it won't have any side effect.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> a3c751a5 Thu May 14 09:44:23 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> vfs: allow unprivileged whiteout creation Whiteouts, unlike real device node should not require privileges to create. The general concern with device nodes is that opening them can have side effects. The kernel already avoids zero major (see Documentation/admin-guide/devices.txt). To be on the safe side the patch explicitly forbids registering a char device with 0/0 number (see cdev_add()). This guarantees that a non-O_PATH open on a whiteout will fail with ENODEV; i.e. it won't have any side effect. Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
|
H A D | namei.c | a3c751a5 Thu May 14 09:44:23 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> vfs: allow unprivileged whiteout creation
Whiteouts, unlike real device node should not require privileges to create.
The general concern with device nodes is that opening them can have side effects. The kernel already avoids zero major (see Documentation/admin-guide/devices.txt). To be on the safe side the patch explicitly forbids registering a char device with 0/0 number (see cdev_add()).
This guarantees that a non-O_PATH open on a whiteout will fail with ENODEV; i.e. it won't have any side effect.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> a3c751a5 Thu May 14 09:44:23 CDT 2020 Miklos Szeredi <mszeredi@redhat.com> vfs: allow unprivileged whiteout creation Whiteouts, unlike real device node should not require privileges to create. The general concern with device nodes is that opening them can have side effects. The kernel already avoids zero major (see Documentation/admin-guide/devices.txt). To be on the safe side the patch explicitly forbids registering a char device with 0/0 number (see cdev_add()). This guarantees that a non-O_PATH open on a whiteout will fail with ENODEV; i.e. it won't have any side effect. Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
|