Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
x94 nvmem_cell_read_variable_common+0x4c/0xb0 nvmem_cell_read_variable_le_u32+0x40/0x100 a6xx_gpu_init+0x170/0x2f4 adreno_bind+0x174/0x284 component_bind_all+0xf0/0x264 msm_drm_bind+0x1d8/0x7a0 try_to_bring_up_master+0x164/0x1ac __component_add+0xbc/0x13c component_add+0x20/0x2c dp_display_probe+0x340/0x384 platform_probe+0xc0/0x100 really_probe+0x110/0x304 __driver_probe_device+0xb8/0x120 driver_probe_device+0x4c/0xfc __device_attach_driver+0xb0/0x128 bus_for_each_drv+0x90/0xdc __device_attach+0xc8/0x174 device_initial_probe+0x20/0x2c bus_probe_device+0x40/0xa4 deferred_probe_work_func+0x7c/0xb8 process_one_work+0x128/0x21c process_scheduled_works+0x40/0x54 worker_thread+0x1ec/0x2a8 kthread
obe_work_func+0x7c/0xb8 process_one_work+0x128/0x21c process_scheduled_works+0x40/0x54 worker_thread+0x1ec/0x2a8 kthread+0x138/0x158 ret_from_fork+0x10/0x20 Fix it by making sure there are any bits to mask out. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/abcb8d33e4d2215ccde5ab5ccf9f730a59d79d97 - https://git.kernel.org/stable/c/60df06bbdf497e37ed25ad40572c362e5b0998df - https://git.kernel.org/stable/c/2df6c023050205c4d04ffc121bc549f65cb8d1df - https://git.kernel.org/stable/c/eb0fc8e7170e61eaf65d28dee4a8baf4e86b19ca - https://git.kernel.org/stable/c/0594f1d048d8dc338eb9a240021b1d00ae1eb082 - https://git.kernel.org/s
dee4a8baf4e86b19ca - https://git.kernel.org/stable/c/0594f1d048d8dc338eb9a240021b1d00ae1eb082 - https://git.kernel.org/stable/c/57e48886401b14cd351423fabfec2cfd18df4f66 - https://git.kernel.org/stable/c/0e822e5413da1af28cca350cb1cb42b6133bdcae - https://git.kernel.org/stable/c/5d388fa01fa6eb310ac023a363a6cb216d9d8fe9
CVE ID: CVE-2021-47498 State: PUBLISHED Published: 2024-05-22T08:19:44.803Z Last Updated: 2025-11-03T17:30:58.877Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dm rq: don't queue request to blk-mq during DM suspend DM uses blk-mq's quiesce/unquiesce to stop/start device mapper queue. But blk-mq's unquiesce may come from outside events, such as elevator switch, updating nr_requests or others, and request may come during suspend, so simply ask for blk-mq to requeue it. Fixes one kernel panic issue when running updating nr_requests and dm-mpath suspend/resume stress test. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE
updating nr_requests and dm-mpath suspend/resume stress test. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8050652810bf38241edec8717393d2446e8036f1 - https://git.kernel.org/stable/c/8ca9745efe3528feb06ca4e117188038eea2d351 - https://git.kernel.org/stable/c/b4459b11e84092658fa195a2587aff3b9637f0e7
CVE ID: CVE-2021-47499 State: PUBLISHED Published: 2024-05-24T15:01:42.684Z Last Updated: 2025-05-04T07:12:21.484Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: iio: accel: kxcjk-1013: Fix possible memory leak in probe and remove When ACPI type is ACPI_SMO8500, the data->dready_trig will not be set, the memory allocated by iio_triggered_buffer_setup() will not be freed, and cause memory leak as follows: unreferenced object 0xffff888009551400 (size 512): comm "i2c-SMO8500-125", pid 911, jiffies 4294911787 (age 83.852s) hex dump (first 32 bytes): 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00
83.852s) hex dump (first 32 bytes): 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 20 e2 e5 c0 ff ff ff ff ........ ....... backtrace: [<0000000041ce75ee>] kmem_cache_alloc_trace+0x16d/0x360 [<000000000aeb17b0>] iio_kfifo_allocate+0x41/0x130 [kfifo_buf] [<000000004b40c1f5>] iio_triggered_buffer_setup_ext+0x2c/0x210 [industrialio_triggered_buffer] [<000000004375b15f>] kxcjk1013_probe+0x10c3/0x1d81 [kxcjk_1013] Fix it by remove data->dready_trig condition in probe and remove. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/8c1d43f3a3fc7184c42d7398bdf59a2a2903e4fc - https://git.k
ADP Vulnrichment: References: - https://git.kernel.org/stable/c/8c1d43f3a3fc7184c42d7398bdf59a2a2903e4fc - https://git.kernel.org/stable/c/60a55b9d91ba99eb8cf015bc46dc2de05e168a15 - https://git.kernel.org/stable/c/3899700ddacbf7aaafadf44464fff3ff0d4e3307 - https://git.kernel.org/stable/c/a3730f74159ad00a28960c0efe2a931fe6fe6b45 - https://git.kernel.org/stable/c/8c163a14277115ca962103910ab4cce55e862ffb - https://git.kernel.org/stable/c/ee86d0bad80bdcd11a87e188a596727f41b62320 - https://git.kernel.org/stable/c/14508fe13b1c578b3d2ba574f1d48b351975860c - https://git.kernel.org/stable/c/70c9774e180d151abaab358108e3510a8e615215
CVE ID: CVE-2021-47500 State: PUBLISHED Published: 2024-05-24T15:01:43.362Z Last Updated: 2025-05-04T07:12:22.590Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: iio: mma8452: Fix trigger reference couting The mma8452 driver directly assigns a trigger to the struct iio_dev. The IIO core when done using this trigger will call `iio_trigger_put()` to drop the reference count by 1. Without the matching `iio_trigger_get()` in the driver the reference count can reach 0 too early, the trigger gets freed while still in use and a use-after-free occurs. Fix this by getting a reference to the trigger before assigning it to the IIO device.
n use and a use-after-free occurs. Fix this by getting a reference to the trigger before assigning it to the IIO device. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/094d513b78b1714113bc016684b8142382e071ba - https://git.kernel.org/stable/c/fb75cc4740d81264cd5bcb0e17d961d018a8be96 - https://git.kernel.org/stable/c/794c0898f6bf39a458655d5fb4af70ec43a5cfcb - https://git.kernel.org/stable/c/f5deab10ced368c807866283f8b79144c4823be8 - https://git.kernel.org/stable/c/acf0088ac073ca6e7f4cad6acac112177e08df5e - https://git.kernel.org/stable/c/db12d95085367de8b0223929d1332731024441f1 - https://git.kernel.org/stable/c/c435170
f5e - https://git.kernel.org/stable/c/db12d95085367de8b0223929d1332731024441f1 - https://git.kernel.org/stable/c/c43517071dfc9fce34f8f69dbb98a86017f6b739 - https://git.kernel.org/stable/c/cd0082235783f814241a1c9483fb89e405f4f892
CVE ID: CVE-2021-47501 State: PUBLISHED Published: 2024-05-24T15:01:49.040Z Last Updated: 2025-05-04T07:12:23.634Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: i40e: Fix NULL pointer dereference in i40e_dbg_dump_desc When trying to dump VFs VSI RX/TX descriptors using debugfs there was a crash due to NULL pointer dereference in i40e_dbg_dump_desc. Added a check to i40e_dbg_dump_desc that checks if VSI type is correct for dumping RX/TX descriptors. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/e5b7fb2198abc50058f1a29c395b004f76ab1c83 - https://git.kern
ram Container: References: - https://git.kernel.org/stable/c/e5b7fb2198abc50058f1a29c395b004f76ab1c83 - https://git.kernel.org/stable/c/16431e442db248ecd8aa9457cf0a656f1885f56e - https://git.kernel.org/stable/c/23ec111bf3549aae37140330c31a16abfc172421
CVE ID: CVE-2021-47502 State: PUBLISHED Published: 2024-05-24T15:01:49.699Z Last Updated: 2025-05-04T07:12:24.711Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd934x: handle channel mappping list correctly Currently each channel is added as list to dai channel list, however there is danger of adding same channel to multiple dai channel list which endups corrupting the other list where its already added. This patch ensures that the channel is actually free before adding to the dai channel list and also ensures that the channel is on the list before deleting it. This check was missing previously, and we did not
and also ensures that the channel is on the list before deleting it. This check was missing previously, and we did not hit this issue as we were testing very simple usecases with sequence of amixer commands. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/1089dac26c6b4b833323ae6c0ceab29fb30ede72 - https://git.kernel.org/stable/c/339ffb5b56005582aacc860524d2d208604049d1 - https://git.kernel.org/stable/c/23ba28616d3063bd4c4953598ed5e439ca891101
CVE ID: CVE-2021-47503 State: PUBLISHED Published: 2024-05-24T15:01:50.358Z Last Updated: 2025-05-04T07:12:25.934Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: pm80xx: Do not call scsi_remove_host() in pm8001_alloc() Calling scsi_remove_host() before scsi_add_host() results in a crash: BUG: kernel NULL pointer dereference, address: 0000000000000108 RIP: 0010:device_del+0x63/0x440 Call Trace: device_unregister+0x17/0x60 scsi_remove_host+0xee/0x2a0 pm8001_pci_probe+0x6ef/0x1b90 [pm80xx] local_pci_probe+0x3f/0x90 We cannot call scsi_remove_host() in pm8001_alloc() because scsi_add_host() has not been called yet at that poi
x3f/0x90 We cannot call scsi_remove_host() in pm8001_alloc() because scsi_add_host() has not been called yet at that point in time. Function call tree: pm8001_pci_probe() | `- pm8001_pci_alloc() | | | `- pm8001_alloc() | | | `- scsi_remove_host() | `- scsi_add_host() Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/1e434d2687e8bc0b3cdc9dd093c0e9047c0b4add - https://git.kernel.org/stable/c/f8dccc1bdea7e21b5ec06c957aef8831c772661c - https://git.kernel.org/stable/c/653926205741add87a6cf452e21950eebc6ac10b
CVE ID: CVE-2021-47504 State: PUBLISHED Published: 2024-05-24T15:01:51.013Z Last Updated: 2025-07-28T11:16:20.281Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: io_uring: ensure task_work gets run as part of cancelations If we successfully cancel a work item but that work item needs to be processed through task_work, then we can be sleeping uninterruptibly in io_uring_cancel_generic() and never process it. Hence we don't make forward progress and we end up with an uninterruptible sleep warning. While in there, correct a comment that should be IFF, not IIF. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Contai
, correct a comment that should be IFF, not IIF. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8e12976c0c19ebc14b60046b1348c516a74c25a2 - https://git.kernel.org/stable/c/78a780602075d8b00c98070fa26e389b3b3efa72
CVE ID: CVE-2021-47505 State: PUBLISHED Published: 2024-05-24T15:01:52.088Z Last Updated: 2025-05-04T07:12:28.338Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: aio: fix use-after-free due to missing POLLFREE handling signalfd_poll() and binder_poll() are special in that they use a waitqueue whose lifetime is the current task, rather than the struct file as is normally the case. This is okay for blocking polls, since a blocking poll occurs within one task; however, non-blocking polls require another solution. This solution is for the queue to be cleared before it is freed, by sending a POLLFREE notification to all waiters. Unf
This solution is for the queue to be cleared before it is freed, by sending a POLLFREE notification to all waiters. Unfortunately, only eventpoll handles POLLFREE. A second type of non-blocking poll, aio poll, was added in kernel v4.18, and it doesn't handle POLLFREE. This allows a use-after-free to occur if a signalfd or binder fd is polled with aio poll, and the waitqueue gets freed. Fix this by making aio poll handle POLLFREE. A patch by Ramji Jiyani <ramjiyani@google.com> (https://lore.kernel.org/r/20211027011834.2497484-1-ramjiyani@google.com) tried to do this by making aio_poll_wake() always complete the request inline if POLLFREE is seen. However, that solution had two bugs. First, i
ng aio_poll_wake() always complete the request inline if POLLFREE is seen. However, that solution had two bugs. First, it introduced a deadlock, as it unconditionally locked the aio context while holding the waitqueue lock, which inverts the normal locking order. Second, it didn't consider that POLLFREE notifications are missed while the request has been temporarily de-queued. The second problem was solved by my previous patch. This patch then properly fixes the use-after-free by handling POLLFREE in a deadlock-free way. It does this by taking advantage of the fact that freeing of the waitqueue is RCU-delayed, similar to what eventpoll does. Additional Analyst Notes: - CISA ADP Vulnrichment:
eing of the waitqueue is RCU-delayed, similar to what eventpoll does. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/321fba81ec034f88aea4898993c1bf15605c023f - https://git.kernel.org/stable/c/4105e6a128e8a98455dfc9e6dbb2ab0c33c4497f - https://git.kernel.org/stable/c/47ffefd88abfffe8a040bcc1dd0554d4ea6f7689 - https://git.kernel.org/stable/c/60d311f9e6381d779d7d53371f87285698ecee24 - https://git.kernel.org/stable/c/50252e4b5e989ce64555c7aef7516bdefc2fea72
CVE ID: CVE-2021-47506 State: PUBLISHED Published: 2024-05-24T15:01:52.746Z Last Updated: 2025-05-21T08:31:49.596Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nfsd: fix use-after-free due to delegation race A delegation break could arrive as soon as we've called vfs_setlease. A delegation break runs a callback which immediately (in nfsd4_cb_recall_prepare) adds the delegation to del_recall_lru. If we then exit nfs4_set_delegation without hashing the delegation, it will be freed as soon as the callback is done with it, without ever being removed from del_recall_lru. Symptoms show up later as use-after-free or list corruption
ne with it, without ever being removed from del_recall_lru. Symptoms show up later as use-after-free or list corruption warnings, usually in the laundromat thread. I suspect aba2072f4523 "nfsd: grant read delegations to clients holding writes" made this bug easier to hit, but I looked as far back as v3.0 and it looks to me it already had the same problem. So I'm not sure where the bug was introduced; it may have been there from the beginning. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/04a8d07f3d58308b92630045560799a3faa3ebce - https://git.kernel.org/stable/c/348714018139c39533c55661a0c7c990671396b4 - https://git.k
8308b92630045560799a3faa3ebce - https://git.kernel.org/stable/c/348714018139c39533c55661a0c7c990671396b4 - https://git.kernel.org/stable/c/33645d3e22720cac1e4548f8fef57bf0649536ee - https://git.kernel.org/stable/c/2becaa990b93cbd2928292c0b669d3abb6cf06d4 - https://git.kernel.org/stable/c/e0759696de6851d7536efddfdd2dfed4c4df1f09 - https://git.kernel.org/stable/c/eeb0711801f5e19ef654371b627682aed3b11373 - https://git.kernel.org/stable/c/148c816f10fd11df27ca6a9b3238cdd42fa72cd3 - https://git.kernel.org/stable/c/548ec0805c399c65ed66c6641be467f717833ab5
CVE ID: CVE-2021-47507 State: PUBLISHED Published: 2024-05-24T15:01:53.401Z Last Updated: 2025-05-04T12:41:35.982Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nfsd: Fix nsfd startup race (again) Commit bd5ae9288d64 ("nfsd: register pernet ops last, unregister first") has re-opened rpc_pipefs_event() race against nfsd_net_id registration (register_pernet_subsys()) which has been fixed by commit bb7ffbf29e76 ("nfsd: fix nsfd startup race triggering BUG_ON"). Restore the order of register_pernet_subsys() vs register_cld_notifier(). Add WARN_ON() to prevent a future regression. Crash info: Unable to handle kernel NULL pointer de
gister_cld_notifier(). Add WARN_ON() to prevent a future regression. Crash info: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000012 CPU: 8 PID: 345 Comm: mount Not tainted 5.4.144-... #1 pc : rpc_pipefs_event+0x54/0x120 [nfsd] lr : rpc_pipefs_event+0x48/0x120 [nfsd] Call trace: rpc_pipefs_event+0x54/0x120 [nfsd] blocking_notifier_call_chain rpc_fill_super get_tree_keyed rpc_fs_get_tree vfs_get_tree do_mount ksys_mount __arm64_sys_mount el0_svc_handler el0_svc Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/f5734b1714ca355703e9ea8fb61d04beff1790b9 - https://git.kernel.org/stable/c/c5209
nces: - https://git.kernel.org/stable/c/f5734b1714ca355703e9ea8fb61d04beff1790b9 - https://git.kernel.org/stable/c/c520943a00ad5015704969ad3304c956bcd49d25 - https://git.kernel.org/stable/c/8bf902fee5893cfc2f04a698abab47629699ae9a - https://git.kernel.org/stable/c/b10252c7ae9c9d7c90552f88b544a44ee773af64
CVE ID: CVE-2021-47508 State: PUBLISHED Published: 2024-05-24T15:01:54.048Z Last Updated: 2025-05-04T07:12:31.796Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: btrfs: free exchange changeset on failures Fstests runs on my VMs have show several kmemleak reports like the following. unreferenced object 0xffff88811ae59080 (size 64): comm "xfs_io", pid 12124, jiffies 4294987392 (age 6.368s) hex dump (first 32 bytes): 00 c0 1c 00 00 00 00 00 ff cf 1c 00 00 00 00 00 ................ 90 97 e5 1a 81 88 ff ff 90 97 e5 1a 81 88 ff ff ................ backtrace: [<00000000ac0176d2>] ulist_add_merge+0x60/0x150 [btrfs] [<0000000076e9f312>]
1a 81 88 ff ff ................ backtrace: [<00000000ac0176d2>] ulist_add_merge+0x60/0x150 [btrfs] [<0000000076e9f312>] set_state_bits+0x86/0xc0 [btrfs] [<0000000014fe73d6>] set_extent_bit+0x270/0x690 [btrfs] [<000000004f675208>] set_record_extent_bits+0x19/0x20 [btrfs] [<00000000b96137b1>] qgroup_reserve_data+0x274/0x310 [btrfs] [<0000000057e9dcbb>] btrfs_check_data_free_space+0x5c/0xa0 [btrfs] [<0000000019c4511d>] btrfs_delalloc_reserve_space+0x1b/0xa0 [btrfs] [<000000006d37e007>] btrfs_dio_iomap_begin+0x415/0x970 [btrfs] [<00000000fb8a74b8>] iomap_iter+0x161/0x1e0 [<0000000071dff6ff>] __iomap_dio_rw+0x1df/0x700 [<000000002567ba53>] iomap_dio_rw+0x5/0x20 [<0000000072e555f8>] btrfs_file_wr
0000071dff6ff>] __iomap_dio_rw+0x1df/0x700 [<000000002567ba53>] iomap_dio_rw+0x5/0x20 [<0000000072e555f8>] btrfs_file_write_iter+0x290/0x530 [btrfs] [<000000005eb3d845>] new_sync_write+0x106/0x180 [<000000003fb505bf>] vfs_write+0x24d/0x2f0 [<000000009bb57d37>] __x64_sys_pwrite64+0x69/0xa0 [<000000003eba3fdf>] do_syscall_64+0x43/0x90 In case brtfs_qgroup_reserve_data() or btrfs_delalloc_reserve_metadata() fail the allocated extent_changeset will not be freed. So in btrfs_check_data_free_space() and btrfs_delalloc_reserve_space() free the allocated extent_changeset to get rid of the allocated memory. The issue currently only happens in the direct IO write path, but only after 65b3c08606e5 ("bt
of the allocated memory. The issue currently only happens in the direct IO write path, but only after 65b3c08606e5 ("btrfs: fix ENOSPC failure when attempting direct IO write into NOCOW range"), and also at defrag_one_locked_target(). Every other place is always calling extent_changeset_free() even if its call to btrfs_delalloc_reserve_space() or btrfs_check_data_free_space() has failed. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/ca06c5cb1b6dbfe67655b33c02fc394d65824519 - https://git.kernel.org/stable/c/da5e817d9d75422eaaa05490d0b9a5e328fc1a51
CVE ID: CVE-2021-47509 State: PUBLISHED Published: 2024-05-24T15:09:25.349Z Last Updated: 2025-05-04T07:12:32.885Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Limit the period size to 16MB Set the practical limit to the period size (the fragment shift in OSS) instead of a full 31bit; a too large value could lead to the exhaust of memory as we allocate temporary buffers of the period size, too. As of this patch, we set to 16MB limit, which should cover all use cases. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/d1bb703ad050de9095f10b2
- CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/d1bb703ad050de9095f10b2d3416c32921ac6bcc - https://git.kernel.org/stable/c/b02a41eebcc36d4f07196780f2e165ca2c499257 - https://git.kernel.org/stable/c/be55f306396cd62c6889286a7194fd8b53363aeb - https://git.kernel.org/stable/c/2e54cf6794bf82a54aaefc78da13819aea9cd28a - https://git.kernel.org/stable/c/76f19e4cbb548e28547f8c328aa0bfb3a10222d3 - https://git.kernel.org/stable/c/ad45babf7886e7a212ee1d5eda9ef49f696db43c - https://git.kernel.org/stable/c/35a3e511032146941085f87dd9fb5b82ea5c00a2 - https://git.kernel.org/stable/c/8839c8c0f77ab8fc0463f4ab8b37fca3f70677c2
CVE ID: CVE-2021-47510 State: PUBLISHED Published: 2024-05-24T15:09:26.019Z Last Updated: 2025-05-04T07:12:34.135Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix re-dirty process of tree-log nodes There is a report of a transaction abort of -EAGAIN with the following script. #!/bin/sh for d in sda sdb; do mkfs.btrfs -d single -m single -f /dev/\${d} done mount /dev/sda /mnt/test mount /dev/sdb /mnt/scratch for dir in test scratch; do echo 3 >/proc/sys/vm/drop_caches fio --directory=/mnt/\${dir} --name=fio.\${dir} --rw=read --size=50G --bs=64m \ --numjobs=$(nproc) --time_based --ramp_time=5 --runtime=480 \ --group_rep
me=fio.\${dir} --rw=read --size=50G --bs=64m \ --numjobs=$(nproc) --time_based --ramp_time=5 --runtime=480 \ --group_reporting |& tee /dev/shm/fio.\${dir} echo 3 >/proc/sys/vm/drop_caches done for d in sda sdb; do umount /dev/\${d} done The stack trace is shown in below. [3310.967991] BTRFS: error (device sda) in btrfs_commit_transaction:2341: errno=-11 unknown (Error while writing out transaction) [3310.968060] BTRFS info (device sda): forced readonly [3310.968064] BTRFS warning (device sda): Skipping commit of aborted transaction. [3310.968065] ------------[ cut here ]------------ [3310.968066] BTRFS: Transaction aborted (error -11) [3310.968074] WARNING: CPU: 14 PID: 1684 at fs/btrfs/tran
--------- [3310.968066] BTRFS: Transaction aborted (error -11) [3310.968074] WARNING: CPU: 14 PID: 1684 at fs/btrfs/transaction.c:1946 btrfs_commit_transaction.cold+0x209/0x2c8 [3310.968131] CPU: 14 PID: 1684 Comm: fio Not tainted 5.14.10-300.fc35.x86_64 #1 [3310.968135] Hardware name: DIAWAY Tartu/Tartu, BIOS V2.01.B10 04/08/2021 [3310.968137] RIP: 0010:btrfs_commit_transaction.cold+0x209/0x2c8 [3310.968144] RSP: 0018:ffffb284ce393e10 EFLAGS: 00010282 [3310.968147] RAX: 0000000000000026 RBX: ffff973f147b0f60 RCX: 0000000000000027 [3310.968149] RDX: ffff974ecf098a08 RSI: 0000000000000001 RDI: ffff974ecf098a00 [3310.968150] RBP: ffff973f147b0f08 R08: 0000000000000000 R09: ffffb284ce393c48 [33
00000000000001 RDI: ffff974ecf098a00 [3310.968150] RBP: ffff973f147b0f08 R08: 0000000000000000 R09: ffffb284ce393c48 [3310.968151] R10: ffffb284ce393c40 R11: ffffffff84f47468 R12: ffff973f101bfc00 [3310.968153] R13: ffff971f20cf2000 R14: 00000000fffffff5 R15: ffff973f147b0e58 [3310.968154] FS: 00007efe65468740(0000) GS:ffff974ecf080000(0000) knlGS:0000000000000000 [3310.968157] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [3310.968158] CR2: 000055691bcbe260 CR3: 000000105cfa4001 CR4: 0000000000770ee0 [3310.968160] PKRU: 55555554 [3310.968161] Call Trace: [3310.968167] ? dput+0xd4/0x300 [3310.968174] btrfs_sync_file+0x3f1/0x490 [3310.968180] __x64_sys_fsync+0x33/0x60 [3310.968185] do_sysc