Skip to content

WIP: try out custom config annotation #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 299 commits into from
Closed

WIP: try out custom config annotation #47

wants to merge 299 commits into from

Conversation

prakashsurya
Copy link
Contributor

No description provided.

rtg-canonical and others added 30 commits July 18, 2023 09:27
@rtg-canonical
UBUNTU: [Config] aws: Format end of annotations file
d6fe6c3 
Ignore: yes

Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: [Config] aws: Config update after rebase
50f3c5f 
A number of new device configurations were not enabled, primarily
the INTEL_VSC and LJCA family of devices,

Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: [Config] aws: Update configs and policies after rebase
415a462 
Ignore: yes

Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: [Config] aws: CONFIG_SOUND=m
6155eeb 
BugLink: https://bugs.launchpad.net/bugs/1970586

Signed-off-by: Tim Gardner <[email protected]>
Acked-by: Kleber Sacilotto de Souza <[email protected]>
Acked-by: Andrea Righi <[email protected]>
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: Start new release
737744b 
Ignore: yes
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: link-to-tracker: update tracking bug
e23b93d 
BugLink: https://bugs.launchpad.net/bugs/1974290
Properties: no-test-build
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: Ubuntu-aws-5.15.0-1009.11
e39f812 
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: Start new release
bfd9d02 
Ignore: yes
Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]>
@rtg-canonical
UBUNTU: Ubuntu-aws-5.15.0-1011.14
64bb5b2 
Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]>
@rtg-canonical
UBUNTU: Start new release
cb5641f 
Ignore: yes
Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]>
@rtg-canonical
UBUNTU: Ubuntu-aws-5.15.0-1013.17
70418d2 
Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]>
@rtg-canonical
UBUNTU: Start new release
11f274e 
Ignore: yes
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: link-to-tracker: update tracking bug
bd1d06f 
BugLink: https://bugs.launchpad.net/bugs/1978586
Properties: no-test-build
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: [Config] Update configs after rebase
c87d397 
UBUNTU: [Config] updateconfigs for IPU6 driver
BugLink: https://bugs.launchpad.net/bugs/1955383

UBUNTU: [Config] IPU6: enable OV01A10 sensor
BugLink: https://bugs.launchpad.net/bugs/1955383

UBUNTU: [Config] ivsc: enable Intel VSC drivers
BugLink: https://bugs.launchpad.net/bugs/1955383

UBUNTU: [Config] make Intel IPU6 modules amd64 only
BugLink: https://bugs.launchpad.net/bugs/1955383

UBUNTU: [Config] IPU6: enable OV02C10 sensor
BugLink: https://bugs.launchpad.net/bugs/1964983

UBUNTU: [Config] drop intel_ulpss in favor of by LJCA
BugLink: https://bugs.launchpad.net/bugs/1964983

Revert "UBUNTU: [Config] enable Intel DMA remapping options by default"
BugLink: https://bugs.launchpad.net/bugs/1971699

Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: [Packaging] aws: drop do_<mod> arch specific configs
be26ca4 
BugLink: https://bugs.launchpad.net/bugs/1969434

    They should been assigned automatically based on the latest
    dkms-versions.

    Also disable building any dkms for mainline builds.

    Signed-off-by: You-Sheng Yang (vicamo) <[email protected]>
    Signed-off-by: Dimitri John Ledkov <[email protected]>
    Acked-by: Stefan Bader <[email protected]>
    Acked-by: Kleber Sacilotto de Souza <[email protected]>
    Signed-off-by: Kleber Sacilotto de Souza <[email protected]>

Copied from master

Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: Ubuntu-aws-5.15.0-1014.18
e719bbd 
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: Start new release
3b60069 
Ignore: yes
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: link-to-tracker: update tracking bug
0ae9500 
BugLink: https://bugs.launchpad.net/bugs/1979423
Properties: no-test-build
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: [Config] aws: updateconfigs after rebase
978a9a2 
UBUNTU: [Config] updateconfigs for BLK_DEV_FD_RAWCMD
BugLink: https://bugs.launchpad.net/bugs/1976135

Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: Ubuntu-aws-5.15.0-1015.19
2b4984d 
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: Start new release
14e996b 
Ignore: yes
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: link-to-tracker: update tracking bug
766e5ca 
BugLink: https://bugs.launchpad.net/bugs/1982271
Properties: no-test-build
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: [Config]: aws: Enable speculation mitigations
8459b06 
CVE-2022-29900
CVE-2022-29901
    Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]>

Copied from master

Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: [Config] aws: Disable AMD ACP 6 DMIC Support
cdfa5c1 
BugLink: https://bugs.launchpad.net/bugs/1949245

    This includes setting CONFIG_SND_SOC_AMD_ACP6x and
    CONFIG_SND_SOC_AMD_YC_MACH to 'm'.

    Signed-off-by: Hui Wang <[email protected]>
    Acked-by: Stefan Bader <[email protected]>
    Acked-by: Tim Gardner <[email protected]>
    Signed-off-by: Stefan Bader <[email protected]>

Copied from master

Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: [Config] aws: Enable config option CONFIG_PCIE_EDR
36776e0 
BugLink: https://bugs.launchpad.net/bugs/1965241

    PCIE_EDR is enabling support to handle events generated when a PCIE port
    disconnects to handle errors. From the comments given in the commit which
    adds this option and its help, it sounds like if the OS enables DPC (down-
    stream port control) which allows to control PCIE ports in parallel to the
    firmware, it should also enable EDR.

    Signed-off-by: Michael Reed <[email protected]>
    Acked-by: Stefan Bader <[email protected]>
    [Added annotation enforcement and bug reference, and adjust annotation
     to force arm64 to the same setting as it was before]
    Acked-by: Kleber Sacilotto de Souza <[email protected]>
    Signed-off-by: Stefan Bader <[email protected]>

Copied from master

Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: Ubuntu-aws-5.15.0-1016.20
6130983 
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: Start new release
dc06fae 
Ignore: yes
Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]>
@rtg-canonical
UBUNTU: Ubuntu-aws-5.15.0-1017.21
675e6a5 
Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]>
@rtg-canonical
UBUNTU: Start new release
d1e6e5e 
Ignore: yes
Signed-off-by: Tim Gardner <[email protected]>
@rtg-canonical
UBUNTU: link-to-tracker: update tracking bug
9f35982 
BugLink: https://bugs.launchpad.net/bugs/1983870
Properties: no-test-build
Signed-off-by: Tim Gardner <[email protected]>
rtg-canonical and others added 18 commits July 19, 2023 09:16
@rtg-canonical
UBUNTU: Ubuntu-aws-5.15-5.15.0-1041.46~20.04.1
a68b78c 
Signed-off-by: Tim Gardner <[email protected]>
@@DELPHIX_PATCHSET_START@@
31d8456 
This is a placeholder commit to separate the Ubuntu kernel source and
our patches. Used by kernel_merge_with_upstream() in the linux-pkg repo.
@pzakha
DLPX-71852 iSCSI: journal flooded with "Unable to locate Target IQN" …
8036a3e 
…messages (#2)
DLPX-74216 nfs-server restarts fail when order-5 allocations are exha…
5574ecd 
…usted (#3)
@pzakha
DLPX-72065 Aborted iSCSI command never completes after LUN reset (#4)
971c53c
DLPX-82827 Fix for Solaris NFSv4 client mounts (#19)
83c570c
DLPX-83442 Disable various kernel modules which we don't use (#20)
f1dfb0e
TOOL-16649 CONFIG_MD is needed on the buildserver (#22)
200189e
@pcd1193182
target: login should wait until tx/rx threads have properly started. (#…
6371833 
…21)
DLPX-83701 Make function mnt_add_count() traceable (#24)
7074213
DLPX-84469 Users unable to connect to CIFS mounts (#28)
906dc48
DLPX-84907 CVE-2022-3628 (#29)
c487acd
@sdimitro
DLPX-84985 target: iscsi: fix deadlock in the iSCSI login code (#30)
7d7dc79
DLPX-84995 NFSD: Never call nfsd_file_gc() in foreground paths (#35)
8eba468 
The checks in nfsd_file_acquire() and nfsd_file_put() that directly
invoke filecache garbage collection are intended to keep cache
occupancy between a low- and high-watermark. The reason to limit the
capacity of the filecache is to keep filecache lookups reasonably
fast.

However, invoking garbage collection at those points has some
undesirable negative impacts. Files that are held open by NFSv4
clients often push the occupancy of the filecache over these
watermarks. At that point:

- Every call to nfsd_file_acquire() and nfsd_file_put() results in
  an LRU walk. This has the same effect on lookup latency as long
  chains in the hash table.
- Garbage collection will then run on every nfsd thread, causing a
  lot of unnecessary lock contention.
- Limiting cache capacity pushes out files used only by NFSv3
  clients, which are the type of files the filecache is supposed to
  help.

To address those negative impacts, remove the direct calls to the
garbage collector.
@sumedhbala-delphix
DLPX-84906 Disable frame buffer drivers
b6743af 
PR URL: https://www.github.com/delphix/linux-kernel-aws/pull/36
@palash-gandhi
DLPX-86177 Azure Accelerated networking broken because Mellanox drive…
fe87fad 
…rs absent in kernel (#37)

PR URL: https://www.github.com/delphix/linux-kernel-aws/pull/37
DLPX-86675 Disk quota exceeded when unpacking an upgrade image (#44)
781cd66
DLPX-87344 Fix kernel merge conflict with upstream
6e87f48
@prakashsurya prakashsurya force-pushed the dlpx/pr/prakashsurya/870bc6b5-3652-42d6-872e-174c339c0953 branch from 44c8eda to 1530382 Compare September 1, 2023 18:47
@prakashsurya prakashsurya force-pushed the dlpx/pr/prakashsurya/870bc6b5-3652-42d6-872e-174c339c0953 branch from 1530382 to 8c03b28 Compare September 1, 2023 18:49
delphix-devops-bot pushed a commit that referenced this pull request Mar 21, 2024
@smb49
mptcp: more conservative check for zero probes
4c023ae 
BugLink: https://bugs.launchpad.net/bugs/2049417

[ Upstream commit 72377ab ]

Christoph reported that the MPTCP protocol can find the subflow-level
write queue unexpectedly not empty while crafting a zero-window probe,
hitting a warning:

------------[ cut here ]------------
WARNING: CPU: 0 PID: 188 at net/mptcp/protocol.c:1312 mptcp_sendmsg_frag+0xc06/0xe70
Modules linked in:
CPU: 0 PID: 188 Comm: kworker/0:2 Not tainted 6.6.0-rc2-g1176aa719d7a #47
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-2.el7 04/01/2014
Workqueue: events mptcp_worker
RIP: 0010:mptcp_sendmsg_frag+0xc06/0xe70 net/mptcp/protocol.c:1312
RAX: 47d0530de347ff6a RBX: 47d0530de347ff6b RCX: ffff8881015d3c00
RDX: ffff8881015d3c00 RSI: 47d0530de347ff6b RDI: 47d0530de347ff6b
RBP: 47d0530de347ff6b R08: ffffffff8243c6a8 R09: ffffffff82042d9c
R10: 0000000000000002 R11: ffffffff82056850 R12: ffff88812a13d580
R13: 0000000000000001 R14: ffff88812b375e50 R15: ffff88812bbf3200
FS:  0000000000000000(0000) GS:ffff88813bc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000695118 CR3: 0000000115dfc001 CR4: 0000000000170ef0
Call Trace:
 <TASK>
 __subflow_push_pending+0xa4/0x420 net/mptcp/protocol.c:1545
 __mptcp_push_pending+0x128/0x3b0 net/mptcp/protocol.c:1614
 mptcp_release_cb+0x218/0x5b0 net/mptcp/protocol.c:3391
 release_sock+0xf6/0x100 net/core/sock.c:3521
 mptcp_worker+0x6e8/0x8f0 net/mptcp/protocol.c:2746
 process_scheduled_works+0x341/0x690 kernel/workqueue.c:2630
 worker_thread+0x3a7/0x610 kernel/workqueue.c:2784
 kthread+0x143/0x180 kernel/kthread.c:388
 ret_from_fork+0x4d/0x60 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:304
 </TASK>

The root cause of the issue is that expectations are wrong: e.g. due
to MPTCP-level re-injection we can hit the critical condition.

Explicitly avoid the zero-window probe when the subflow write queue
is not empty and drop the related warnings.

Reported-by: Christoph Paasch <[email protected]>
Closes: multipath-tcp/mptcp_net-next#444
Fixes: f70cad1 ("mptcp: stop relying on tcp_tx_skb_cache")
Cc: [email protected]
Reviewed-by: Mat Martineau <[email protected]>
Signed-off-by: Paolo Abeni <[email protected]>
Signed-off-by: Mat Martineau <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
Signed-off-by: Roxana Nicolescu <[email protected]>
Signed-off-by: Stefan Bader <[email protected]>
delphix-devops-bot pushed a commit that referenced this pull request Sep 14, 2024
@floatious @roxanan1996
ata: libata-core: Fix double free on error
c959429 
BugLink: https://bugs.launchpad.net/bugs/2073765

commit ab9e0c5 upstream.

If e.g. the ata_port_alloc() call in ata_host_alloc() fails, we will jump
to the err_out label, which will call devres_release_group().
devres_release_group() will trigger a call to ata_host_release().
ata_host_release() calls kfree(host), so executing the kfree(host) in
ata_host_alloc() will lead to a double free:

kernel BUG at mm/slub.c:553!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
CPU: 11 PID: 599 Comm: (udev-worker) Not tainted 6.10.0-rc5 #47
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014
RIP: 0010:kfree+0x2cf/0x2f0
Code: 5d 41 5e 41 5f 5d e9 80 d6 ff ff 4d 89 f1 41 b8 01 00 00 00 48 89 d9 48 89 da
RSP: 0018:ffffc90000f377f0 EFLAGS: 00010246
RAX: ffff888112b1f2c0 RBX: ffff888112b1f2c0 RCX: ffff888112b1f320
RDX: 000000000000400b RSI: ffffffffc02c9de5 RDI: ffff888112b1f2c0
RBP: ffffc90000f37830 R08: 0000000000000000 R09: 0000000000000000
R10: ffffc90000f37610 R11: 617461203a736b6e R12: ffffea00044ac780
R13: ffff888100046400 R14: ffffffffc02c9de5 R15: 0000000000000006
FS:  00007f2f1cabe980(0000) GS:ffff88813b380000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2f1c3acf75 CR3: 0000000111724000 CR4: 0000000000750ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? __die_body.cold+0x19/0x27
 ? die+0x2e/0x50
 ? do_trap+0xca/0x110
 ? do_error_trap+0x6a/0x90
 ? kfree+0x2cf/0x2f0
 ? exc_invalid_op+0x50/0x70
 ? kfree+0x2cf/0x2f0
 ? asm_exc_invalid_op+0x1a/0x20
 ? ata_host_alloc+0xf5/0x120 [libata]
 ? ata_host_alloc+0xf5/0x120 [libata]
 ? kfree+0x2cf/0x2f0
 ata_host_alloc+0xf5/0x120 [libata]
 ata_host_alloc_pinfo+0x14/0xa0 [libata]
 ahci_init_one+0x6c9/0xd20 [ahci]

Ensure that we will not call kfree(host) twice, by performing the kfree()
only if the devres_open_group() call failed.

Fixes: dafd6c4 ("libata: ensure host is free'd on error exit paths")
Cc: [email protected]
Reviewed-by: Damien Le Moal <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Niklas Cassel <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Signed-off-by: Portia Stephens <[email protected]>
Signed-off-by: Roxana Nicolescu <[email protected]>
delphix-devops-bot pushed a commit that referenced this pull request Feb 7, 2025
@floatious @smb49
ata: libata-core: Fix double free on error
763b4ff 
BugLink: https://bugs.launchpad.net/bugs/2076435

commit ab9e0c5 upstream.

If e.g. the ata_port_alloc() call in ata_host_alloc() fails, we will jump
to the err_out label, which will call devres_release_group().
devres_release_group() will trigger a call to ata_host_release().
ata_host_release() calls kfree(host), so executing the kfree(host) in
ata_host_alloc() will lead to a double free:

kernel BUG at mm/slub.c:553!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
CPU: 11 PID: 599 Comm: (udev-worker) Not tainted 6.10.0-rc5 #47
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014
RIP: 0010:kfree+0x2cf/0x2f0
Code: 5d 41 5e 41 5f 5d e9 80 d6 ff ff 4d 89 f1 41 b8 01 00 00 00 48 89 d9 48 89 da
RSP: 0018:ffffc90000f377f0 EFLAGS: 00010246
RAX: ffff888112b1f2c0 RBX: ffff888112b1f2c0 RCX: ffff888112b1f320
RDX: 000000000000400b RSI: ffffffffc02c9de5 RDI: ffff888112b1f2c0
RBP: ffffc90000f37830 R08: 0000000000000000 R09: 0000000000000000
R10: ffffc90000f37610 R11: 617461203a736b6e R12: ffffea00044ac780
R13: ffff888100046400 R14: ffffffffc02c9de5 R15: 0000000000000006
FS:  00007f2f1cabe980(0000) GS:ffff88813b380000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2f1c3acf75 CR3: 0000000111724000 CR4: 0000000000750ef0
PKRU: 55555554
Call Trace:
 <TASK>
 ? __die_body.cold+0x19/0x27
 ? die+0x2e/0x50
 ? do_trap+0xca/0x110
 ? do_error_trap+0x6a/0x90
 ? kfree+0x2cf/0x2f0
 ? exc_invalid_op+0x50/0x70
 ? kfree+0x2cf/0x2f0
 ? asm_exc_invalid_op+0x1a/0x20
 ? ata_host_alloc+0xf5/0x120 [libata]
 ? ata_host_alloc+0xf5/0x120 [libata]
 ? kfree+0x2cf/0x2f0
 ata_host_alloc+0xf5/0x120 [libata]
 ata_host_alloc_pinfo+0x14/0xa0 [libata]
 ahci_init_one+0x6c9/0xd20 [ahci]

Ensure that we will not call kfree(host) twice, by performing the kfree()
only if the devres_open_group() call failed.

Fixes: dafd6c4 ("libata: ensure host is free'd on error exit paths")
Cc: [email protected]
Reviewed-by: Damien Le Moal <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Niklas Cassel <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Signed-off-by: Portia Stephens <[email protected]>
Signed-off-by: Roxana Nicolescu <[email protected]>
delphix-devops-bot pushed a commit that referenced this pull request Sep 26, 2025
@smb49
btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref
93bea03 
BugLink: https://bugs.launchpad.net/bugs/2115678

[ Upstream commit bc7e0975093567f51be8e1bdf4aa5900a3cf0b1e ]

btrfs_prelim_ref() calls the old and new reference variables in the
incorrect order. This causes a NULL pointer dereference because oldref
is passed as NULL to trace_btrfs_prelim_ref_insert().

Note, trace_btrfs_prelim_ref_insert() is being called with newref as
oldref (and oldref as NULL) on purpose in order to print out
the values of newref.

To reproduce:
echo 1 > /sys/kernel/debug/tracing/events/btrfs/btrfs_prelim_ref_insert/enable

Perform some writeback operations.

Backtrace:
BUG: kernel NULL pointer dereference, address: 0000000000000018
 #PF: supervisor read access in kernel mode
 #PF: error_code(0x0000) - not-present page
 PGD 115949067 P4D 115949067 PUD 11594a067 PMD 0
 Oops: Oops: 0000 [#1] SMP NOPTI
 CPU: 1 UID: 0 PID: 1188 Comm: fsstress Not tainted 6.15.0-rc2-tester+ #47 PREEMPT(voluntary)  7ca2cef72d5e9c600f0c7718adb6462de8149622
 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-2-gc13ff2cd-prebuilt.qemu.org 04/01/2014
 RIP: 0010:trace_event_raw_event_btrfs__prelim_ref+0x72/0x130
 Code: e8 43 81 9f ff 48 85 c0 74 78 4d 85 e4 0f 84 8f 00 00 00 49 8b 94 24 c0 06 00 00 48 8b 0a 48 89 48 08 48 8b 52 08 48 89 50 10 <49> 8b 55 18 48 89 50 18 49 8b 55 20 48 89 50 20 41 0f b6 55 28 88
 RSP: 0018:ffffce44820077a0 EFLAGS: 00010286
 RAX: ffff8c6b403f9014 RBX: ffff8c6b55825730 RCX: 304994edf9cf506b
 RDX: d8b11eb7f0fdb699 RSI: ffff8c6b403f9010 RDI: ffff8c6b403f9010
 RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000010
 R10: 00000000ffffffff R11: 0000000000000000 R12: ffff8c6b4e8fb000
 R13: 0000000000000000 R14: ffffce44820077a8 R15: ffff8c6b4abd1540
 FS:  00007f4dc6813740(0000) GS:ffff8c6c1d378000(0000) knlGS:0000000000000000
 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
 CR2: 0000000000000018 CR3: 000000010eb42000 CR4: 0000000000750ef0
 PKRU: 55555554
 Call Trace:
  <TASK>
  prelim_ref_insert+0x1c1/0x270
  find_parent_nodes+0x12a6/0x1ee0
  ? __entry_text_end+0x101f06/0x101f09
  ? srso_alias_return_thunk+0x5/0xfbef5
  ? srso_alias_return_thunk+0x5/0xfbef5
  ? srso_alias_return_thunk+0x5/0xfbef5
  ? srso_alias_return_thunk+0x5/0xfbef5
  btrfs_is_data_extent_shared+0x167/0x640
  ? fiemap_process_hole+0xd0/0x2c0
  extent_fiemap+0xa5c/0xbc0
  ? __entry_text_end+0x101f05/0x101f09
  btrfs_fiemap+0x7e/0xd0
  do_vfs_ioctl+0x425/0x9d0
  __x64_sys_ioctl+0x75/0xc0

Signed-off-by: Goldwyn Rodrigues <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
CVE-2025-38034
Signed-off-by: Manuel Diewald <[email protected]>
Signed-off-by: Mehmet Basaran <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.