【openEuler-1.0-LTS】往qos_level文件写入-1会出现告警"sleeping function called from invalid context"

【标题描述】往qos_level文件写入-1会出现告警"sleeping function called from invalid context"
【环境信息】
硬件信息：
1）	裸机场景提供出问题的硬件信息；
2）	虚机场景提供虚机XML文件或者配置信息
软件信息：
1）	OS版本及分支
4.19.90
2）	内核信息
3）	发现问题的组件版本信息
如果有特殊组网，请提供网络拓扑图
【问题复现步骤】
具体操作步骤

```
1. cd /sys/fs/cgroup/cpu
2. mkdir test
3. echo -1 > test.cpu.qos_level
```

出现概率(是否必现，概率性错误)
必现
【预期结果】
描述预期结果，可以通过对比新老版本获取
不出现告警

【实际结果】
描述出问题的结果 
出现如下告警

```
root@zq:/sys/fs/cgroup/cpu# echo -1 > test/cpu.qos_level
root@localhost:/sys/fs/cgroup/cpu# echo -1 > test/cpu.qos_level
[   34.276516] BUG: sleeping function called from invalid context at ../kernel/locking/mutex.c:264
[   34.277001] in_atomic(): 1, irqs_disabled(): 0, pid: 550, name: bash

```

【附件信息】
比如系统message日志/组件日志、dump信息、图片等

```
[   34.276516] BUG: sleeping function called from invalid context at ../kernel/locking/mutex.c:264
[   34.277001] in_atomic(): 1, irqs_disabled(): 0, pid: 550, name: bash
[   34.277498] CPU: 5 PID: 550 Comm: bash Not tainted 4.19.90+ #2
[   34.277527] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
[   34.277669] Call Trace:
[   34.278235]  dump_stack+0x6d/0x98
[   34.278235]  ___might_sleep+0xfc/0x120
[   34.278235]  __might_sleep+0x4a/0x80
[   34.278235]  ? set_nr_if_polling+0x40/0x40
[   34.278235]  mutex_lock+0x20/0x50
[   34.278235]  static_key_slow_inc_cpuslocked+0x3f/0xa0
[   34.278235]  cfs_bandwidth_usage_inc+0x15/0x20
[   34.278235]  tg_change_scheduler+0x90/0xa0
[   34.278235]  ? terminate_walk+0x6d/0xe0
[   34.278235]  ? path_openat+0x5b9/0x1460
[   34.278235]  ? reuse_swap_page+0x126/0x390
[   34.278235]  walk_tg_tree_from+0x35/0xd0
[   34.278235]  ? sched_move_work+0x70/0x70
[   34.278235]  cpu_qos_write+0x5d/0x80
[   34.278235]  cgroup_file_write+0x10b/0x140
[   34.278235]  kernfs_fop_write+0x124/0x1b0
[   34.278235]  __vfs_write+0x2b/0x190
[   34.278235]  ? __might_sleep+0x4a/0x80
[   34.278235]  ? _cond_resched+0x19/0x30
[   34.278235]  ? __sb_start_write+0x3b/0xb0
[   34.278235]  vfs_write+0xc4/0x1c0
[   34.278235]  ksys_write+0x49/0xb0
[   34.278235]  __x64_sys_write+0x1a/0x20
[   34.278235]  do_syscall_64+0x5c/0x130
[   34.278235]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   34.278235] RIP: 0033:0x7faa51464224
[   34.278235] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 c1 07 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 45
[   34.278235] RSP: 002b:00007ffcc5103238 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[   34.278235] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007faa51464224
[   34.278235] RDX: 0000000000000003 RSI: 0000559a1fe45150 RDI: 0000000000000001
[   34.278235] RBP: 0000559a1fe45150 R08: 000000000000000a R09: 0000000000000002
[   34.278235] R10: 000000000000000a R11: 0000000000000246 R12: 00007faa51740760
[   34.278235] R13: 0000000000000003 R14: 00007faa5173c2a0 R15: 00007faa5173b760

```

GVP openEuler/kernel
Closed

Content Risk Flag

Comments (1)

GVPopenEuler/kernelClosed

Content Risk Flag