Hi, all
I'm glad to invide Yihao Wu <wuyihao(a)linux.alibaba.com> as maintainer
of ANCK scheduler.
Yihao is working on linux kernel scheduler for 5 years, and show great
interest in kernel technologies.
Here are some highlight contributions from Yihao:
1. Implement the lastest version of CPU SLI feature (Sevice Level Index)
for rich container;
this new version show great advantages in performance and accuracy.
2. Design and implement cpu isolation solution for function computing
running on Daishu, which
enable 2000 microvm running on one machine which acceptable overhead
(< 1%).
3. The core develper in plugsched project, which aims to upgrade linux
kernel scheduler subsystem online.
more details please visit project repo:
https://gitee.com/anolis/plugsched
4. Backport cpuidle-haltpoll feature to ANCK and optimize performance
for virtual machine.
5. Proficient in problem analysis, be skilled using gdb, crash, pyGDB,
qemu ...
https://lore.kernel.org/all/20220428103726.108597-1-wuyihao@linux.alibaba.c…
Working with Yihao is efficient and have a sense of achievement. Let us
hope it happens soon.
-- csp
> Hi, all
>
>
> I'm glad to invide Yihao Wu <wuyihao(a)linux.alibaba.com> as maintainer
> of ANCK scheduler.
> Yihao is working on linux kernel scheduler for 5 years, and show great
> interest in kernel technologies.
>
> Here are some highlight contributions from Yihao:
>
> 1. Implement the lastest version of CPU SLI feature (Sevice Level Index)
> for rich container;
> this new version show great advantages in performance and accuracy.
>
> 2. Design and implement cpu isolation solution for function computing
> running on Daishu, which
> enable 2000 microvm running on one machine which acceptable overhead
> (< 1%).
>
> 3. The core develper in plugsched project, which aims to upgrade linux
> kernel scheduler subsystem online.
> more details please visit project repo:
> https://gitee.com/anolis/plugsched
>
> 4. Backport cpuidle-haltpoll feature to ANCK and optimize performance
> for virtual machine.
>
> 5. Proficient in problem analysis, be skilled using gdb, crash, pyGDB,
> qemu ...
> https://lore.kernel.org/all/20220428103726.108597-1-wuyihao@linux.alibaba.c…
>
>
>
> Working with Yihao is efficient and have a sense of achievement. Let us
> hope it happens soon.
Looks great to me.
Acked-by: Baolin Wang <baolin.wang(a)linux.alibaba.com>
Hi,
The ANCK-5.10 next release has been code frozen yesterday（4.20), the
develop branch "devel-5.10" has been rebased to the latest upstream
stable branch "5.10.112" as planned.
Please note that your forked branch need pull the latest devel-5.10,
especially for the PR in progress.
Thanks for your attention!
BS.
-- Shiloong
Hi Jian,
Thanks very much for your work!
The patch is looks good for this issue#254.
Some minor suggestions:
1. It's better to use "cloud-kernel(a)lists.openanolis.cn" for cloud
kernel issues;
2. Could you please raise MR(merge request) directly for this patch on
codeup?
(https://codeup.openanolis.cn/codeup/kernel/cloud-kernel/merge_requests), for
more details you can refers to
https://openanolis.cn/sig/Cloud-Kernel/doc/384933904934126352
3. Seems this patch also available for ANCK-5.10, could you please also
raise a MR for devel-5.10 branch? with exfat enable together.
BTW, the subject of the patch mail is better as "[PATCH] anolis: config:
Enable CONFIG_NTFS" directly.
Thanks again!
BS.
-- shile
On 2021/11/11 12:44, 张俭 wrote:
> Hi,
> I submitted a patch about ntfs.
>
>
>
>
>
>
>
> _______________________________________________
> Anolis OS mailing list -- os(a)lists.openanolis.cn
> To unsubscribe send an email to os-leave(a)lists.openanolis.cn
>
From: Miklos Szeredi <mszeredi(a)redhat.com>
commit 4a2abf99f9c2877039006b8dfb3ec4e0d1278fe8 upstream
In the FOPEN_DIRECT_IO case the write path doesn't call file_remove_privs()
and that means setuid bit is not cleared if unpriviliged user writes to a
file with setuid bit set.
pjdfstest chmod test 12.t tests this and fails.
Fix this by adding a flag to the FUSE_WRITE message that requests clearing
privileges on the given file. This needs
This better than just calling fuse_remove_privs(), because the attributes
may not be up to date, so in that case a write may miss clearing the
privileges.
Test case:
$ passthrough_ll /mnt/pasthrough-mnt -o default_permissions,allow_other,cache=never
$ mkdir /mnt/pasthrough-mnt/testdir
$ cd /mnt/pasthrough-mnt/testdir
$ prove -rv pjdfstests/tests/chmod/12.t
Reported-by: Vivek Goyal <vgoyal(a)redhat.com>
Signed-off-by: Miklos Szeredi <mszeredi(a)redhat.com>
Tested-by: Vivek Goyal <vgoyal(a)redhat.com>
Signed-off-by: Jeffle Xu <jefflexu(a)linux.alibaba.com>
---
Corresponding virtiofsd commits can refer to
[1] virtiofsd: Parse flag FUSE_WRITE_KILL_PRIV
https://gitlab.com/virtio-fs/qemu/-/commit/f779bc5265e7e7abb13a03d4bfbc7415…
[2] virtiofsd: Drop CAP_FSETID if client asked for it
https://gitlab.com/virtio-fs/qemu/-/commit/ee88465224b3aed2596049caa28f86cb…
---
fs/fuse/file.c | 11 +++++++++--
include/uapi/linux/fuse.h | 5 +++++
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index 80f991ac4a0a..e6d2e5e2b072 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -1404,10 +1404,17 @@ ssize_t fuse_direct_io(struct fuse_io_priv *io, struct iov_iter *iter,
if (err && !nbytes)
break;
- if (write)
+ if (write) {
+ if (!capable(CAP_FSETID)) {
+ struct fuse_write_in *inarg;
+
+ inarg = &req->misc.write.in;
+ inarg->write_flags |= FUSE_WRITE_KILL_PRIV;
+ }
nres = fuse_send_write(req, io, pos, nbytes, owner);
- else
+ } else {
nres = fuse_send_read(req, io, pos, nbytes, owner);
+ }
if (!io->async)
fuse_release_user_pages(req, io->should_dirty);
diff --git a/include/uapi/linux/fuse.h b/include/uapi/linux/fuse.h
index 1c6956b32597..5a011734a97b 100644
--- a/include/uapi/linux/fuse.h
+++ b/include/uapi/linux/fuse.h
@@ -120,6 +120,9 @@
* 7.28
* - add FOPEN_CACHE_DIR
* - add FUSE_CACHE_SYMLINKS
+ *
+ * 7.31
+ * - add FUSE_WRITE_KILL_PRIV flag
*/
#ifndef _LINUX_FUSE_H
@@ -315,9 +318,11 @@ struct fuse_file_lock {
*
* FUSE_WRITE_CACHE: delayed write from page cache, file handle is guessed
* FUSE_WRITE_LOCKOWNER: lock_owner field is valid
+ * FUSE_WRITE_KILL_PRIV: kill suid and sgid bits
*/
#define FUSE_WRITE_CACHE (1 << 0)
#define FUSE_WRITE_LOCKOWNER (1 << 1)
+#define FUSE_WRITE_KILL_PRIV (1 << 2)
/**
* Read flags
--
2.27.0
