- Dev - mailweb.openeuler.org

Re: openEuler 技术委员会例会
by Jianmin Wang 14 Feb '22

14 Feb '22

Hi，王书，您好，感谢提交议题，因为和 kernel 密切相关，是否有 Kernel SIG 的意见以及对应的 PR / Issue 提前发出来呢？ ——王建民 > On 14 Feb 2022, at 4:18 PM, 王书 <wangshu(a)uniontech.com> wrote: > > 议题申报： > 《推送TOA模块到内核sig组申请》---统信刘冬华 > > > ------------------ Original ------------------ > From: "叶青龙"<yeqinglong(a)uniontech.com>; > Date: Mon, Feb 14, 2022 03:22 PM > To: "王书"<wangshu(a)uniontech.com>; > Subject: Fw:[Dev] Fwd: openEuler 技术委员会例会 > > 请在例会通知邮件上申报议题。 > > > > > >> 服务器OS与云计算产线叶青龙 >> >> 联系电话：18991378194 >> >> 地址：西安市雁塔区天谷八路西安软件新城软件研发基地2期 > > > > > ------------------ Original ------------------ > From: "王建民"<jianmin(a)iscas.ac.cn>; > Date: Tue, Feb 8, 2022 04:43 PM > To: "tc"<tc(a)openeuler.org>; "dev"<dev(a)openeuler.org>; > Subject: [Dev] Fwd: openEuler 技术委员会例会 > > 大家新年好， > > 春节后第一次 TC 例会将于 2022 年 2 月 16 日进行，欢迎大家回复邮件提交议题。 > > 谢谢。 > > -王建民 > > Hello, Everyone, > > Happy New Year! > > The first bi-weekly meeting of openEuler TC will be held on 2022/02/16 Wednesday. > > Welcome to submit topics by replying to the email. > > > Best Regards, > Jianmin Wang > > > Begin forwarded message: > > From: openEuler conference <public(a)openeuler.org> > Date: 8 February 2022 at 2:28:47 PM GMT+8 > Subject: [Dev] openEuler 技术委员会例会 > > 您好！ > > TC SIG 邀请您参加 2022-02-16 10:00 召开的ZOOM会议 > > 会议主题：openEuler 技术委员会例会 > > 会议链接：https://us06web.zoom.us/j/82775432385?pwd=Y2hkOGZkeklrMzJVaUVnM2dONTBxdz09 > > 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID > > 更多资讯尽在：https://openeuler.org/zh/ > > > > > Hello! > > openEuler TC SIG invites you to attend the ZOOM conference will be held at 2022-02-16 10:00, > > The subject of the conference is openEuler 技术委员会例会, > > You can join the meeting at https://us06web.zoom.us/j/82775432385?pwd=Y2hkOGZkeklrMzJVaUVnM2dONTBxdz09. > > Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. > > More information: https://openeuler.org/en/ > > _______________________________________________ > Dev mailing list -- dev(a)openeuler.org > To unsubscribe send an email to dev-leave(a)openeuler.org > _______________________________________________ > Dev mailing list -- dev(a)openeuler.org > To unsubscribe send an email to dev-leave(a)openeuler.org

2 1

小程序升级讨论
by openEuler conference 14 Feb '22

14 Feb '22

您好！ sig-OpenDesign SIG 邀请您参加 2022-02-15 11:00 召开的ZOOM会议会议主题：小程序升级讨论会议内容：讨论社区小程序升级方案会议链接：https://us06web.zoom.us/j/89808923445?pwd=TGd6bW5OSVBRWmlBWDFsM1piRlRLUT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-OpenDesign SIG invites you to attend the ZOOM conference will be held at 2022-02-15 11:00, The subject of the conference is 小程序升级讨论, Summary: 讨论社区小程序升级方案 You can join the meeting at https://us06web.zoom.us/j/89808923445?pwd=TGd6bW5OSVBRWmlBWDFsM1piRlRLUT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

【2203LTS版本】risc-v需求讨论
by openEuler conference 14 Feb '22

14 Feb '22

您好！ sig-QA SIG 邀请您参加 2022-02-14 16:30 召开的ZOOM会议会议主题：【2203LTS版本】risc-v需求讨论会议链接：https://us06web.zoom.us/j/82958418689?pwd=SVdndVpqKyt5YzBVT2pHaXFEMDNQUT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-QA SIG invites you to attend the ZOOM conference will be held at 2022-02-14 16:30, The subject of the conference is 【2203LTS版本】risc-v需求讨论, You can join the meeting at https://us06web.zoom.us/j/82958418689?pwd=SVdndVpqKyt5YzBVT2pHaXFEMDNQUT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

[Compiler-SIG/OpenJDK] Vector API of JDK stepped into the fourth incubation with a new JEP for wider discussion/idea
by Erik Yuan 14 Feb '22

14 Feb '22

Hi folks, Vector API is a OpenJDK feature helping optimize the compilation of vector computation at runtime. This feature has gone through three incubations. JEP 417, Vector API (Third Incubator)<http://openjdk.java.net/jeps/417> has been integrated into jdk18, with full SVE and masking support. Arm OpenJDK team is now working together with OpenJDK community on the fourth incubator: https://bugs.openjdk.java.net/browse/JDK-8280173 (draft). Any inputs are welcome! Especially the ideas based on your service scenarios on Arm platforms. You may reply this email thread or directly provide your comments into JEP above. BTW, I'd like to introduce my colleague Ningsheng Jian who is leading Arm OpenJDK team. If there are any further questions, feel free to ping us. Thanks, Erik

3 3

【关于openEuler-20.03-LTS-Next 分支冻结的意见征询与公示】
by xiasenlin 14 Feb '22

14 Feb '22

各位社区的maintainer和developer们好：在2022年2月12号的release会议上，release成员及与会者达成一致：考虑到openEuler-20.03-LTS-Next分支从SP3版本之后，在可预见的时间内不再有新的版本，因此从今天开始正式冻结openEuler-20.03-LTS-Next 分支，同时为release成员预留check-pr权限，若在接下来的两周内没有在release例会中收到需要解冻的决议，将继续观察3个月，若3个月内不再有例外合入，那么我们将前往community将该分支设为readonly.

1 0

openEuler kernel scm文件系统交流
by openEuler conference 14 Feb '22

14 Feb '22

您好！ Kernel SIG 邀请您参加 2022-02-14 14:30 召开的ZOOM会议会议主题：openEuler kernel scm文件系统交流会议链接：https://us06web.zoom.us/j/82584624791?pwd=elFaRlo0QjBsd0lCWUJhbFhsaGxLZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler Kernel SIG invites you to attend the ZOOM conference will be held at 2022-02-14 14:30, The subject of the conference is openEuler kernel scm文件系统交流, You can join the meeting at https://us06web.zoom.us/j/82584624791?pwd=elFaRlo0QjBsd0lCWUJhbFhsaGxLZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

[PATCH] libmultipath: fix multipathd coredump in disassemble_map
by lixiaokeng 12 Feb '22

12 Feb '22

Coredump appears when events are executed in a certain order. 1. The sdc and sdd are added as paths of d1. The sdc is added firstly and d1->wait_for_udev be set to 1. Then sdd is added but it just adds to pathvec because d1->wait_for_udev is 1. 2. The uev_remove_path(sdc) are executed. Because d1 has one path, d1 will be flushed. 3. The uev_add_path(sdc) are executed. Now sdc and sdd will both add to d1 in adopt_paths because sdd->wwid is d1. And d1->wait_for_udev be set to 1. 4. The uev_remove_path(sdd) are executed. Because d1->wait_for_udev is 1, domap doesn't executed and the major:minor of sdd(8:64) still exist in kernel d1. The sdd in pathvec is deleted. 5. The uev_add_path(sdd) are executed. Now the sdd(8:64) is a path of d2. And new sdd is added to pathvec. 6. The update_multipath_strings(d1) are executed. The d1 find sdd in pathvec by dev_t(8:64）and sdd will be add to d1. Now the pointer of sdd is store in paths of d1 and d2. 7. When NIC is down and a new path add to d1, sdd will be freed in verify_paths (because sdd is actually a path of d2). 8. When d2->hwe is sdd->hwe and setup_map(d2) is called. Core causes. The path shouldn't be add to the mpp whose wwid is different with its. Here we add wwid check in disassemble_map. This bug has been solved in upstream in update_pathvec_from_dm. It is a great change, so we fix it with huawei patch. This patch could be discarded when multipath-tools update. Signed-off-by:lixiaokeng<lixiaokeng(a)huawei.com> --- libmultipath/dmparser.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/libmultipath/dmparser.c b/libmultipath/dmparser.c index 0f370e9..99b57db 100644 --- a/libmultipath/dmparser.c +++ b/libmultipath/dmparser.c @@ -342,6 +342,16 @@ int disassemble_map(vector pathvec, char *params, struct multipath *mpp, goto out1; } } else { + if (strlen(pp->wwid) && strlen(mpp->wwid) && + strcmp(pp->wwid, mpp->wwid) != 0) { + condlog(0, "%s: path wwid is different with that of %s.\n", pp->dev_t, mpp->alias); + FREE(word); + for (k = 0; k < num_paths_args; k++) { + p += get_word(p, NULL); + } + continue; + } + if (!strlen(pp->wwid) && strlen(mpp->wwid)) strlcpy(pp->wwid, mpp->wwid, --

1 0

[PATCH] libmultipath: fix daemon memory leak in disassemble_map
by lixiaokeng 12 Feb '22

12 Feb '22

When one iscsi device logs in and logs out with the "multipath -r" executed at the same time, memory leak happens in multipathd process. The reason is following. When "multipath -r" is executed, the path will be free in configure function. Before path_discovery executed, iscsi device logs out. Then path_discovery will not find any path and there is no path in the gvecs->pathvec. When map_discovery function is executed, disassemble_map function will be called. Because gvecs->pathvec->slot is empty and is_deamon is 1, a path will be allocated and is not stored in gvecs->pathvec but store in mpp->pg. But when the mpp is removed and freed by remove_map function, the path will not be free and can't be find anymore. The procedure details given as follows, 1."multipath -r" is executed main ->child ->reconfigure ->configure ->path_discovery //after iscsi logout ->map_discovery ->update_multipath_table ->disassemble_map ->alloc_path 2.then "multipath -r" is executed again main ->child ->reconfigure ->remove_maps_and_stop_waiters ->remove_maps Here, we skip alloc_path if pp isn't find in pathvec and process is daemon. In daemon, we should not store path with incomplete information to pathvec. The pathvec stores all paths in daemon, so it is reasonable keep same with pathvec. Reported-by: Tianxiong Lu <lutianxiong(a)huawei.com> Signed-off-by: Lixiaokeng <lixiaokeng(a)huawei.com> Signed-off-by: Zhiqiang Liu <liuzhiqiang26(a)huawei.com> --- libmultipath/dmparser.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/libmultipath/dmparser.c b/libmultipath/dmparser.c index 7da5fbf..3ce6eb3 100644 --- a/libmultipath/dmparser.c +++ b/libmultipath/dmparser.c @@ -305,6 +305,16 @@ int disassemble_map(vector pathvec, char *params, struct multipath *mpp, } if (!pp) { + /* daemon should keep same with pathvec */ + /* pp is not find in pathvec, skip it */ + if (is_daemon) { + FREE(word); + for (k = 0; k < num_paths_args; k++) { + p += get_word(p, NULL); + } + continue; + } + pp_unfound = 1; pp = alloc_path(); @@ -317,8 +327,7 @@ int disassemble_map(vector pathvec, char *params, struct multipath *mpp, strlcpy(pp->wwid, mpp->wwid, WWID_SIZE); } - /* Only call this in multipath client mode */ - if (!is_daemon && store_path(pathvec, pp)) { + if (store_path(pathvec, pp)) { free_path(pp); goto out1; } --

1 0

[PATCH] fix memory leak in check_path
by lixiaokeng 12 Feb '22

12 Feb '22

We get alias by strdup, and should free it after using. Sigined-off-by:lixiaokeng<lixiaokeng(a)huawei.com> --- multipathd/main.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/multipathd/main.c b/multipathd/main.c index 0327100..e4ff027 100644 --- a/multipathd/main.c +++ b/multipathd/main.c @@ -1900,10 +1900,12 @@ check_path (struct vectors * vecs, struct path * pp, int ticks) } if (ev_add_map(dev_path, alias, vecs)) { condlog(2, "fail to add map for mpp %s", alias); + FREE(alias); return 0; } else { condlog(2, "success to add map for mpp %s", alias); } + FREE(alias); } } else { return 0; --

1 0

[PATCH] multipathd: fix mpp->hwe use after free in ev_remove_path
by lixiaokeng 12 Feb '22

12 Feb '22

When a multipath device (for example mpatha) has only one path and it can't flush because of occupation, "multipathd del path" and "multipath -v2" may lead to multipathd coredump. The reason is that mpp->hwe = pp->hwe but pp->hwe will be free later. Here we clear mpp->hwe in clear_ref_from_mpp. Signed-off-by: Lixiaokeng <lixiaokeng(a)huawei.com> --- multipathd/main.c | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/multipathd/main.c b/multipathd/main.c index 3e00c41..ae864ad 100644 --- a/multipathd/main.c +++ b/multipathd/main.c @@ -823,17 +823,23 @@ void clear_ref_from_mpp(struct path * pp, struct vectors * vecs) int j; mpp = find_mp_by_wwid(vecs->mpvec, pp->wwid); - if(!!mpp){ - condlog(2, "%s: clear path from mpp %s", pp->dev, mpp->alias); - if ((i = find_slot(mpp->paths, (void *)pp)) != -1){ - vector_del_slot(mpp->paths, i); - } - vector_foreach_slot (mpp->pg, pgp, j) { - if ((i = find_slot(pgp->paths, (void *)pp)) != -1){ - vector_del_slot(pgp->paths, i); - } + if (!mpp) { + return; + } + + condlog(2, "%s: clear path from mpp %s", pp->dev, mpp->alias); + if (mpp->hwe == pp->hwe) { + mpp->hwe = NULL; + } + if ((i = find_slot(mpp->paths, (void *)pp)) != -1) { + vector_del_slot(mpp->paths, i); + } + vector_foreach_slot(mpp->pg, pgp, j) { + if ((i = find_slot(pgp->paths, (void *)pp)) != -1) { + vector_del_slot(pgp->paths, i); } } + extract_hwe_from_path(mpp); } static int --

1 0

[PATCH] clear path in mpp->pg in clear_ref_from_mpp
by lixiaokeng 12 Feb '22

12 Feb '22

When multipathd del path xxx, multipathd -v2, multipathd add path xxx and multipath -U dm-x are executed simultaneously, multipath -U dm-x will case coredump. The reason is that there are two paths with same dev_t in dm_table. The process is as follows: multipathd del path xxx(such as sde whose dev_t is 8:64): cli_del_path ->ev_remove_path ->domap //dm_table in kernel will be reloaded and doesn't contain 8:64. //Then multipath -v2 is executed, and the dm_table in kernel //will be reloaded and contains 8:64. ->setup_multipath ->update_multipath_strings ->update_multipath_table ->dm_get_map //get params with 8:64 ->disassemble_map //pp1 will be saved mpp->pg ->delete pp1 in pathvec ->clear_ref_from_mpp //pp is cleared in mpp->paths but still saved in //mpp->pg ->free_paths //pp1 is freed but still exist in mpp->pg and is not null multipathd add path sde cli_add_path ->store_pathinfo //alloc pp2 (dev_t is 8:64), and store it to gvecs->pathvec //pp2 is not equal to pp1 ->ev_add_path ->adopt_paths ->update_mpp_paths //pp1 is found in mpp->pg and its dev_t is //8:64 and dev is not sde (cased by free). //it will be stored in mpp->paths. ->pp2 is stored to mpp->paths ->setup_map //params with two 8:64 ->domap //dm_table is reloaded and contains two 8:64 multipath -U dm-x(sde is one path of dm-x) main ->check_usable_paths ->dm_get_maps //get params with two 8:64 ->disassemble_map //alloc pp3 whose dev_t is 8:64, and pp3 is saved //twice in mpp->pg ->free_multipath(mpp, FREE_PATHS) //double free pp3 Here, we add that pp1 in mpp->pg is cleared in clear_ref_from_mpp. Reported-by: Tianxiong Lu <lutianxiong(a)huawei.com> Signed-off-by: lixiaokeng <lixiaokeng(a)huawei.com> --- multipathd/main.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/multipathd/main.c b/multipathd/main.c index e80ab74..a9e7edd 100644 --- a/multipathd/main.c +++ b/multipathd/main.c @@ -818,7 +818,9 @@ static void clear_ref_from_mpp(struct path * pp, struct vectors * vecs) { struct multipath * mpp = NULL; + struct pathgroup * pgp; int i = -1; + int j; mpp = find_mp_by_wwid(vecs->mpvec, pp->wwid); if(!!mpp){ @@ -826,6 +828,11 @@ void clear_ref_from_mpp(struct path * pp, struct vectors * vecs) if ((i = find_slot(mpp->paths, (void *)pp)) != -1){ vector_del_slot(mpp->paths, i); } + vector_foreach_slot (mpp->pg, pgp, j) { + if ((i = find_slot(pgp->paths, (void *)pp)) != -1){ + vector_del_slot(pgp->paths, i); + } + } } } --

1 0

[PATCH] libmultipath: fix multipathd coredump in disassemble_map
by lixiaokeng 12 Feb '22

12 Feb '22

Coredump appears when events are executed in a certain order. 1. The sdc and sdd are added as paths of d1. The sdc is added firstly and d1->wait_for_udev be set to 1. Then sdd is added but it just adds to pathvec because d1->wait_for_udev is 1. 2. The uev_remove_path(sdc) are executed. Because d1 has one path, d1 will be flushed. 3. The uev_add_path(sdc) are executed. Now sdc and sdd will both add to d1 in adopt_paths because sdd->wwid is d1. And d1->wait_for_udev be set to 1. 4. The uev_remove_path(sdd) are executed. Because d1->wait_for_udev is 1, domap doesn't executed and the major:minor of sdd(8:64) still exist in kernel d1. The sdd in pathvec is deleted. 5. The uev_add_path(sdd) are executed. Now the sdd(8:64) is a path of d2. And new sdd is added to pathvec. 6. The update_multipath_strings(d1) are executed. The d1 find sdd in pathvec by dev_t(8:64）and sdd will be add to d1. Now the pointer of sdd is store in paths of d1 and d2. 7. When NIC is down and a new path add to d1, sdd will be freed in verify_paths (because sdd is actually a path of d2). 8. When d2->hwe is sdd->hwe and setup_map(d2) is called. Core causes. The path shouldn't be add to the mpp whose wwid is different with its. Here we add wwid check in disassemble_map. This bug has been solved in upstream in update_pathvec_from_dm. It is a great change, so we fix it with huawei patch. This patch could be discarded when multipath-tools update. Signed-off-by:lixiaokeng<lixiaokeng(a)huawei.com> --- libmultipath/dmparser.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/libmultipath/dmparser.c b/libmultipath/dmparser.c index 0f370e9..99b57db 100644 --- a/libmultipath/dmparser.c +++ b/libmultipath/dmparser.c @@ -342,6 +342,16 @@ int disassemble_map(vector pathvec, char *params, struct multipath *mpp, goto out1; } } else { + if (strlen(pp->wwid) && strlen(mpp->wwid) && + strcmp(pp->wwid, mpp->wwid) != 0) { + condlog(0, "%s: path wwid is different with that of %s.\n", pp->dev_t, mpp->alias); + FREE(word); + for (k = 0; k < num_paths_args; k++) { + p += get_word(p, NULL); + } + continue; + } + if (!strlen(pp->wwid) && strlen(mpp->wwid)) strlcpy(pp->wwid, mpp->wwid, --

1 0

[PATCH] libmultipath: fix daemon memory leak in disassemble_map
by lixiaokeng 12 Feb '22

12 Feb '22

When one iscsi device logs in and logs out with the "multipath -r" executed at the same time, memory leak happens in multipathd process. The reason is following. When "multipath -r" is executed, the path will be free in configure function. Before path_discovery executed, iscsi device logs out. Then path_discovery will not find any path and there is no path in the gvecs->pathvec. When map_discovery function is executed, disassemble_map function will be called. Because gvecs->pathvec->slot is empty and is_deamon is 1, a path will be allocated and is not stored in gvecs->pathvec but store in mpp->pg. But when the mpp is removed and freed by remove_map function, the path will not be free and can't be find anymore. The procedure details given as follows, 1."multipath -r" is executed main ->child ->reconfigure ->configure ->path_discovery //after iscsi logout ->map_discovery ->update_multipath_table ->disassemble_map ->alloc_path 2.then "multipath -r" is executed again main ->child ->reconfigure ->remove_maps_and_stop_waiters ->remove_maps Here, we skip alloc_path if pp isn't find in pathvec and process is daemon. In daemon, we should not store path with incomplete information to pathvec. The pathvec stores all paths in daemon, so it is reasonable keep same with pathvec. Reported-by: Tianxiong Lu <lutianxiong(a)huawei.com> Signed-off-by: Lixiaokeng <lixiaokeng(a)huawei.com> Signed-off-by: Zhiqiang Liu <liuzhiqiang26(a)huawei.com> --- libmultipath/dmparser.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/libmultipath/dmparser.c b/libmultipath/dmparser.c index 7da5fbf..3ce6eb3 100644 --- a/libmultipath/dmparser.c +++ b/libmultipath/dmparser.c @@ -305,6 +305,16 @@ int disassemble_map(vector pathvec, char *params, struct multipath *mpp, } if (!pp) { + /* daemon should keep same with pathvec */ + /* pp is not find in pathvec, skip it */ + if (is_daemon) { + FREE(word); + for (k = 0; k < num_paths_args; k++) { + p += get_word(p, NULL); + } + continue; + } + pp_unfound = 1; pp = alloc_path(); @@ -317,8 +327,7 @@ int disassemble_map(vector pathvec, char *params, struct multipath *mpp, strlcpy(pp->wwid, mpp->wwid, WWID_SIZE); } - /* Only call this in multipath client mode */ - if (!is_daemon && store_path(pathvec, pp)) { + if (store_path(pathvec, pp)) { free_path(pp); goto out1; } --

1 0

[PATCH] fix memory leak in check_path
by lixiaokeng 12 Feb '22

12 Feb '22

We get alias by strdup, and should free it after using. Sigined-off-by:lixiaokeng<lixiaokeng(a)huawei.com> --- multipathd/main.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/multipathd/main.c b/multipathd/main.c index 0327100..e4ff027 100644 --- a/multipathd/main.c +++ b/multipathd/main.c @@ -1900,10 +1900,12 @@ check_path (struct vectors * vecs, struct path * pp, int ticks) } if (ev_add_map(dev_path, alias, vecs)) { condlog(2, "fail to add map for mpp %s", alias); + FREE(alias); return 0; } else { condlog(2, "success to add map for mpp %s", alias); } + FREE(alias); } } else { return 0; --

1 0

[PATCH] multipathd: fix mpp->hwe use after free in ev_remove_path
by lixiaokeng 12 Feb '22

12 Feb '22

When a multipath device (for example mpatha) has only one path and it can't flush because of occupation, "multipathd del path" and "multipath -v2" may lead to multipathd coredump. The reason is that mpp->hwe = pp->hwe but pp->hwe will be free later. Here we clear mpp->hwe in clear_ref_from_mpp. Signed-off-by: Lixiaokeng <lixiaokeng(a)huawei.com> --- multipathd/main.c | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/multipathd/main.c b/multipathd/main.c index 3e00c41..ae864ad 100644 --- a/multipathd/main.c +++ b/multipathd/main.c @@ -823,17 +823,23 @@ void clear_ref_from_mpp(struct path * pp, struct vectors * vecs) int j; mpp = find_mp_by_wwid(vecs->mpvec, pp->wwid); - if(!!mpp){ - condlog(2, "%s: clear path from mpp %s", pp->dev, mpp->alias); - if ((i = find_slot(mpp->paths, (void *)pp)) != -1){ - vector_del_slot(mpp->paths, i); - } - vector_foreach_slot (mpp->pg, pgp, j) { - if ((i = find_slot(pgp->paths, (void *)pp)) != -1){ - vector_del_slot(pgp->paths, i); - } + if (!mpp) { + return; + } + + condlog(2, "%s: clear path from mpp %s", pp->dev, mpp->alias); + if (mpp->hwe == pp->hwe) { + mpp->hwe = NULL; + } + if ((i = find_slot(mpp->paths, (void *)pp)) != -1) { + vector_del_slot(mpp->paths, i); + } + vector_foreach_slot(mpp->pg, pgp, j) { + if ((i = find_slot(pgp->paths, (void *)pp)) != -1) { + vector_del_slot(pgp->paths, i); } } + extract_hwe_from_path(mpp); } static int --

1 0

[PATCH] clear path in mpp->pg in clear_ref_from_mpp
by lixiaokeng 12 Feb '22

12 Feb '22

When multipathd del path xxx, multipathd -v2, multipathd add path xxx and multipath -U dm-x are executed simultaneously, multipath -U dm-x will case coredump. The reason is that there are two paths with same dev_t in dm_table. The process is as follows: multipathd del path xxx(such as sde whose dev_t is 8:64): cli_del_path ->ev_remove_path ->domap //dm_table in kernel will be reloaded and doesn't contain 8:64. //Then multipath -v2 is executed, and the dm_table in kernel //will be reloaded and contains 8:64. ->setup_multipath ->update_multipath_strings ->update_multipath_table ->dm_get_map //get params with 8:64 ->disassemble_map //pp1 will be saved mpp->pg ->delete pp1 in pathvec ->clear_ref_from_mpp //pp is cleared in mpp->paths but still saved in //mpp->pg ->free_paths //pp1 is freed but still exist in mpp->pg and is not null multipathd add path sde cli_add_path ->store_pathinfo //alloc pp2 (dev_t is 8:64), and store it to gvecs->pathvec //pp2 is not equal to pp1 ->ev_add_path ->adopt_paths ->update_mpp_paths //pp1 is found in mpp->pg and its dev_t is //8:64 and dev is not sde (cased by free). //it will be stored in mpp->paths. ->pp2 is stored to mpp->paths ->setup_map //params with two 8:64 ->domap //dm_table is reloaded and contains two 8:64 multipath -U dm-x(sde is one path of dm-x) main ->check_usable_paths ->dm_get_maps //get params with two 8:64 ->disassemble_map //alloc pp3 whose dev_t is 8:64, and pp3 is saved //twice in mpp->pg ->free_multipath(mpp, FREE_PATHS) //double free pp3 Here, we add that pp1 in mpp->pg is cleared in clear_ref_from_mpp. Reported-by: Tianxiong Lu <lutianxiong(a)huawei.com> Signed-off-by: lixiaokeng <lixiaokeng(a)huawei.com> --- multipathd/main.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/multipathd/main.c b/multipathd/main.c index e80ab74..a9e7edd 100644 --- a/multipathd/main.c +++ b/multipathd/main.c @@ -818,7 +818,9 @@ static void clear_ref_from_mpp(struct path * pp, struct vectors * vecs) { struct multipath * mpp = NULL; + struct pathgroup * pgp; int i = -1; + int j; mpp = find_mp_by_wwid(vecs->mpvec, pp->wwid); if(!!mpp){ @@ -826,6 +828,11 @@ void clear_ref_from_mpp(struct path * pp, struct vectors * vecs) if ((i = find_slot(mpp->paths, (void *)pp)) != -1){ vector_del_slot(mpp->paths, i); } + vector_foreach_slot (mpp->pg, pgp, j) { + if ((i = find_slot(pgp->paths, (void *)pp)) != -1){ + vector_del_slot(pgp->paths, i); + } + } } } --

1 0

sig-Zephyr2022年2月会议
by openEuler conference 11 Feb '22

11 Feb '22

您好！ sig-Zephyr SIG 邀请您参加 2022-02-12 21:45 召开的ZOOM会议会议主题：sig-Zephyr2022年2月会议会议内容： 1. sig-Zephyr简介 2.Zephyr最新进展 3.sig-Zephyr2022计划 4.其他事项讨论，包括Zephyr使用上的答疑解惑会议链接：https://us06web.zoom.us/j/83557438933?pwd=bXVkTmtxNXRsS05sZWNzMnF1S3BYZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-Zephyr SIG invites you to attend the ZOOM conference will be held at 2022-02-12 21:45, The subject of the conference is sig-Zephyr2022年2月会议, Summary: 1. sig-Zephyr简介 2.Zephyr最新进展 3.sig-Zephyr2022计划 4.其他事项讨论，包括Zephyr使用上的答疑解惑 You can join the meeting at https://us06web.zoom.us/j/83557438933?pwd=bXVkTmtxNXRsS05sZWNzMnF1S3BYZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

Re: openEuler 技术委员会例会
by Jianmin Wang 11 Feb '22

11 Feb '22

肆仔，你好， CEV 这块在社区中由安全委员会负责，可以跟 weigang@gwei3 了解情况。建议可以关注 security-committee 安全委员会的例会（会在 dev(a)openeuler.org <mailto:dev@openeuler.org> 邮件列表中通知），与委员会的成员沟通了解更多安全漏洞方面的问题。下面的链接是安全委员会之前例会的会议纪要，也可以参考。 https://etherpad.openeuler.org/p/security-committee-meetings <https://etherpad.openeuler.org/p/security-committee-meetings> ——王建民 > On 8 Feb 2022, at 5:07 PM, 肆仔 <19464572(a)qq.com> wrote: > > > 你好，我想了解下社区版本发布规则跟cve漏洞修复要求 > > 也就是我们社区计划在某个时间点发布一个版本，对这个版本内高危紧急cve漏洞的修复有要求么？比如9分以上的cve漏洞都必须已经修复。 > > 主要是这一段时间高危紧急漏洞爆发的频繁，而cve的修复特别是内核和底层库的修复，又可能影响系统的性能，导致系统性能评测这块又要重做，继而导致系统发布延迟 > 所以想了解社区这边在系统发布时对该系统版本的cve修复是如何要求的 > > 谢谢 > > ------------------ 原始邮件 ------------------ > 发件人: "王建民" <jianmin(a)iscas.ac.cn>; > 发送时间: 2022年2月8日(星期二) 下午2:41 > 收件人: "tc"<tc(a)openeuler.org>;"dev"<dev(a)openeuler.org>; > 主题: [Dev] Fwd: openEuler 技术委员会例会 > > 大家新年好， > > 春节后第一次 TC 例会将于 2022 年 2 月 16 日进行，欢迎大家回复邮件提交议题。 > > 谢谢。 > > -王建民 > > Hello, Everyone, > > Happy New Year! > > The first bi-weekly meeting of openEuler TC will be held on 2022/02/16 Wednesday. > > Welcome to submit topics by replying to the email. > > > Best Regards, > Jianmin Wang > > > Begin forwarded message: > > From: openEuler conference <public(a)openeuler.org> > Date: 8 February 2022 at 2:28:47 PM GMT+8 > Subject: [Dev] openEuler 技术委员会例会 > > 您好！ > > TC SIG 邀请您参加 2022-02-16 10:00 召开的ZOOM会议 > > 会议主题：openEuler 技术委员会例会 > > 会议链接：https://us06web.zoom.us/j/82775432385?pwd=Y2hkOGZkeklrMzJVaUVnM2dONTBxdz09 > > 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID > > 更多资讯尽在：https://openeuler.org/zh/ > > > > > Hello! > > openEuler TC SIG invites you to attend the ZOOM conference will be held at 2022-02-16 10:00, > > The subject of the conference is openEuler 技术委员会例会, > > You can join the meeting at https://us06web.zoom.us/j/82775432385?pwd=Y2hkOGZkeklrMzJVaUVnM2dONTBxdz09. > > Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. > > More information: https://openeuler.org/en/ > > _______________________________________________ > Dev mailing list -- dev(a)openeuler.org > To unsubscribe send an email to dev-leave(a)openeuler.org > _______________________________________________ > Dev mailing list -- dev(a)openeuler.org > To unsubscribe send an email to dev-leave(a)openeuler.org

1 0

sig-zephyr2022年2月会议
by openEuler conference 11 Feb '22

11 Feb '22

您好！ sig-Zephyr SIG 邀请您参加 2022-02-13 22:00 召开的ZOOM会议会议主题：sig-zephyr2022年2月会议会议内容： 1. sig-Zephyr简介 2.Zephyr最新进展 3.sig-Zephyr2022计划 4.其他事项讨论，包括Zephyr使用上的答疑解惑会议链接：https://us06web.zoom.us/j/84575182341?pwd=ZmN1b3c4KzdoYTZEQk9yamt3OXFwZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-Zephyr SIG invites you to attend the ZOOM conference will be held at 2022-02-13 22:00, The subject of the conference is sig-zephyr2022年2月会议, Summary: 1. sig-Zephyr简介 2.Zephyr最新进展 3.sig-Zephyr2022计划 4.其他事项讨论，包括Zephyr使用上的答疑解惑 You can join the meeting at https://us06web.zoom.us/j/84575182341?pwd=ZmN1b3c4KzdoYTZEQk9yamt3OXFwZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

SIG-Cloudnative例会
by openEuler conference 11 Feb '22

11 Feb '22

您好！ sig-CloudNative SIG 邀请您参加 2022-02-15 16:00 召开的ZOOM会议(自动录制) 会议主题：SIG-Cloudnative例会会议内容： CloudNative SIG例会，欢迎大家积极申请议题会议链接：https://us06web.zoom.us/j/88106975696?pwd=M2RKWklKZ3pwVEVVWlBIWWViRkk4UT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-CloudNative SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-02-15 16:00, The subject of the conference is SIG-Cloudnative例会, Summary: CloudNative SIG例会，欢迎大家积极申请议题 You can join the meeting at https://us06web.zoom.us/j/88106975696?pwd=M2RKWklKZ3pwVEVVWlBIWWViRkk4UT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

Compiler SIG双周例会
by openEuler conference 11 Feb '22

11 Feb '22

您好！ Compiler SIG 邀请您参加 2022-02-15 10:00 召开的ZOOM会议(自动录制) 会议主题：Compiler SIG双周例会会议内容：欢迎上报议题，新增议题回复邮件即可会议链接：https://us06web.zoom.us/j/89695091580?pwd=aWZibDNCZTlxdE1ZRWp4dnRFbUFMQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler Compiler SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-02-15 10:00, The subject of the conference is Compiler SIG双周例会, Summary: 欢迎上报议题，新增议题回复邮件即可 You can join the meeting at https://us06web.zoom.us/j/89695091580?pwd=aWZibDNCZTlxdE1ZRWp4dnRFbUFMQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

2 1

【议题收集】//// openEuler release 双周例会
by Huangchengpiao 11 Feb '22

11 Feb '22

本周五上午openEuler release SIG例会。欢迎各位社区开发者踊跃申报议题~ -----Original Message----- From: openEuler conference [mailto:public@openeuler.org] Sent: Monday, February 7, 2022 5:23 PM Subject: [Dev] openEuler release 双周例会您好！ sig-release-management SIG 邀请您参加 2022-02-11 10:00 召开的ZOOM会议(自动录制) 会议主题：openEuler release 双周例会会议链接：https://us06web.zoom.us/j/86141460269?pwd=OEU0OEFRVjVBbGI4c20wNWlwZVJLZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-02-11 10:00, The subject of the conference is openEuler release 双周例会, You can join the meeting at https://us06web.zoom.us/j/86141460269?pwd=OEU0OEFRVjVBbGI4c20wNWlwZVJLZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/ _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org

3 4

小程序功能讨论
by openEuler conference 10 Feb '22

10 Feb '22

您好！ sig-OpenDesign SIG 邀请您参加 2022-02-11 10:00 召开的ZOOM会议会议主题：小程序功能讨论会议内容：讨论小程序新功能会议链接：https://us06web.zoom.us/j/82802085863?pwd=VDJWTTlwUGJEUEV4dXVNU2FMUmEvQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-OpenDesign SIG invites you to attend the ZOOM conference will be held at 2022-02-11 10:00, The subject of the conference is 小程序功能讨论, Summary: 讨论小程序新功能 You can join the meeting at https://us06web.zoom.us/j/82802085863?pwd=VDJWTTlwUGJEUEV4dXVNU2FMUmEvQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

OpenStack SIG例会
by openEuler conference 10 Feb '22

10 Feb '22

您好！ sig-openstack SIG 邀请您参加 2022-02-11 15:00 召开的ZOOM会议(自动录制) 会议主题：OpenStack SIG例会会议链接：https://us06web.zoom.us/j/85222921020?pwd=Ui9Qak9KaXdYNnhHMWlPNGlsMlZOZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-openstack SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-02-11 15:00, The subject of the conference is OpenStack SIG例会, You can join the meeting at https://us06web.zoom.us/j/85222921020?pwd=Ui9Qak9KaXdYNnhHMWlPNGlsMlZOZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

OpenDesign component 230
by openEuler conference 10 Feb '22

10 Feb '22

您好！ sig-OpenDesign SIG 邀请您参加 2022-02-11 15:00 召开的ZOOM会议会议主题：OpenDesign component 230 会议内容：确定230需要完成开发的组件会议链接：https://us06web.zoom.us/j/83769408877?pwd=a2hrMDhWOWRIb3Rqb25KalVSdURRdz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-OpenDesign SIG invites you to attend the ZOOM conference will be held at 2022-02-11 15:00, The subject of the conference is OpenDesign component 230, Summary: 确定230需要完成开发的组件 You can join the meeting at https://us06web.zoom.us/j/83769408877?pwd=a2hrMDhWOWRIb3Rqb25KalVSdURRdz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

【议题申报】//// openEuler release 双周例会
by xiasenlin 09 Feb '22

09 Feb '22

议题申报：openEuler-20.03-LTS-Next分支在出完最后一个SP3分支之后，实际上已处于闲置状态，既没有版本诉求也占用了一定的门禁资源，申请将该分支冻结，对应工程删除 -----Original Message----- From: wangyiru [mailto:wangyiru1@huawei.com] Sent: Wednesday, February 9, 2022 9:44 AM To: Huangchengpiao <huangchengpiao(a)huawei.com>; release <release(a)openeuler.org>; dev(a)openeuler.org Subject: [Release] 答复: 【议题收集】//// [Dev] openEuler release 双周例会议题申报：针对22.03 LTS中存在“上游社区不再更新和维护”或者“不支持python3”问题的相关软件包是否保留的用户需求搜集我们在做软件包选型的过程中，发现下列软件包存在“上游社区不再更新和维护”或者“不支持python3”的问题，因此考虑不在22.03 LTS版本中发布这些包。但是同时我们担忧openEuler社区的其他开发者、使用者和客户在22.03 LTS中仍然需要这些包，因此我们决定发起一场讨论（https://gitee.com/openeuler/community/issues/I4SHO… -----邮件原件----- 发件人: Huangchengpiao [mailto:huangchengpiao@huawei.com] 发送时间: 2022年2月7日 19:26 收件人: release <release(a)openeuler.org>; dev(a)openeuler.org 主题: [Release] 【议题收集】//// [Dev] openEuler release 双周例会本周五上午openEuler release SIG例会。欢迎各位社区开发者踊跃申报议题~ -----Original Message----- From: openEuler conference [mailto:public@openeuler.org] Sent: Monday, February 7, 2022 5:23 PM Subject: [Dev] openEuler release 双周例会您好！ sig-release-management SIG 邀请您参加 2022-02-11 10:00 召开的ZOOM会议(自动录制) 会议主题：openEuler release 双周例会会议链接：https://us06web.zoom.us/j/86141460269?pwd=OEU0OEFRVjVBbGI4c20wNWlwZVJLZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-02-11 10:00, The subject of the conference is openEuler release 双周例会, You can join the meeting at https://us06web.zoom.us/j/86141460269?pwd=OEU0OEFRVjVBbGI4c20wNWlwZVJLZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/ _______________________________________________ Dev mailing list -- dev(a)openeuler.org To unsubscribe send an email to dev-leave(a)openeuler.org _______________________________________________ Release mailing list -- release(a)openeuler.org To unsubscribe send an email to release-leave(a)openeuler.org _______________________________________________ Release mailing list -- release(a)openeuler.org To unsubscribe send an email to release-leave(a)openeuler.org

2 1

OpenDesign 2022开工会
by openEuler conference 09 Feb '22

09 Feb '22

您好！ sig-OpenDesign SIG 邀请您参加 2022-02-10 09:30 召开的ZOOM会议会议主题：OpenDesign 2022开工会会议内容： OpenDesign 2022年工作计划同步会议链接：https://us06web.zoom.us/j/82872919245?pwd=MGlNUXpyWlMreGx5ZmNaRkFqTVJZQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-OpenDesign SIG invites you to attend the ZOOM conference will be held at 2022-02-10 09:30, The subject of the conference is OpenDesign 2022开工会, Summary: OpenDesign 2022年工作计划同步 You can join the meeting at https://us06web.zoom.us/j/82872919245?pwd=MGlNUXpyWlMreGx5ZmNaRkFqTVJZQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

Re: 【议题收集】//// openEuler release 双周例会
by Huangchengpiao 09 Feb '22

09 Feb '22

收到。当前议题：议题1：针对22.03 LTS, DB(postrgresql, greenplum, neo4j, tidb)相关软件版本选择及是否保留的用户需求搜集 --- zhaobo 议题2，毕昇编译器简介 --- xingyushuai 欢迎社区小伙伴们继续申报议题~ -----Original Message----- From: xingyushuai Sent: Wednesday, February 9, 2022 9:24 AM To: Huangchengpiao <huangchengpiao(a)huawei.com>; bo zhaobo <bzhaojyathousandy(a)gmail.com>; release <release(a)openeuler.org>; dev(a)openeuler.org Cc: bule <bule1(a)huawei.com>; Zhangwen(Esan) <zwzhangwen.zhang(a)huawei.com> Subject: 答复: [Dev] 【议题收集】//// openEuler release 双周例会议题2，毕昇编译器简介 -----邮件原件----- 发件人: Huangchengpiao [mailto:huangchengpiao@huawei.com] 发送时间: 2022年2月8日 20:14 收件人: bo zhaobo <bzhaojyathousandy(a)gmail.com>; release <release(a)openeuler.org>; dev(a)openeuler.org 主题: [Release] Re: [Dev] 【议题收集】//// openEuler release 双周例会收到。议题1：针对22.03 LTS, DB(postrgresql, greenplum, neo4j, tidb)相关软件版本选择及是否保留的用户需求搜集 --- zhaobo 欢迎社区小伙伴们继续申报议题~ From: bo zhaobo [mailto:bzhaojyathousandy@gmail.com] Sent: Tuesday, February 8, 2022 5:18 PM To: Huangchengpiao <huangchengpiao(a)huawei.com> Cc: release <release(a)openeuler.org>; dev(a)openeuler.org Subject: Re: [Dev] 【议题收集】//// openEuler release 双周例会议题申报：针对22.03 LTS, DB(postrgresql, greenplum, neo4j, tidb)相关软件版本选择及是否保留的用户需求搜集针对即将到来的22.03 LTS，DB SIG很难判断是否还应该保留以下openEuler 22.03 LTS中DB相关的软件/库。所以我们考虑让他们公开投票或者在公开渠道收集客户/用户诉求，将根据我们得到的请求做出决定。请注意，提及到的软件都已经存在于openEuler 20.03 LTS中，需要在issue(https://gitee.com/openeuler/community/issues/I4SGDD?from=proj…<https://gitee.com/openeuler/community/issues/I4SGDD?from=project-issue)%E4%…>)。我们将在issue comments的基础上指导我们的工作。 1. greenplum (6.17.0) 2. postgresql / postgresql-13 (10.5) (13.3) 3. neo4j安装(4.3.0) 4. tidb (4.0.14) 请注意“问题评论格式”，请在这里留下你还需要的内容和要求的摘要内容。 https://gitee.com/openeuler/community/issues/I4SGDD?from=project-issue Huangchengpiao <huangchengpiao(a)huawei.com<mailto:huangchengpiao@huawei.com>> 于2022年2月7日周一 19:37写道：本周五上午openEuler release SIG例会。欢迎各位社区开发者踊跃申报议题~ -----Original Message----- From: openEuler conference [mailto:public@openeuler.org<mailto:public@openeuler.org>] Sent: Monday, February 7, 2022 5:23 PM Subject: [Dev] openEuler release 双周例会您好！ sig-release-management SIG 邀请您参加 2022-02-11 10:00 召开的ZOOM会议(自动录制) 会议主题：openEuler release 双周例会会议链接：https://us06web.zoom.us/j/86141460269?pwd=OEU0OEFRVjVBbGI4c20wNWlwZVJLZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com<http://gitee.com>的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-02-11 10:00, The subject of the conference is openEuler release 双周例会, You can join the meeting at https://us06web.zoom.us/j/86141460269?pwd=OEU0OEFRVjVBbGI4c20wNWlwZVJLZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com<http://gitee.com>. More information: https://openeuler.org/en/ _______________________________________________ Dev mailing list -- dev(a)openeuler.org<mailto:dev@openeuler.org> To unsubscribe send an email to dev-leave(a)openeuler.org<mailto:dev-leave@openeuler.org> _______________________________________________ Dev mailing list -- dev(a)openeuler.org<mailto:dev@openeuler.org> To unsubscribe send an email to dev-leave(a)openeuler.org<mailto:dev-leave@openeuler.org> _______________________________________________ Release mailing list -- release(a)openeuler.org To unsubscribe send an email to release-leave(a)openeuler.org

1 0

安全委员会例会
by openEuler conference 08 Feb '22

08 Feb '22

您好！ security-committee SIG 邀请您参加 2022-02-09 16:00 召开的ZOOM会议(自动录制) 会议主题：安全委员会例会会议内容： 2022年春节后首次例会。会议链接：https://us06web.zoom.us/j/86428114479?pwd=NXZHY3BlcWhYQmlGck9OQlFQQU90Zz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler security-committee SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-02-09 16:00, The subject of the conference is 安全委员会例会, Summary: 2022年春节后首次例会。 You can join the meeting at https://us06web.zoom.us/j/86428114479?pwd=NXZHY3BlcWhYQmlGck9OQlFQQU90Zz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

openEuler 技术委员会例会
by openEuler conference 08 Feb '22

08 Feb '22

您好！ TC SIG 邀请您参加 2022-02-09 10:00 召开的ZOOM会议会议主题：openEuler 技术委员会例会会议链接：https://us06web.zoom.us/j/88532113689?pwd=RXBTeENQUVVHKzZ2T2liai9kMHBOdz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler TC SIG invites you to attend the ZOOM conference will be held at 2022-02-09 10:00, The subject of the conference is openEuler 技术委员会例会, You can join the meeting at https://us06web.zoom.us/j/88532113689?pwd=RXBTeENQUVVHKzZ2T2liai9kMHBOdz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

2 1

openEuler release 双周例会
by openEuler conference 07 Feb '22

07 Feb '22

您好！ sig-release-management SIG 邀请您参加 2022-02-11 10:00 召开的ZOOM会议(自动录制) 会议主题：openEuler release 双周例会会议链接：https://us06web.zoom.us/j/86141460269?pwd=OEU0OEFRVjVBbGI4c20wNWlwZVJLZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-02-11 10:00, The subject of the conference is openEuler release 双周例会, You can join the meeting at https://us06web.zoom.us/j/86141460269?pwd=OEU0OEFRVjVBbGI4c20wNWlwZVJLZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

[PATCH] e2fsck: exit journal recovery when jounral superblock fails to update
by Zhiqiang Liu 30 Jan '22

30 Jan '22

Jounral superblock may be failed to update in e2fsck_journal_release. But if needs_recovery flag is cleared, e2fsck_check_ext3_journal will be failed. To fix this case, we use "fatal_error" when recover journal failed. So we can reserve the recovery flag to recover the journal when try e2fsck again. Fix issue:https://gitee.com/src-openeuler/e2fsprogs/issues/I4S0SD?from=project-… Reported-by: Liangyun <liangyun2(a)huawei.com> Signed-off-by: Liangyun <liangyun2(a)huawei.com> --- e2fsck/journal.c | 26 ++++++++++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/e2fsck/journal.c b/e2fsck/journal.c index df4f354..a9b5b51 100644 --- a/e2fsck/journal.c +++ b/e2fsck/journal.c @@ -757,10 +757,12 @@ static errcode_t e2fsck_journal_fix_corrupt_super(e2fsck_t ctx, return 0; } -static void e2fsck_journal_release(e2fsck_t ctx, journal_t *journal, +static errcode_t e2fsck_journal_release(e2fsck_t ctx, journal_t *journal, int reset, int drop) { journal_superblock_t *jsb; + errcode_t err = 0; + errcode_t err2; if (drop) mark_buffer_clean(journal->j_sb_buffer); @@ -774,6 +776,16 @@ static void e2fsck_journal_release(e2fsck_t ctx, journal_t *journal, } brelse(journal->j_sb_buffer); + if(reset == 1 && drop == 0) { + err = sync_blockdev(journal->j_fs_dev); + /* Make sure all replayed data is on permanent storage */ + if (journal->j_flags & JFS_BARRIER) { + err2 = blkdev_issue_flush(journal->j_fs_dev, GFP_KERNEL, NULL); + if (!err) + err = err2; + } + } + if (ctx->journal_io) { if (ctx->fs && ctx->fs->io != ctx->journal_io) io_channel_close(ctx->journal_io); @@ -787,6 +799,8 @@ static void e2fsck_journal_release(e2fsck_t ctx, journal_t *journal, if (journal->j_fs_dev) ext2fs_free_mem(&journal->j_fs_dev); ext2fs_free_mem(&journal); + + return err; } /* @@ -925,6 +939,7 @@ static errcode_t recover_ext3_journal(e2fsck_t ctx) struct problem_context pctx; journal_t *journal; errcode_t retval; + errcode_t recover_retval; clear_problem_context(&pctx); @@ -964,7 +979,14 @@ static errcode_t recover_ext3_journal(e2fsck_t ctx) errout: journal_destroy_revoke(journal); journal_destroy_revoke_caches(); - e2fsck_journal_release(ctx, journal, 1, 0); + recover_retval = e2fsck_journal_release(ctx, journal, 1, 0); + if(recover_retval == -EIO) { + ctx->fs->flags &= ~EXT2_FLAG_VALID; + com_err(ctx->program_name, 0, + _("e2fsck journal release failed " + "on %s, retval=%d \n"), ctx->device_name, recover_retval); + fatal_error(ctx, 0); + } return retval; } -- 1.8.3.1

1 0

[PATCH] e2fsck: add env param E2FS_UNRELIABLE_IO to fix unreliable io case
by Zhiqiang Liu 30 Jan '22

30 Jan '22

Func write_primary_superblock() has two way to wirte disk. One is 1k block, the other is byte by byte as default. On unreliable IO case such as flaky network, the byte-by-byte method may lost some data of ext4-superblock. Then, the superblock may lose consistency and the sb checksum error will occur. We provide the env param E2FS_UNRELIABLE_IO for users to choose if it's necessary to take 1k block way on writing disk. Fix issue:https://gitee.com/src-openeuler/e2fsprogs/issues/I4RZVX?from=project-… Signed-off-by: Haotian Li <lihaotian9(a)huawei.com> Signed-off-by: Zhiqiang Liu <liuzhiqiang26(a)huawei.com> --- lib/ext2fs/closefs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lib/ext2fs/closefs.c b/lib/ext2fs/closefs.c index 1d4d5b7..1893fb6 100644 --- a/lib/ext2fs/closefs.c +++ b/lib/ext2fs/closefs.c @@ -195,8 +195,9 @@ static errcode_t write_primary_superblock(ext2_filsys fs, __u16 *old_super, *new_super; int check_idx, write_idx, size; errcode_t retval; + int is_unreliable_io = getenv("E2FS_UNRELIABLE_IO") ? 1 : 0; - if (!fs->io->manager->write_byte || !fs->orig_super) { + if (!fs->io->manager->write_byte || !fs->orig_super || is_unreliable_io) { fallback: io_channel_set_blksize(fs->io, SUPERBLOCK_OFFSET); retval = io_channel_write_blk64(fs->io, 1, -SUPERBLOCK_SIZE, -- 2.23.0

1 0

[PATCH] e2fsck: exit journal recovery when find EIO, ENOMEM errors
by Zhiqiang Liu 30 Jan '22

30 Jan '22

jbd2_journal_revocer() may fail when some error occers such as ENOMEM. However, jsb->s_start is still cleared by func e2fsck_journal_release(). This may break consistency between metadata and data in disk. Sometimes, failure in jbd2_journal_revocer() is temporary but retry e2fsck will skip the journal recovery when the temporary problem is fixed. To fix this case, we use "fatal_error" instead "goto errout" when recover journal failed. If journal recovery fails, we will send error message to user and reserve the recovery flags to recover the journal when try e2fsck again. Fix issue: https://gitee.com/src-openeuler/e2fsprogs/issues/I4RZUT?from=project-issue Reported-by: Liangyun <liangyun2(a)huawei.com> Signed-off-by: Haotian Li <lihaotian9(a)huawei.com> Signed-off-by: Zhiqiang Liu <liuzhiqiang26(a)huawei.com> --- e2fsck/journal.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/e2fsck/journal.c b/e2fsck/journal.c index e83f3a9..df4f354 100644 --- a/e2fsck/journal.c +++ b/e2fsck/journal.c @@ -942,6 +942,13 @@ static errcode_t recover_ext3_journal(e2fsck_t ctx) goto errout; retval = -journal_recover(journal); + if (retval == EIO || retval == ENOMEM || retval == EXT2_ET_NO_MEMORY) { + ctx->fs->flags &= ~EXT2_FLAG_VALID; + com_err(ctx->program_name, 0, + _("Journal recovery failed " + "on %s, retval=%d \n"), ctx->device_name, retval); + fatal_error(ctx, 0); + } if (retval) goto errout; -- 1.8.3.1 ~

1 0

【会议纪要】RE: Re: Compiler SIG双周例会
by xiezhiheng 29 Jan '22

29 Jan '22

会议纪要 MEETING MINUTES 主题 Subject Compiler SIG双周例会时间 Date & Time 2022年01月25日星期二 10:00-11:00 地点 Location 线上会议与会者 Attendees Shaka（龙芯），rocky，本杰明，孙海勇（龙芯），谢志恒（华为），郭培林（华为），伊金静（华为），高翔（麒麟），郭策（麒麟），金旭（麒麟），李星，陆伟宁（龙芯），崔玉栋（麒麟），刘旸（麒麟），王铭（麒麟），王强，王硕（麒麟），尹泽浩，张玉龙等纪要者 Note Taker 谢志恒议题一： GCC支持龙芯策略讨论（谢志恒，孙海勇） 1. openEuler GCC启用社区化开发模式，使用issue+PR，源码仓+制品仓方式管理 2. GCC 10.3（openEuler 22.03）支持龙芯架构特性支持，龙芯同事正在迁移测试，需要一定迁移时间议题二： LLVM和clang支持龙芯策略讨论（谢志恒，孙海勇，郭培林） 1. openEuler 22.03搭配LLVM 12.0.1版本，龙芯同事目前维护LLVM 8.0.1和11.0.1龙芯架构后端，因人力资源问题，无法长期支撑维护LLVM 12.0.1版本 2. 初步定下方案，在openEuler 22.03中引入LLVM 11.1.0单独支持龙芯架构，其余架构仍用LLVM 12.0.1版本 3. 目前LLVM和clang会支持龙芯架构，后续计划有compiler-rt、lld等组件将支持龙芯架构遗留问题： LLVM和clang支持龙芯方案 1. openEuler 22.03龙芯架构下需要提前全量测试使用LLVM编译的组件，提前识别LLVM 11.1.0兼容性问题 -- 郭培林 2. 向TC会议汇报并评审该解决方案 -- 郭培林分享资料见附件。会议录屏已自动上传至B站: https://www.bilibili.com/video/BV19L4y1s75X > -----Original Message----- > From: xiezhiheng [mailto:xiezhiheng@huawei.com] > Sent: Friday, January 21, 2022 5:22 PM > To: openEuler conference <public(a)openeuler.org>; dev(a)openeuler.org; > pengchenghan <pengchenghan(a)huawei.com>; hedongbo > <hedongbo(a)huawei.com>; yijinjing <yijinjing(a)huawei.com>; wangding (C) > <wangding16(a)huawei.com> > Subject: [Dev] Re: Compiler SIG双周例会 > > 议题申报： > GCC支持龙芯策略讨论： > > 1、简单介绍openEuler GCC仓目前运作模式 > 2、龙芯适配策略的讨论 > > > -----Original Message----- > > From: openEuler conference [mailto:public@openeuler.org] > > Sent: Friday, January 21, 2022 2:29 PM > > To: dev(a)openeuler.org<mailto:dev@openeuler.org>; pengchenghan <pengchenghan(a)huawei.com<mailto:pengchenghan@huawei.com>>; > > hedongbo <hedongbo(a)huawei.com<mailto:hedongbo@huawei.com>>; yijinjing <yijinjing(a)huawei.com<mailto:yijinjing@huawei.com>> > > Subject: [Dev] Compiler SIG双周例会 > > > > 您好！ > > > > Compiler SIG 邀请您参加 2022-01-25 10:00 召开的ZOOM会议(自动录制) > > > > 会议主题：Compiler SIG双周例会 > > > > 会议链接： > > > https://us06web.zoom.us/j/83419109921?pwd=ZzFWZEx3SGhtTVU0dWZvcmJLa > > 3NSQT09 > > > > 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com > 的 > > ID > > > > 更多资讯尽在：https://openeuler.org/zh/ > > > > > > > > > > Hello! > > > > openEuler Compiler SIG invites you to attend the ZOOM conference(auto > > recording) will be held at 2022-01-25 10:00, > > > > The subject of the conference is Compiler SIG双周例会, > > > > You can join the meeting at > > > https://us06web.zoom.us/j/83419109921?pwd=ZzFWZEx3SGhtTVU0dWZvcmJLa > > 3NSQT09. > > > > Note: You are advised to change the participant name after joining the > > conference or use your ID at gitee.com. > > > > More information: https://openeuler.org/en/ > > > > _______________________________________________ > > Dev mailing list -- dev(a)openeuler.org<mailto:dev@openeuler.org> > > To unsubscribe send an email to dev-leave(a)openeuler.org<mailto:dev-leave@openeuler.org> > _______________________________________________ > Dev mailing list -- dev(a)openeuler.org<mailto:dev@openeuler.org> > To unsubscribe send an email to dev-leave(a)openeuler.org<mailto:dev-leave@openeuler.org>

1 0

glusterfs 22.03-LTS删除子包说明
by haowenchao 29 Jan '22

29 Jan '22

Hi All: 软件包glusterfs升级到10.0版本引入两个子包（glusterfs-ganesha和glusterfs-regression），这两个子包依赖的rpm在openeuler中没有提供，导致子包无法正常使用，将会删除这两个子包。 glusterfs-regression是回归测试用的子包；glusterfs-ganesha 是基于NFS-Ganesh提供使用glusterfs作为NFS服务端的功能， openeuler没有提供NFS-Ganesh，故glusterfs-ganesha也无法使用。如果有人使用到了上述子包，请在https://gitee.com/src-openeuler/glusterfs提issue跟踪讨论。

1 0

[release][DISCUSS]下列软件包是否需要在22.03 LTS发布，邀请大家参与讨论并反馈意见
by wangyiru 29 Jan '22

29 Jan '22

各位社区开发者，大家好：我们在做软件包选型的过程中，发现下列软件包存在“上游社区不再更新和维护”或者“不支持python3”的问题，因此考虑不在22.03 LTS版本中发布这些包。但是同时我们担忧openEuler社区的其他开发者、使用者和客户在22.03 LTS中仍然需要这些包，因此我们决定发起一场讨论（https://gitee.com/openeuler/community/issues/I4SHO… 这些软件包主要分为三类：一、上游社区已经不维护的包： 1．cookxml(3.0.2) 所属sig组：Application 上游社区地址：https://sourceforge.net/projects/cookxml/files/ 2．crda(3.18_2018.05.31) 所属sig组：System-tool 上游社区地址：http://www.kernel.org/pub/software/network/crda 3．libkml(1.3.0) 所属sig组：Application 上游社区地址：https://github.com/libkml/libkml 4．libpng12(1.2.57) 所属sig组：Runtime 上游社区地址：https://sourceforge.net/projects/libpng/files/libpng12/ 5．python-which(1.1.0) 所属sig组：Programming-language 上游社区地址：https://code.google.com/archive/p/which/downloads 6．cowsay(3.04) 所属sig组：Application 上游社区地址：https://github.com/tnalpgge/rank-amateur-cowsay 7．perl-File-Pid(1.01) 所属sig组：sig-perl-modules上游社区地址：https://metacpan.org/dist/File-Pid 8．perl-FreezeThaw(0.5001) 所属sig组：sig-perl-modules 上游社区地址：http://search.cpan.org/dist/FreezeThaw/ 9．pwgen(2.08) 所属sig组：Application 上游社区地址：https://sourceforge.net/projects/pwgen/ 10．python-django-babel(0.6.2) 所属sig组：sig-python-modules 上游社区地址：https://github.com/python-babel/django-babel/ 11．python-multi_key_dict(2.0.3) 所属sig组：sig-python-modules 上游社区地址：https://github.com/formiaczek/multi_key_dict 12．python-unicodecsv(0.14.1) 所属sig组：sig-python-modules 上游社区地址：https://github.com/jdunck/python-unicodecsv 二、依赖python2的由于已经剔除Python2所以不计划放入版本的包： 1． python-futures(3.1.1) 所属sig组：Programming-language 上游社区地址：https://github.com/agronholm/pythonfutures 2． python2-typing(3.6.2) python-typing替换了python2-typing 所属sig组：Programming-language 上游社区地址：https://github.com/python/typing 3． Pyorbit(2.24.0) 所属sig组：sig-python-modules 上游社区地址：https://download.gnome.org/sources/pyorbit/ 4． python-subprocess32(3.2.7) 所属sig组：sig-python-modules 上游社区地址：https://github.com/google/python-subprocess32 5． python-CouchDB(1.2) python-cloudant替换了python-CouchDB，但是根据上游信息，python-cloudant在2021年12月31日也已经停止更新所属sig组：sig-python-modules 上游社区地址：https://github.com/djc/couchdb-python/ 6． pygobject2(2.28.7) 所属sig组：Programming-language 上游社区地址：https://download.gnome.org/sources/pygobject/ 7． pygtk2(2.24.0) 所属sig组：Programming-language 上游社区地址：https://download.gnome.org/sources/pygtk/ 8． gimp(2.10.6) 同时依赖pygobject2，pygtk2和python2三个包所属sig组：Others 上游社区地址：http://download.gimp.org/pub/gimp 9. qtwebkit(2.3.4) 所属sig组：Others 上游社区地址：http://trac.webkit.org/wiki/QtWebKit 三、依赖recycle的jasper，所以不计划放入版本的包 1． g2clib(1.6.0) 所属sig组：Application 上游社区地址：http://www.nco.ncep.noaa.gov/pmb/codes/GRIB2/ 若您对上述软件包仍有述求，请在issue中留下您仍然需要的包并详细说明。非常感谢！ best withes，汪奕如（Yiru Wang）华为技术有限公司 Tel : +86 18463108086 Email : wangyiru1(a)huawei.com [cid:image001.png@01D814F2.00C5BDF0] This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

1 0

[DISCUSS][DB] Collect and Discuss whether reserve the mentioned DB software/libraries in the following openEuler 22.03
by bo zhaobo 29 Jan '22

29 Jan '22

Hi guys, I'm from DB SIG, currently, everyone in openEuler is busying in the development. And we also face some questions need to be clear, so we want to collect some ideas from openEuler community, customers and users. We are difficult to judge whether we should still reserve the following DB related software/library in openEuler 22.03 LTS. So we consider to make them vote in public ,direct us to make the decision according to the requests we will get. Note that the mentioned ones are in openEuler 20.03 LTS, you guys need to leave your comment(request) in the issue( https://gitee.com/openeuler/community/issues/I4SGDD?from=project-issue) We will leverage our work based on the issue comments. 1. greenplum(6.17.0) 2. postgresql(10.5)/postgresql-13(13.3) 3. neo4j (4.3.0) 4. tidb (4.0.14) Note that "issue comment format", please leave which ones you still need and request summarized content there. Thanks very much. Bo Zhao BR, DB SIG

3 4

[DISCUSS][DB] Collect and Discuss whether reserve the mentioned DB software/libraries in the following openEuler 22.03
by 270162781＠qq.com 28 Jan '22

28 Jan '22

Hi guys, I'm from DB SIG, currently, every one in openEuler is busying in the development. And we also face some questions need to be clear, so we want to collect some ideas from openEuler community, customers and users. We are difficult to judge whether we should still reserve the following DB related software/library in openEuler 22.03 LTS. So we consider to make them vote in public ,direct us to make the decision according to the requests we will get. Notes that the mentioned ones are in openEuler 20.03 LTS, you guys need to leave your comment(request) in the issue(https://gitee.com/openeuler/community/issues/I4SGDD?from=project-issu…. We will leverage our work based on the issue comments. 1. greenplum(6.17.0) 2. postgresql(10.5)/postgresql-13(13.3) 3. neo4j (4.3.0) 4. tidb (4.0.14) Notes that "issue comment format", please leave which ones you still need and request summarized content there. Thanks very much. Bo Zhao BR, DB SIG

1 0

可重复构建讨论
by openEuler conference 28 Jan '22

28 Jan '22

您好！ sig-CICD SIG 邀请您参加 2022-01-28 10:30 召开的ZOOM会议(自动录制) 会议主题：可重复构建讨论会议内容：可重复构建讨论会议链接：https://us06web.zoom.us/j/83593171861?pwd=bVBleEhDbFZ3ejhieHAycHorN01nQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-CICD SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-01-28 10:30, The subject of the conference is 可重复构建讨论, Summary: 可重复构建讨论 You can join the meeting at https://us06web.zoom.us/j/83593171861?pwd=bVBleEhDbFZ3ejhieHAycHorN01nQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

SIG 运营辅导计划 - 2021 SIG Operations Coaching Program
by Quanyi Ma 27 Jan '22

27 Jan '22

Hi Dev，根据 1 月 26 日技术委员会的会议，计划对社区部分 SIG 在 Q1 进行第一轮运营辅导，由技术委员会和社区技术专家对 SIG 进行一对一辅导。分工如下 1. sig-OKD <https://gitee.com/openeuler/community/tree/master/sig/sig-OKD> - 候健 2. sig-libboundscheck <https://gitee.com/openeuler/community/tree/master/sig/sig-libboundscheck> - 胡欣慰 3. sig-Migration <https://gitee.com/openeuler/community/tree/master/sig/sig-Migration> - 叶青龙 4. sig-HPC <https://gitee.com/openeuler/community/tree/master/sig/sig-HPC> - 熊伟 5. sig-KubeSphere <https://gitee.com/openeuler/community/tree/master/sig/sig-KubeSphere> - 候健 6. sig-CICD <https://gitee.com/openeuler/community/tree/master/sig/sig-CICD> - 吴峰光 7. sig-DyscheOS <https://gitee.com/openeuler/community/tree/master/sig/sig-DyscheOS> - 熊伟 8. sig-Ostree-Assembly <https://gitee.com/openeuler/community/tree/master/sig/sig-Ostree-Assembly> - 石勇 9. sig-OSCourse <https://gitee.com/openeuler/community/tree/master/sig/sig-OSCourse> - 马全一 10. sig-cms <https://gitee.com/openeuler/community/tree/master/sig/sig-cms> - 王建民 11. sig-REDF <https://gitee.com/openeuler/community/tree/master/sig/sig-REDF> - 胡欣慰 12. sig-ONL <https://gitee.com/openeuler/community/tree/master/sig/sig-ONL> - 熊伟在春节假期后的技术委员会会议上，计划请各位 SIG 组 Maintainer 代表陆续在会议上陈述一下 SIG 的工作计划。 --- According to the Technical Committee meeting on January 26, we plan to conduct the first round of operational coaching for some SIGs in the community in Q1, and the Technical Committee and community technical experts will conduct one-on-one coaching for SIGs. 1. sig-OKD <https://gitee.com/openeuler/community/tree/master/sig/sig-OKD> - Jian Hou 2. sig-libboundscheck <https://gitee.com/openeuler/community/tree/master/sig/sig-libboundscheck> - Xinwei Hu 3. sig-Migration <https://gitee.com/openeuler/community/tree/master/sig/sig-Migration> - Qinglong Ye 4. sig-HPC <https://gitee.com/openeuler/community/tree/master/sig/sig-HPC> - Wei Xiong 5. sig-KubeSphere <https://gitee.com/openeuler/community/tree/master/sig/sig-KubeSphere> - Jian Hou 6. sig-CICD <https://gitee.com/openeuler/community/tree/master/sig/sig-CICD> - Fengguang Wu 7. sig-DyscheOS <https://gitee.com/openeuler/community/tree/master/sig/sig-DyscheOS> - Wei Xiong 8. sig-Ostree-Assembly <https://gitee.com/openeuler/community/tree/master/sig/sig-Ostree-Assembly> - Yong Shi 9. sig-OSCourse <https://gitee.com/openeuler/community/tree/master/sig/sig-OSCourse> - Quanyi Ma 10. sig-cms <https://gitee.com/openeuler/community/tree/master/sig/sig-cms> - Jianmin Wang 11. sig-REDF <https://gitee.com/openeuler/community/tree/master/sig/sig-REDF> - Xinwei Hu 12. sig-ONL <https://gitee.com/openeuler/community/tree/master/sig/sig-ONL> - Wei Xiong At the Technical Committee meeting after the Spring Festival, we plan to invite the SIG Maintainers to present the SIG's status and plan at the meeting. Best regards, -- Quanyi Ma <eli(a)patch.sh>

2 1

compass-ci job field字段说明
by openEuler conference 27 Jan '22

27 Jan '22

您好！ sig-CICD SIG 邀请您参加 2022-01-27 11:00 召开的ZOOM会议(自动录制) 会议主题：compass-ci job field字段说明会议内容： 1.compass-ci job field字段说明 2.性能差异解决方案讨论会议链接：https://us06web.zoom.us/j/85773766235?pwd=UXVVQlp1d3pCNWVBQVhJZWRLVEFvQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-CICD SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-01-27 11:00, The subject of the conference is compass-ci job field字段说明, Summary: 1.compass-ci job field字段说明 2.性能差异解决方案讨论 You can join the meeting at https://us06web.zoom.us/j/85773766235?pwd=UXVVQlp1d3pCNWVBQVhJZWRLVEFvQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

openEuler release sig补充例会
by openEuler conference 26 Jan '22

26 Jan '22

您好！ sig-release-management SIG 邀请您参加 2022-01-28 10:00 召开的ZOOM会议(自动录制) 会议主题：openEuler release sig补充例会会议内容：讨论迁移软件清单会议链接：https://us06web.zoom.us/j/82734546609?pwd=U0JrVitsOTZQUlRBV0d0THVVM1BBZz09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-01-28 10:00, The subject of the conference is openEuler release sig补充例会, Summary: 讨论迁移软件清单 You can join the meeting at https://us06web.zoom.us/j/82734546609?pwd=U0JrVitsOTZQUlRBV0d0THVVM1BBZz09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

[native-turbo][glibc] elf: dynamic linker load lib use hugepage
by Zhoukang (A) 26 Jan '22

26 Jan '22

1 0

openEuler release sig maintainer增选信息公示
by Hufeng (Solar, Euler) 26 Jan '22

26 Jan '22

release sig 2022年1月21日经过maintainer 胡峰推选，会议评审同意黄城飘成为release sig maintainer 信息公示期为公示期2022年1月21日至2022年1月26日，公示期欢迎大家反馈意见相关PR如下 https://gitee.com/openeuler/community/pulls/3164 议题4：release management sig变更及新增maintainer提名--hufeng/huangchengpiao --release maintainer竞选流程及原则 --由maintainer和扩展成员提名（个人先向以上成员提出申请），release sig评审 ---1.个人或者所属团队，连续6个月以上对社区有持续贡献，且至少有一个特性为版本关键特性（存在于release notes） ---2.持续参加release sig例会，近6个月与会率70%以上 ---3.对版本release管理有突出贡献（自我举证） --release maintianer变更流程及原则 --主动提出或者release提出，release sig评审 ---1.主动退出或者连续6次以上无故不参与release sig例会 ---2.个人或者所属团队，连续6个月无社区贡献 --本规范从2022年1月21日起发布，公示和评审期22个工作日，2022年2月24日截止 ---1.本次提名黄诚飘为release maintainer ---2.原有release maintainer Zhu Yanpeng @zyp-rock由于工作调整原因，个人辞去maintainer角色，本次建议调整到扩展成员，连续三次会议无反对意见后，退出release sig --黄城飘竞选openEuler release sig maintainer提名投票（公示期2022年1月21日至2022年1月26日），26日上TC报备 --胡峰：同意 --陈亚强：同意 --李永强：同意 --明沛：同意 --张伟（议题驱动）：缺席 [cid:image001.png@01D81297.EC843A80]

1 0

加入Dev邮件列表
by liangwenhao0603＠163.com 26 Jan '22

26 Jan '22

这是一封申请邮件

1 0

openEuler工程能力介绍-效率提升工具
by openEuler conference 26 Jan '22

26 Jan '22

您好！ sig-release-management SIG 邀请您参加 2022-01-27 10:00 召开的ZOOM会议(自动录制) 会议主题：openEuler工程能力介绍-效率提升工具会议内容：介绍openEuler提供的效率提升工具会议链接：https://us06web.zoom.us/j/85158236290?pwd=eDR0TVNrdy85NzkvaWw1Vys1V1oyUT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-release-management SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-01-27 10:00, The subject of the conference is openEuler工程能力介绍-效率提升工具, Summary: 介绍openEuler提供的效率提升工具 You can join the meeting at https://us06web.zoom.us/j/85158236290?pwd=eDR0TVNrdy85NzkvaWw1Vys1V1oyUT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

2 1

TC双周例会
by openEuler conference 25 Jan '22

25 Jan '22

您好！ TC SIG 邀请您参加 2022-01-26 10:00 召开的ZOOM会议(自动录制) 会议主题：TC双周例会会议内容： TC双周例会，请大家申报议题会议链接：https://us06web.zoom.us/j/86208821099?pwd=VjJoTHlBcTlMc1FNb2Y1bnlDeGdNQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler TC SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-01-26 10:00, The subject of the conference is TC双周例会, Summary: TC双周例会，请大家申报议题 You can join the meeting at https://us06web.zoom.us/j/86208821099?pwd=VjJoTHlBcTlMc1FNb2Y1bnlDeGdNQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

3 2

2203 LTS版本测试策略评审
by openEuler conference 25 Jan '22

25 Jan '22

您好！ sig-QA SIG 邀请您参加 2022-01-26 14:15 召开的ZOOM会议(自动录制) 会议主题：2203 LTS版本测试策略评审会议链接：https://us06web.zoom.us/j/82825436195?pwd=bEVVd0tHeFRLbVR4RzJxRW9wdEJFQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-QA SIG invites you to attend the ZOOM conference(auto recording) will be held at 2022-01-26 14:15, The subject of the conference is 2203 LTS版本测试策略评审, You can join the meeting at https://us06web.zoom.us/j/82825436195?pwd=bEVVd0tHeFRLbVR4RzJxRW9wdEJFQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

G11N SIG 双周例会
by openEuler conference 25 Jan '22

25 Jan '22

您好！ G11N SIG 邀请您参加 2022-01-28 10:00 召开的ZOOM会议会议主题：G11N SIG 双周例会会议内容：全球化平台进展会议链接：https://us06web.zoom.us/j/89605448215?pwd=eW40dlN4OEdETGluVHJIS1dkQUxuQT09 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler G11N SIG invites you to attend the ZOOM conference will be held at 2022-01-28 10:00, The subject of the conference is G11N SIG 双周例会, Summary: 全球化平台进展 You can join the meeting at https://us06web.zoom.us/j/89605448215?pwd=eW40dlN4OEdETGluVHJIS1dkQUxuQT09. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0