From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
patches@lists.linux.dev, Wang Yugui <wangyugui@e16-tech.com>,
Josef Bacik <josef@toxicpanda.com>,
Filipe Manana <fdmanana@suse.com>,
David Sterba <dsterba@suse.com>, Sasha Levin <sashal@kernel.org>
Subject: [PATCH 6.7 070/162] btrfs: fix race between ordered extent completion and fiemap
Date: Mon, 4 Mar 2024 21:22:15 +0000 [thread overview]
Message-ID: <20240304211554.097290598@linuxfoundation.org> (raw)
In-Reply-To: <20240304211551.833500257@linuxfoundation.org>
6.7-stable review patch. If anyone has any objections, please let me know.
------------------
From: Filipe Manana <fdmanana@suse.com>
[ Upstream commit a1a4a9ca77f143c00fce69c1239887ff8b813bec ]
For fiemap we recently stopped locking the target extent range for the
whole duration of the fiemap call, in order to avoid a deadlock in a
scenario where the fiemap buffer happens to be a memory mapped range of
the same file. This use case is very unlikely to be useful in practice but
it may be triggered by fuzz testing (syzbot, etc).
However by not locking the target extent range for the whole duration of
the fiemap call we can race with an ordered extent. This happens like
this:
1) The fiemap task finishes processing a file extent item that covers
the file range [512K, 1M[, and that file extent item is the last item
in the leaf currently being processed;
2) And ordered extent for the file range [768K, 2M[, in COW mode,
completes (btrfs_finish_one_ordered()) and the file extent item
covering the range [512K, 1M[ is trimmed to cover the range
[512K, 768K[ and then a new file extent item for the range [768K, 2M[
is inserted in the inode's subvolume tree;
3) The fiemap task calls fiemap_next_leaf_item(), which then calls
btrfs_next_leaf() to find the next leaf / item. This finds that the
the next key following the one we previously processed (its type is
BTRFS_EXTENT_DATA_KEY and its offset is 512K), is the key corresponding
to the new file extent item inserted by the ordered extent, which has
a type of BTRFS_EXTENT_DATA_KEY and an offset of 768K;
4) Later the fiemap code ends up at emit_fiemap_extent() and triggers
the warning:
if (cache->offset + cache->len > offset) {
WARN_ON(1);
return -EINVAL;
}
Since we get 1M > 768K, because the previously emitted entry for the
old extent covering the file range [512K, 1M[ ends at an offset that
is greater than the new extent's start offset (768K). This makes fiemap
fail with -EINVAL besides triggering the warning that produces a stack
trace like the following:
[1621.677651] ------------[ cut here ]------------
[1621.677656] WARNING: CPU: 1 PID: 204366 at fs/btrfs/extent_io.c:2492 emit_fiemap_extent+0x84/0x90 [btrfs]
[1621.677899] Modules linked in: btrfs blake2b_generic (...)
[1621.677951] CPU: 1 PID: 204366 Comm: pool Not tainted 6.8.0-rc5-btrfs-next-151+ #1
[1621.677954] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014
[1621.677956] RIP: 0010:emit_fiemap_extent+0x84/0x90 [btrfs]
[1621.678033] Code: 2b 4c 89 63 (...)
[1621.678035] RSP: 0018:ffffab16089ffd20 EFLAGS: 00010206
[1621.678037] RAX: 00000000004fa000 RBX: ffffab16089ffe08 RCX: 0000000000009000
[1621.678039] RDX: 00000000004f9000 RSI: 00000000004f1000 RDI: ffffab16089ffe90
[1621.678040] RBP: 00000000004f9000 R08: 0000000000001000 R09: 0000000000000000
[1621.678041] R10: 0000000000000000 R11: 0000000000001000 R12: 0000000041d78000
[1621.678043] R13: 0000000000001000 R14: 0000000000000000 R15: ffff9434f0b17850
[1621.678044] FS: 00007fa6e20006c0(0000) GS:ffff943bdfa40000(0000) knlGS:0000000000000000
[1621.678046] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[1621.678048] CR2: 00007fa6b0801000 CR3: 000000012d404002 CR4: 0000000000370ef0
[1621.678053] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[1621.678055] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[1621.678056] Call Trace:
[1621.678074] <TASK>
[1621.678076] ? __warn+0x80/0x130
[1621.678082] ? emit_fiemap_extent+0x84/0x90 [btrfs]
[1621.678159] ? report_bug+0x1f4/0x200
[1621.678164] ? handle_bug+0x42/0x70
[1621.678167] ? exc_invalid_op+0x14/0x70
[1621.678170] ? asm_exc_invalid_op+0x16/0x20
[1621.678178] ? emit_fiemap_extent+0x84/0x90 [btrfs]
[1621.678253] extent_fiemap+0x766/0xa30 [btrfs]
[1621.678339] btrfs_fiemap+0x45/0x80 [btrfs]
[1621.678420] do_vfs_ioctl+0x1e4/0x870
[1621.678431] __x64_sys_ioctl+0x6a/0xc0
[1621.678434] do_syscall_64+0x52/0x120
[1621.678445] entry_SYSCALL_64_after_hwframe+0x6e/0x76
There's also another case where before calling btrfs_next_leaf() we are
processing a hole or a prealloc extent and we had several delalloc ranges
within that hole or prealloc extent. In that case if the ordered extents
complete before we find the next key, we may end up finding an extent item
with an offset smaller than (or equals to) the offset in cache->offset.
So fix this by changing emit_fiemap_extent() to address these three
scenarios like this:
1) For the first case, steps listed above, adjust the length of the
previously cached extent so that it does not overlap with the current
extent, emit the previous one and cache the current file extent item;
2) For the second case where he had a hole or prealloc extent with
multiple delalloc ranges inside the hole or prealloc extent's range,
and the current file extent item has an offset that matches the offset
in the fiemap cache, just discard what we have in the fiemap cache and
assign the current file extent item to the cache, since it's more up
to date;
3) For the third case where he had a hole or prealloc extent with
multiple delalloc ranges inside the hole or prealloc extent's range
and the offset of the file extent item we just found is smaller than
what we have in the cache, just skip the current file extent item
if its range end at or behind the cached extent's end, because we may
have emitted (to the fiemap user space buffer) delalloc ranges that
overlap with the current file extent item's range. If the file extent
item's range goes beyond the end offset of the cached extent, just
emit the cached extent and cache a subrange of the file extent item,
that goes from the end offset of the cached extent to the end offset
of the file extent item.
Dealing with those cases in those ways makes everything consistent by
reflecting the current state of file extent items in the btree and
without emitting extents that have overlapping ranges (which would be
confusing and violating expectations).
This issue could be triggered often with test case generic/561, and was
also hit and reported by Wang Yugui.
Reported-by: Wang Yugui <wangyugui@e16-tech.com>
Link: https://lore.kernel.org/linux-btrfs/20240223104619.701F.409509F4@e16-tech.com/
Fixes: b0ad381fa769 ("btrfs: fix deadlock with fiemap and extent locking")
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
fs/btrfs/extent_io.c | 103 ++++++++++++++++++++++++++++++++++++++++---
1 file changed, 96 insertions(+), 7 deletions(-)
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index 197b41d02735b..3f795f105a645 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -2436,6 +2436,7 @@ static int emit_fiemap_extent(struct fiemap_extent_info *fieinfo,
struct fiemap_cache *cache,
u64 offset, u64 phys, u64 len, u32 flags)
{
+ u64 cache_end;
int ret = 0;
/* Set at the end of extent_fiemap(). */
@@ -2445,15 +2446,102 @@ static int emit_fiemap_extent(struct fiemap_extent_info *fieinfo,
goto assign;
/*
- * Sanity check, extent_fiemap() should have ensured that new
- * fiemap extent won't overlap with cached one.
- * Not recoverable.
+ * When iterating the extents of the inode, at extent_fiemap(), we may
+ * find an extent that starts at an offset behind the end offset of the
+ * previous extent we processed. This happens if fiemap is called
+ * without FIEMAP_FLAG_SYNC and there are ordered extents completing
+ * while we call btrfs_next_leaf() (through fiemap_next_leaf_item()).
*
- * NOTE: Physical address can overlap, due to compression
+ * For example we are in leaf X processing its last item, which is the
+ * file extent item for file range [512K, 1M[, and after
+ * btrfs_next_leaf() releases the path, there's an ordered extent that
+ * completes for the file range [768K, 2M[, and that results in trimming
+ * the file extent item so that it now corresponds to the file range
+ * [512K, 768K[ and a new file extent item is inserted for the file
+ * range [768K, 2M[, which may end up as the last item of leaf X or as
+ * the first item of the next leaf - in either case btrfs_next_leaf()
+ * will leave us with a path pointing to the new extent item, for the
+ * file range [768K, 2M[, since that's the first key that follows the
+ * last one we processed. So in order not to report overlapping extents
+ * to user space, we trim the length of the previously cached extent and
+ * emit it.
+ *
+ * Upon calling btrfs_next_leaf() we may also find an extent with an
+ * offset smaller than or equals to cache->offset, and this happens
+ * when we had a hole or prealloc extent with several delalloc ranges in
+ * it, but after btrfs_next_leaf() released the path, delalloc was
+ * flushed and the resulting ordered extents were completed, so we can
+ * now have found a file extent item for an offset that is smaller than
+ * or equals to what we have in cache->offset. We deal with this as
+ * described below.
*/
- if (cache->offset + cache->len > offset) {
- WARN_ON(1);
- return -EINVAL;
+ cache_end = cache->offset + cache->len;
+ if (cache_end > offset) {
+ if (offset == cache->offset) {
+ /*
+ * We cached a dealloc range (found in the io tree) for
+ * a hole or prealloc extent and we have now found a
+ * file extent item for the same offset. What we have
+ * now is more recent and up to date, so discard what
+ * we had in the cache and use what we have just found.
+ */
+ goto assign;
+ } else if (offset > cache->offset) {
+ /*
+ * The extent range we previously found ends after the
+ * offset of the file extent item we found and that
+ * offset falls somewhere in the middle of that previous
+ * extent range. So adjust the range we previously found
+ * to end at the offset of the file extent item we have
+ * just found, since this extent is more up to date.
+ * Emit that adjusted range and cache the file extent
+ * item we have just found. This corresponds to the case
+ * where a previously found file extent item was split
+ * due to an ordered extent completing.
+ */
+ cache->len = offset - cache->offset;
+ goto emit;
+ } else {
+ const u64 range_end = offset + len;
+
+ /*
+ * The offset of the file extent item we have just found
+ * is behind the cached offset. This means we were
+ * processing a hole or prealloc extent for which we
+ * have found delalloc ranges (in the io tree), so what
+ * we have in the cache is the last delalloc range we
+ * found while the file extent item we found can be
+ * either for a whole delalloc range we previously
+ * emmitted or only a part of that range.
+ *
+ * We have two cases here:
+ *
+ * 1) The file extent item's range ends at or behind the
+ * cached extent's end. In this case just ignore the
+ * current file extent item because we don't want to
+ * overlap with previous ranges that may have been
+ * emmitted already;
+ *
+ * 2) The file extent item starts behind the currently
+ * cached extent but its end offset goes beyond the
+ * end offset of the cached extent. We don't want to
+ * overlap with a previous range that may have been
+ * emmitted already, so we emit the currently cached
+ * extent and then partially store the current file
+ * extent item's range in the cache, for the subrange
+ * going the cached extent's end to the end of the
+ * file extent item.
+ */
+ if (range_end <= cache_end)
+ return 0;
+
+ if (!(flags & (FIEMAP_EXTENT_ENCODED | FIEMAP_EXTENT_DELALLOC)))
+ phys += cache_end - offset;
+
+ offset = cache_end;
+ len = range_end - cache_end;
+ goto emit;
+ }
}
/*
@@ -2473,6 +2561,7 @@ static int emit_fiemap_extent(struct fiemap_extent_info *fieinfo,
return 0;
}
+emit:
/* Not mergeable, need to submit cached one */
ret = fiemap_fill_next_extent(fieinfo, cache->offset, cache->phys,
cache->len, cache->flags);
--
2.43.0
next prev parent reply other threads:[~2024-03-04 21:29 UTC|newest]
Thread overview: 182+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 21:21 [PATCH 6.7 000/162] 6.7.9-rc1 review Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 001/162] btrfs: fix deadlock with fiemap and extent locking Greg Kroah-Hartman
2024-03-06 12:39 ` Filipe Manana
2024-03-06 13:47 ` Greg Kroah-Hartman
2024-03-11 9:15 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-11 18:41 ` David Sterba
2024-03-11 19:23 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-11 20:06 ` Filipe Manana
2024-03-13 13:42 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-13 13:47 ` Filipe Manana
2024-03-12 16:41 ` David Sterba
2024-03-04 21:21 ` [PATCH 6.7 002/162] mtd: spinand: gigadevice: Fix the get ecc status issue Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 003/162] ice: fix connection state of DPLL and out pin Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 004/162] ice: fix dpll input pin phase_adjust value updates Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 005/162] ice: fix dpll and dpll_pin data access on PF reset Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 006/162] ice: fix dpll periodic work data updates " Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 007/162] ice: fix pin phase adjust " Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 008/162] spi: cadence-qspi: fix pointer reference in runtime PM hooks Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 009/162] spi: cadence-qspi: remove system-wide suspend helper calls from " Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 010/162] netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 011/162] netlink: add nla be16/32 types to minlen array Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 012/162] net: ip_tunnel: prevent perpetual headroom growth Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 013/162] net: mctp: take ownership of skb in mctp_local_output Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 014/162] net: dpaa: fman_memac: accept phy-interface-type = "10gbase-r" in the device tree Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 015/162] tun: Fix xdp_rxq_infos queue_index when detaching Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 016/162] cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 017/162] net: veth: clear GRO when clearing XDP even when down Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 018/162] ipv6: fix potential "struct net" leak in inet6_rtm_getaddr() Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 019/162] lan78xx: enable auto speed configuration for LAN7850 if no EEPROM is detected Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 020/162] veth: try harder when allocating queue memory Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 021/162] net: usb: dm9601: fix wrong return value in dm9601_mdio_read Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 022/162] net: lan78xx: fix "softirq work is pending" error Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 023/162] uapi: in6: replace temporary label with rfc9486 Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 024/162] stmmac: Clear variable when destroying workqueue Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 025/162] Bluetooth: hci_sync: Check the correct flag before starting a scan Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 026/162] Bluetooth: Avoid potential use-after-free in hci_error_reset Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 027/162] Bluetooth: hci_sync: Fix accept_list when attempting to suspend Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 028/162] Bluetooth: hci_event: Fix wrongly recorded wakeup BD_ADDR Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 029/162] Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 030/162] Bluetooth: Enforce validation on max value of connection interval Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 031/162] Bluetooth: qca: Fix wrong event type for patch config command Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 032/162] Bluetooth: hci_qca: Set BDA quirk bit if fwnode exists in DT Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 033/162] Bluetooth: qca: Fix triggering coredump implementation Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 034/162] netfilter: nf_tables: allow NFPROTO_INET in nft_(match/target)_validate() Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 035/162] netfilter: bridge: confirm multicast packets before passing them up the stack Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 036/162] tools: ynl: fix handling of multiple mcast groups Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 037/162] rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 038/162] igb: extend PTP timestamp adjustments to i211 Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 039/162] net: hsr: Use correct offset for HSR TLV values in supervisory HSR frames Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 040/162] tls: decrement decrypt_pending if no async completion will be called Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 041/162] tls: fix peeking with sync+async decryption Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 042/162] tls: separate no-async decryption request handling from async Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 043/162] tls: fix use-after-free on failed backlog decryption Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 044/162] riscv: tlb: fix __p*d_free_tlb() Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 045/162] efi/capsule-loader: fix incorrect allocation size Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 046/162] power: supply: bq27xxx-i2c: Do not free non existing IRQ Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 047/162] ASoC: cs35l56: Must clear HALO_STATE before issuing SYSTEM_RESET Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 048/162] ALSA: Drop leftover snd-rtctimer stuff from Makefile Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 049/162] ASoC: qcom: Fix uninitialized pointer dmactl Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 050/162] gpu: host1x: Skip reset assert on Tegra186 Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 051/162] riscv: mm: fix NOCACHE_THEAD does not set bit[61] correctly Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 052/162] riscv: Fix build error if !CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 053/162] ASoC: cs35l56: cs35l56_component_remove() must clear cs35l56->component Greg Kroah-Hartman
2024-03-04 21:21 ` [PATCH 6.7 054/162] ASoC: cs35l56: cs35l56_component_remove() must clean up wm_adsp Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 055/162] ASoC: cs35l56: Dont add the same register patch multiple times Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 056/162] ASoC: cs35l56: Fix for initializing ASP1 mixer registers Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 057/162] ASoC: cs35l56: Fix misuse of wm_adsp part string for silicon revision Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 058/162] ASoC: cs35l56: Fix deadlock in ASP1 mixer register initialization Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 059/162] ASoC: soc-card: Fix missing locking in snd_soc_card_get_kcontrol() Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 060/162] RISC-V: Ignore V from the riscv,isa DT property on older T-Head CPUs Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 061/162] drm/tegra: Remove existing framebuffer only if we support display Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 062/162] fbcon: always restore the old font data in fbcon_do_set_font() Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 063/162] afs: Fix endless loop in directory parsing Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 064/162] drm/amd/display: Prevent potential buffer overflow in map_hw_resources Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 065/162] drivers: perf: added capabilities for legacy PMU Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 066/162] drivers: perf: ctr_get_width function for legacy is not defined Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 067/162] Revert "riscv: mm: support Svnapot in huge vmap" Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 068/162] riscv: Fix pte_leaf_size() for NAPOT Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 069/162] riscv: Sparse-Memory/vmemmap out-of-bounds fix Greg Kroah-Hartman
2024-03-04 21:22 ` Greg Kroah-Hartman [this message]
2024-03-04 21:22 ` [PATCH 6.7 071/162] drm/nouveau: keep DMA buffers required for suspend/resume Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 072/162] of: property: fw_devlink: Fix stupid bug in remote-endpoint parsing Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 073/162] tomoyo: fix UAF write bug in tomoyo_write_control() Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 074/162] ALSA: firewire-lib: fix to check cycle continuity Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 075/162] ALSA: ump: Fix the discard error code from snd_ump_legacy_open() Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 076/162] ALSA: hda/realtek: Fix top speaker connection on Dell Inspiron 16 Plus 7630 Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 077/162] ALSA: hda/realtek: tas2781: enable subwoofer volume control Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 078/162] ALSA: hda/realtek: Enable Mute LED on HP 840 G8 (MB 8AB8) Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 079/162] ALSA: hda/realtek: fix mute/micmute LED For HP mt440 Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 080/162] ALSA: hda/realtek: Add special fixup for Lenovo 14IRP8 Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 081/162] Bluetooth: hci_bcm4377: do not mark valid bd_addr as invalid Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 082/162] landlock: Fix asymmetric private inodes referring Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 083/162] gtp: fix use-after-free and null-ptr-deref in gtp_newlink() Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 084/162] mm: cachestat: fix folio read-after-free in cache walk Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 085/162] mtd: rawnand: marvell: fix layouts Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 086/162] wifi: nl80211: reject iftype change with mesh ID change Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 087/162] btrfs: fix double free of anonymous device after snapshot creation failure Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 088/162] btrfs: dev-replace: properly validate device names Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 089/162] btrfs: send: dont issue unnecessary zero writes for trailing hole Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 090/162] Revert "drm/amd/pm: resolve reboot exception for si oland" Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 091/162] drm/buddy: fix range bias Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 092/162] drm/amdgpu/pm: Fix the power1_min_cap value Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 093/162] drm/amd/display: Add monitor patch for specific eDP Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 094/162] soc: qcom: pmic_glink: Fix boot when QRTR=m Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 095/162] dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 096/162] crypto: arm64/neonbs - fix out-of-bounds access on short input Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 097/162] dmaengine: ptdma: use consistent DMA masks Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 098/162] dmaengine: fsl-edma: correct calculation of nbytes in multi-fifo scenario Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 099/162] dmaengine: fsl-qdma: init irq after reg initialization Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 100/162] mmc: mmci: stm32: fix DMA API overlapping mappings warning Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 101/162] mmc: core: Fix eMMC initialization with 1-bit bus connection Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 102/162] mmc: sdhci-xenon: add timeout for PHY init complete Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 103/162] mmc: sdhci-xenon: fix PHY init clock stability Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 104/162] ceph: switch to corrected encoding of max_xattr_size in mdsmap Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 105/162] RISC-V: Drop invalid test from CONFIG_AS_HAS_OPTION_ARCH Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 106/162] riscv: add CALLER_ADDRx support Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 107/162] riscv: Fix enabling cbo.zero when running in M-mode Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 108/162] riscv: Save/restore envcfg CSR during CPU suspend Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 109/162] power: supply: mm8013: select REGMAP_I2C Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 110/162] kbuild: Add -Wa,--fatal-warnings to as-instr invocation Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 111/162] iommufd: Fix iopt_access_list_id overwrite bug Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 112/162] iommufd: Fix protection fault in iommufd_test_syz_conv_iova Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 113/162] efivarfs: Request at most 512 bytes for variable names Greg Kroah-Hartman
2024-03-04 21:22 ` [PATCH 6.7 114/162] pmdomain: arm: Fix NULL dereference on scmi_perf_domain removal Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 115/162] pmdomain: qcom: rpmhpd: Fix enabled_corner aggregation Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 116/162] fprobe: Fix to allocate entry_data_size buffer with rethook instances Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 117/162] mm/debug_vm_pgtable: fix BUG_ON with pud advanced test Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 118/162] mm/vmscan: fix a bug calling wakeup_kswapd() with a wrong zone index Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 119/162] x86/e820: Dont reserve SETUP_RNG_SEED in e820 Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 120/162] x86/cpu: Allow reducing x86_phys_bits during early_identify_cpu() Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 121/162] x86/cpu/intel: Detect TME keyid bits before setting MTRR mask registers Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 122/162] mptcp: map v4 address to v6 when destroying subflow Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 123/162] mptcp: avoid printing warning once on client side Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 124/162] mptcp: push at DSS boundaries Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 125/162] selftests: mptcp: join: add ss mptcp support check Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 126/162] mptcp: fix snd_wnd initialization for passive socket Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 127/162] mptcp: fix potential wake-up event loss Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 128/162] mptcp: fix double-free on socket dismantle Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 129/162] mptcp: fix possible deadlock in subflow diag Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 130/162] mfd: twl6030-irq: Revert to use of_match_device() Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 131/162] NFS: Fix data corruption caused by congestion Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 132/162] af_unix: Fix task hung while purging oob_skb in GC Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 133/162] af_unix: Drop oob_skb ref before purging queue " Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 134/162] ASoC: cs35l56: fix reversed if statement in cs35l56_dspwait_asp1tx_put() Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 135/162] dmaengine: dw-edma: Fix the ch_count hdma callback Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 136/162] dmaengine: dw-edma: Fix wrong interrupt bit set for HDMA Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 137/162] dmaengine: dw-edma: HDMA_V0_REMOTEL_STOP_INT_EN typo fix Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 138/162] dmaengine: dw-edma: Add HDMA remote interrupt configuration Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 139/162] dmaengine: dw-edma: HDMA: Add sync read before starting the DMA transfer in remote setup Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 140/162] dmaengine: dw-edma: eDMA: " Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 141/162] phy: freescale: phy-fsl-imx8-mipi-dphy: Fix alias name to use dashes Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 142/162] phy: qcom: phy-qcom-m31: fix wrong pointer pass to PTR_ERR() Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 143/162] phy: qcom-qmp-usb: fix v3 offsets data Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 144/162] dmaengine: idxd: Remove shadow Event Log head stored in idxd Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 145/162] dmaengine: idxd: Ensure safe user copy of completion record Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 146/162] powerpc/pseries/iommu: IOMMU table is not initialized for kdump over SR-IOV Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 147/162] powerpc/rtas: use correct function name for resetting TCE tables Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 148/162] gpio: 74x164: Enable output pins after registers are reset Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 149/162] gpiolib: Fix the error path order in gpiochip_add_data_with_key() Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 150/162] gpio: fix resource unwinding order in error path Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 151/162] block: define bvec_iter as __packed __aligned(4) Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 152/162] x86/entry_64: Add VERW just before userspace transition Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 153/162] x86/entry_32: " Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 154/162] x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 155/162] KVM/VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 156/162] KVM/VMX: Move VERW closer to VMentry for MDS mitigation Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 157/162] selftests: mptcp: add evts_get_info helper Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 158/162] selftests: mptcp: add chk_subflows_total helper Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 159/162] selftests: mptcp: update userspace pm test helpers Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 160/162] selftests: mptcp: add mptcp_lib_is_v6 Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 161/162] selftests: mptcp: rm subflow with v4/v4mapped addr Greg Kroah-Hartman
2024-03-04 21:23 ` [PATCH 6.7 162/162] drm/nouveau: dont fini scheduler before entity flush Greg Kroah-Hartman
2024-03-04 22:48 ` [PATCH 6.7 000/162] 6.7.9-rc1 review SeongJae Park
2024-03-04 23:05 ` Luna Jernberg
2024-03-06 14:52 ` Greg Kroah-Hartman
2024-03-06 14:54 ` Luna Jernberg
2024-03-06 14:56 ` Luna Jernberg
2024-03-04 23:31 ` Ron Economos
2024-03-05 7:41 ` Greg Kroah-Hartman
2024-03-05 7:44 ` Luna Jernberg
2024-03-05 4:32 ` Bagas Sanjaya
2024-03-05 18:52 ` Shuah Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240304211554.097290598@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wangyugui@e16-tech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).