Sign in
Sign up
Explore
Enterprise
Education
Search
Help
Terms of use
About Us
Explore
Enterprise
Education
Gitee Premium
Gitee AI
AI teammates
Sign in
Sign up
Fetch the repository succeeded.
description of repo status
Open Source
>
Other
>
Operation System
&&
Watch
Unwatch
Watching
Releases Only
Ignoring
128
Star
73
Fork
331
src-openEuler
/
kernel
Closed
Code
Issues
1197
Pull Requests
35
Wiki
Insights
Pipelines
Service
JavaDoc
PHPDoc
Quality Analysis
Jenkins for Gitee
Tencent CloudBase
Tencent Cloud Serverless
悬镜安全
Aliyun SAE
Codeblitz
SBOM
DevLens
Don’t show this again
Update failed. Please try again later!
Remove this flag
Content Risk Flag
This task is identified by
as the content contains sensitive information such as code security bugs, privacy leaks, etc., so it is only accessible to contributors of this repository.
CVE-2024-50175
Done
#IB2YV9
CVE和安全问题
openeuler-ci-bot
owner
Opened this issue
2024-11-08 14:33
一、漏洞信息 漏洞编号:[CVE-2024-50175](https://nvd.nist.gov/vuln/detail/CVE-2024-50175) 漏洞归属组件:[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0 CVSS V3.0分值: BaseScore:5.5 Medium Vector:CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:media: qcom: camss: Remove use_count guard in stop_streamingThe use_count check was introduced so that multiple concurrent Raw DataInterfaces RDIs could be driven by different virtual channels VCs on theCSIPHY input driving the video pipeline.This is an invalid use of use_count though as use_count pertains to thenumber of times a video entity has been opened by user-space not the numberof active streams.If use_count and stream-on count don t agree then stop_streaming() willbreak as is currently the case and has become apparent when using CAMSSwith libcamera s released softisp 0.3.The use of use_count like this is a bit hacky and right now breaks regularusage of CAMSS for a single stream case. Stopping qcam results in the splatbelow, and then it cannot be started again and any attempts to do so failswith -EBUSY.[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]...[ 1265.510630] Call trace:[ 1265.510636] __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common][ 1265.510648] vb2_core_streamoff+0x24/0xcc [videobuf2_common][ 1265.510660] vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2][ 1265.510673] v4l_streamoff+0x24/0x30 [videodev][ 1265.510707] __video_do_ioctl+0x190/0x3f4 [videodev][ 1265.510732] video_usercopy+0x304/0x8c4 [videodev][ 1265.510757] video_ioctl2+0x18/0x34 [videodev][ 1265.510782] v4l2_ioctl+0x40/0x60 [videodev]...[ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state[ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state[ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active stOne CAMSS specific way to handle multiple VCs on the same RDI might be:- Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.- The video buffers are already associated with msm_vfeN_rdiX so release video buffers when told to do so by stop_streaming.- Only release the power-domains for the CSIPHY, CSID and VFE when their internal refcounts drop.Either way refusing to release video buffers based on use_count iserroneous and should be reverted. The silicon enabling code for selectingVCs is perfectly fine. Its a known missing feature that concurrent VCswon t work with CAMSS right now.Initial testing with this code didn t show an error but, SoftISP and real usage with Google Hangouts breaks the upstream code pretty quickly, we needto do a partial revert and take another pass at VCs.This commit partially reverts commit 89013969e232 ( media: camss: sm8250:Pipeline starting and stopping for multiple virtual channels ) 漏洞公开时间:2024-11-08 14:15:14 漏洞创建时间:2024-11-08 14:33:51 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2024-50175 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-50175 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-50175 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-50175.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | debian | | https://security-tracker.debian.org/tracker/CVE-2024-50175 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | | | https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27 | | nvd | | | | https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3 | | nvd | | | | https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9 | | nvd | | | | https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee | | nvd | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:media: qcom: camss: Remove use_count guard in stop_streamingThe use_count check was introduced so that multiple concurrent Raw DataInterfaces RDIs could be driven by different virtual channels VCs on theCSIPHY input driving the video pipeline.This is an invalid use of use_count though as use_count pertains to thenumber of times a video entity has been opened by user-space not the numberof active streams.If use_count and stream-on count don t agree then stop_streaming() willbreak as is currently the case and has become apparent when using CAMSSwith libcamera s released softisp 0.3.The use of use_count like this is a bit hacky and right now breaks regularusage of CAMSS for a single stream case. Stopping qcam results in the splatbelow, and then it cannot be started again and any attempts to do so failswith -EBUSY.[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]...[ 1265.510630] Call trace:[ 1265.510636] __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common][ 1265.510648] vb2_core_streamoff+0x24/0xcc [videobuf2_common][ 1265.510660] vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2][ 1265.510673] v4l_streamoff+0x24/0x30 [videodev][ 1265.510707] __video_do_ioctl+0x190/0x3f4 [videodev][ 1265.510732] video_usercopy+0x304/0x8c4 [videodev][ 1265.510757] video_ioctl2+0x18/0x34 [videodev][ 1265.510782] v4l2_ioctl+0x40/0x60 [videodev]...[ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state[ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state[ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active stOne CAMSS specific way to handle multiple VCs on the same RDI might be:- Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.- The video buffers are already associated with msm_vfeN_rdiX so release video buffers when told to do so by stop_streaming.- Only release the power-domains for the CSIPHY, CSID and VFE when their internal refcounts drop.Either way refusing to release video buffers based on use_count iserroneous and should be reverted. The silicon enabling code for selectingVCs is perfectly fine. Its a known missing feature that concurrent VCswon t work with CAMSS right now.Initial testing with this code didn t show an error but, SoftISP and real usage with Google Hangouts breaks the upstream code pretty quickly, we needto do a partial revert and take another pass at VCs.This commit partially reverts commit 89013969e232 ( media: camss: sm8250:Pipeline starting and stopping for multiple virtual channels ) openEuler评分: 5.5 Vector:CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H 受影响版本排查(受影响/不受影响): 1.openEuler-24.03-LTS(6.6.0):受影响 2.openEuler-20.03-LTS-SP4(4.19.90):不受影响 3.openEuler-22.03-LTS-SP3(5.10.0):不受影响 4.openEuler-22.03-LTS-SP4(5.10.0):不受影响 5.master(6.6.0):不受影响 6.openEuler-24.03-LTS-Next(6.6.0):不受影响 7.openEuler-24.03-LTS-SP1(6.6.0):不受影响 修复是否涉及abi变化(是/否): 1.openEuler-20.03-LTS-SP4(4.19.90):否 2.openEuler-22.03-LTS-SP3(5.10.0):否 3.master(6.6.0):否 4.openEuler-24.03-LTS(6.6.0):否 5.openEuler-24.03-LTS-Next(6.6.0):否 6.openEuler-22.03-LTS-SP4(5.10.0):否 7.openEuler-24.03-LTS-SP1(6.6.0):否 原因说明: 1.openEuler-24.03-LTS(6.6.0):正常修复 2.master(6.6.0):不受影响-漏洞代码不能被攻击者触发 3.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 4.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在 5.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在 6.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在 7.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在 三、漏洞修复 安全公告链接:https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1097
一、漏洞信息 漏洞编号:[CVE-2024-50175](https://nvd.nist.gov/vuln/detail/CVE-2024-50175) 漏洞归属组件:[kernel](https://gitee.com/src-openeuler/kernel) 漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0 CVSS V3.0分值: BaseScore:5.5 Medium Vector:CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H 漏洞简述: In the Linux kernel, the following vulnerability has been resolved:media: qcom: camss: Remove use_count guard in stop_streamingThe use_count check was introduced so that multiple concurrent Raw DataInterfaces RDIs could be driven by different virtual channels VCs on theCSIPHY input driving the video pipeline.This is an invalid use of use_count though as use_count pertains to thenumber of times a video entity has been opened by user-space not the numberof active streams.If use_count and stream-on count don t agree then stop_streaming() willbreak as is currently the case and has become apparent when using CAMSSwith libcamera s released softisp 0.3.The use of use_count like this is a bit hacky and right now breaks regularusage of CAMSS for a single stream case. Stopping qcam results in the splatbelow, and then it cannot be started again and any attempts to do so failswith -EBUSY.[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]...[ 1265.510630] Call trace:[ 1265.510636] __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common][ 1265.510648] vb2_core_streamoff+0x24/0xcc [videobuf2_common][ 1265.510660] vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2][ 1265.510673] v4l_streamoff+0x24/0x30 [videodev][ 1265.510707] __video_do_ioctl+0x190/0x3f4 [videodev][ 1265.510732] video_usercopy+0x304/0x8c4 [videodev][ 1265.510757] video_ioctl2+0x18/0x34 [videodev][ 1265.510782] v4l2_ioctl+0x40/0x60 [videodev]...[ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state[ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state[ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active stOne CAMSS specific way to handle multiple VCs on the same RDI might be:- Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.- The video buffers are already associated with msm_vfeN_rdiX so release video buffers when told to do so by stop_streaming.- Only release the power-domains for the CSIPHY, CSID and VFE when their internal refcounts drop.Either way refusing to release video buffers based on use_count iserroneous and should be reverted. The silicon enabling code for selectingVCs is perfectly fine. Its a known missing feature that concurrent VCswon t work with CAMSS right now.Initial testing with this code didn t show an error but, SoftISP and real usage with Google Hangouts breaks the upstream code pretty quickly, we needto do a partial revert and take another pass at VCs.This commit partially reverts commit 89013969e232 ( media: camss: sm8250:Pipeline starting and stopping for multiple virtual channels ) 漏洞公开时间:2024-11-08 14:15:14 漏洞创建时间:2024-11-08 14:33:51 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2024-50175 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-50175 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-50175 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9 | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-50175.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1233092 | | debian | | https://security-tracker.debian.org/tracker/CVE-2024-50175 | </details> 漏洞分析指导链接: https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md 漏洞数据来源: openBrain开源漏洞感知系统 漏洞补丁信息: <details> <summary>详情(点击展开)</summary> | 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源 | | ------- | -------- | ------- | -------- | --------- | | | | https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27 | | nvd | | | | https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3 | | nvd | | | | https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9 | | nvd | | | | https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee | | nvd | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:media: qcom: camss: Remove use_count guard in stop_streamingThe use_count check was introduced so that multiple concurrent Raw DataInterfaces RDIs could be driven by different virtual channels VCs on theCSIPHY input driving the video pipeline.This is an invalid use of use_count though as use_count pertains to thenumber of times a video entity has been opened by user-space not the numberof active streams.If use_count and stream-on count don t agree then stop_streaming() willbreak as is currently the case and has become apparent when using CAMSSwith libcamera s released softisp 0.3.The use of use_count like this is a bit hacky and right now breaks regularusage of CAMSS for a single stream case. Stopping qcam results in the splatbelow, and then it cannot be started again and any attempts to do so failswith -EBUSY.[ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common]...[ 1265.510630] Call trace:[ 1265.510636] __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common][ 1265.510648] vb2_core_streamoff+0x24/0xcc [videobuf2_common][ 1265.510660] vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2][ 1265.510673] v4l_streamoff+0x24/0x30 [videodev][ 1265.510707] __video_do_ioctl+0x190/0x3f4 [videodev][ 1265.510732] video_usercopy+0x304/0x8c4 [videodev][ 1265.510757] video_ioctl2+0x18/0x34 [videodev][ 1265.510782] v4l2_ioctl+0x40/0x60 [videodev]...[ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state[ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state[ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active stOne CAMSS specific way to handle multiple VCs on the same RDI might be:- Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx.- The video buffers are already associated with msm_vfeN_rdiX so release video buffers when told to do so by stop_streaming.- Only release the power-domains for the CSIPHY, CSID and VFE when their internal refcounts drop.Either way refusing to release video buffers based on use_count iserroneous and should be reverted. The silicon enabling code for selectingVCs is perfectly fine. Its a known missing feature that concurrent VCswon t work with CAMSS right now.Initial testing with this code didn t show an error but, SoftISP and real usage with Google Hangouts breaks the upstream code pretty quickly, we needto do a partial revert and take another pass at VCs.This commit partially reverts commit 89013969e232 ( media: camss: sm8250:Pipeline starting and stopping for multiple virtual channels ) openEuler评分: 5.5 Vector:CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H 受影响版本排查(受影响/不受影响): 1.openEuler-24.03-LTS(6.6.0):受影响 2.openEuler-20.03-LTS-SP4(4.19.90):不受影响 3.openEuler-22.03-LTS-SP3(5.10.0):不受影响 4.openEuler-22.03-LTS-SP4(5.10.0):不受影响 5.master(6.6.0):不受影响 6.openEuler-24.03-LTS-Next(6.6.0):不受影响 7.openEuler-24.03-LTS-SP1(6.6.0):不受影响 修复是否涉及abi变化(是/否): 1.openEuler-20.03-LTS-SP4(4.19.90):否 2.openEuler-22.03-LTS-SP3(5.10.0):否 3.master(6.6.0):否 4.openEuler-24.03-LTS(6.6.0):否 5.openEuler-24.03-LTS-Next(6.6.0):否 6.openEuler-22.03-LTS-SP4(5.10.0):否 7.openEuler-24.03-LTS-SP1(6.6.0):否 原因说明: 1.openEuler-24.03-LTS(6.6.0):正常修复 2.master(6.6.0):不受影响-漏洞代码不能被攻击者触发 3.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发 4.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在 5.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在 6.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在 7.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在 三、漏洞修复 安全公告链接:https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1097
Comments (
14
)
Sign in
to comment
Status
Done
Backlog
已挂起
Doing
Done
Declined
Assignees
Not set
sanglipeng
sanglipeng
Assignee
Collaborator
+Assign
+Mention
Labels
CVE/FIXED
sig/Kernel
Not set
Projects
Unprojected
Unprojected
Pull Requests
None yet
None yet
Successfully merging a pull request will close this issue.
Branches
No related branch
Branches (
-
)
Tags (
-
)
Planed to start   -   Planed to end
-
Top level
Not Top
Top Level: High
Top Level: Medium
Top Level: Low
Priority
Not specified
Serious
Main
Secondary
Unimportant
Duration
(hours)
参与者(3)
1
https://gitee.com/src-openeuler/kernel.git
git@gitee.com:src-openeuler/kernel.git
src-openeuler
kernel
kernel
Going to Help Center
Search
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
Repository Report
Back to the top
Login prompt
This operation requires login to the code cloud account. Please log in before operating.
Go to login
No account. Register