January 2022 - Dev - mailweb.openeuler.org

23 Apr '22

Hi 您好，先自我介绍下，我叫叶金荣，专注MySQL领域超过20年，基本上是国内最早的一批MySQL从业者，一直致力于在国内推广MySQL。同时我也是Oracle MySQL ACE Director及腾讯云TVP成员。我个人网站：imysql.com，微信公众号：老叶茶馆，经常会有MySQL相关原创文章、视频等分享。我对openeuler项目中的DB SIG比较感兴趣，因此想加入。看了下openeuler DB SIG的gitee仓库，目前似乎还都是空的，不太了解具体要怎么加入，所以冒昧发此邮件。盼回复，谢谢。

3 2

[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