修复读写锁带来的scheduling while atomic BUG

**【缺陷描述】：请补充详细的缺陷问题现象描述**
内核出现scheduling while atomic BUG
[616387.574547] BUG: scheduling while atomic: engine/35689/0x00000002
[616387.574806] Modules linked in: qtfs_server(OE) smc(E) ib_core xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat xt_addrtype iptxt_conntrack nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc overlay rfkill intel_rapl_msr intel_rmon skx_edac_common kmem kvm_intel kvm irqbypass vfat rapl fat iTCO_wdt device_dax iTCO_vendor_support vmw_vsock_virtio_transport vmw_vsocmon i2c_i801 pcspkr i2c_smbus vsock virtio_balloon nd_pmem dax_pmem nd_btt lpc_ich joydev sg fuse ext4 mbcache jbd2 virtio_gpu virtio_dma_rm_kms_helper sr_mod cdrom drm ahci libahci crct10dif_pclmul nfit crc32_pclmul libata libnvdimm crc32c_intel virtio_net ghash_clmulni_intessse3 virtio_console virtio_blk failover serio_raw dm_multipath dm_mod [last unloaded: qtfs_server(OE)]
[616387.576568] CPU: 16 PID: 35689 Comm: engine Kdump: loaded Tainted: G W OE 6.6.0eulerx_extsm+ #1
[616387.576883] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 2/2/2022
[616387.577198] Call Trace:
[616387.577504]
[616387.577807] dump_stack_lvl+0x36/0x50
[616387.578121] __schedule_bug+0x52/0x60
[616387.578423] __schedule+0xa7e/0xc30
[616387.578721] schedule+0x5e/0xd0
[616387.579015] io_schedule+0x46/0x70
[616387.579315] folio_put_wait_locked.isra.0+0x11a/0x240
[616387.579612] ? __pfx_wake_page_function+0x10/0x10
[616387.579906] filemap_update_page+0x2bf/0x2d0
[616387.580208] filemap_get_pages+0x221/0x310
[616387.580498] filemap_read+0xd5/0x340
[616387.580784] ? desc_read_finalized_seq+0x2f/0x90
[616387.581078] ? _prb_read_valid+0x6a/0xc0
[616387.581363] ? prb_read_valid+0x1b/0x30
[616387.581646] ? printk_get_next_message+0x76/0x2a0
[616387.581930] ? get_color+0x26/0x130
[616387.582216] new_sync_read+0xc8/0x170
[616387.582497] vfs_read+0x15d/0x1d0
[616387.582773] ksys_read+0x67/0xe0
[616387.583049] qtfs_syscall_read+0x43/0x70 [qtfs_server]
[616387.583339] ? __wake_up_klogd.part.0+0x3c/0x60
[616387.583614] ? vprintk_emit+0x1e7/0x280
[616387.583886] ? _printk+0x5c/0x80
[616387.584160] ? handle_readiter+0x27e/0x690 [qtfs_server]
[616387.584438] handle_readiter+0x34e/0x690 [qtfs_server]
[616387.584713] ? qtfs_conn_recv_block+0x13d/0x1d0 [qtfs_server]
[616387.584990] qtfs_conn_server_run+0x124/0x470 [qtfs_server]
[616387.585273] qtfs_server_misc_ioctl+0x286/0x810 [qtfs_server]

**一、缺陷信息**

**【缺陷所属的os版本】（如openEuler-22.03-LTS，参考命令"cat /etc/os-release"结果）**
openEuler-22.03-LTS-SP3
openEuler-22.03-LTS-SP4
openEuler-24.03-LTS
**【内核版本】（如kernel-5.10.0-60.138.0.165，参考命令"uname -r"结果）**

**【缺陷所属软件及版本号】（如kernel-5.10.0-60.138.0.165，参考命令"rpm -q 包名"结果）**

**【环境信息】**
硬件信息

- 提供跟硬件相关的信息，如架构、cpu和内存规格等
- 虚拟机场景，额外补充宿主机os版本类型

软件信息

- 跟缺陷所属软件相关的其它软件版本信息（如软件包构建失败由gcc引起，请填写gcc的版本号）

网络信息

- 如果有特殊组网，请提供网络拓扑信息以及网络数据走向

**【问题复现步骤】：请描述具体的操作步骤**

**【实际结果】**，请描述出问题的结果和影响
**【期望结果】**，请描述出期望的结果和影响
**【其他相关附件信息】**
比如系统message日志/组件日志、dump信息、图片等

**【缺陷详情及分析指导参考链接】**
在qtfs中使用了自旋读写锁，并且在长路径中也用自旋读写锁保护，如果长路径中发生了调度则会由调度器报潜在的bug。
如果长路径中读写用户态内存产生了缺页，则无法正确处理。

**二、缺陷分析结构反馈**
影响性分析说明：

缺陷严重等级:(Critical/High/Moderate/Low)

缺陷根因说明:

受影响版本排查(受影响/不受影响):
openEuler-20.03-LTS-SP4
openEuler-22.03-LTS-SP1
openEuler-22.03-LTS-SP3
openEuler-22.03-LTS-SP4
openEuler-24.03-LTS

修复是否涉及abi变化(是/否):
openEuler-20.03-LTS-SP4
openEuler-22.03-LTS-SP1
openEuler-22.03-LTS-SP3
openEuler-22.03-LTS-SP4
openEuler-24.03-LTS

src-openEuler/dpu-utilities

内容风险标识

评论 (2)

src-openEuler/dpu-utilities .gitee-modal { width: 500px !important; }

内容风险标识