7.0.4-rc1 review
Subsystems (5)
Greg Kroah-Hartman
maintainerPATCH 272/307 ceph: fix num_ops off-by-one when crypto allocation fails
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sam Edwards <[email protected]>
commit a0d9555bf9eaeba34fe6b6bb86f442fe08ba3842 upstream.
move_dirty_folio_in_page_array() may fail if the file is encrypted, the dirty folio is not the first in the batch, and it fails to allocate a bounce buffer to hold the ciphertext. When that happens, ceph_process_folio_batch() simply redirties the folio and flushes the current batch -- it can retry that folio in a future batch.
However, if this failed folio is not contiguous with the last folio that did make it into the batch, then ceph_process_folio_batch() has already incremented ceph_wbc->num_ops; because it doesn't follow through and add the discontiguous folio to the array, ceph_submit_write() -- which expects that ceph_wbc->num_ops accurately reflects the number of contiguous ranges (and therefore the required number of "write extent" ops) in the writeback -- will panic the kernel:
BUG_ON(ceph_wbc->op_idx + 1 != req->r_num_ops);
This issue can be reproduced on affected kernels by writing to fscrypt-enabled CephFS file(s) with a 4KiB-written/4KiB-skipped/repeat pattern (total filesize should not matter) and gradually increasing the system's memory pressure until a bounce buffer allocation fails.
Fix this crash by decrementing ceph_wbc->num_ops back to the correct value when move_dirty_folio_in_page_array() fails, but the folio already started counting a new (i.e. still-empty) extent.
The defect corrected by this patch has existed since 2022 (see first Fixes:), but another bug blocked multi-folio encrypted writeback until recently (see second Fixes:). The second commit made it into 6.18.16, 6.19.6, and 7.0-rc1, unmasking the panic in those versions. This patch therefore fixes a regression (panic) introduced by cac190c7674f.
--- fs/ceph/addr.c | 4 ++++ 1 file changed, 4 insertions(+)
fs/ceph/addr.c +4 -0
@@ -1365,6 +1365,10 @@ void ceph_process_folio_batch(struct add rc =move_dirty_folio_in_page_array (mapping, wbc, ceph_wbc, folio);if (rc) { +/* Did we just begin a new contiguous op? Nevermind! */ +if (ceph_wbc->len ==0 ) + ceph_wbc->num_ops--; +folio_redirty_for_writepage (wbc, folio);folio_unlock (folio);break ;
Greg Kroah-Hartman
maintainerPATCH 273/307 ceph: only d_add() negative dentries when they are unhashed
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Max Kellermann <[email protected]>
commit 803447f93d75ab6e40c85e6d12b5630d281d70d6 upstream.
Ceph can call d_add(dentry, NULL) on a negative dentry that is already present in the primary dcache hash.
In the current VFS that is not safe. d_add() goes through __d_add() to __d_rehash(), which unconditionally reinserts dentry->d_hash into the hlist_bl bucket. If the dentry is already hashed, reinserting the same node can corrupt the bucket, including creating a self-loop. Once that happens, __d_lookup() can spin forever in the hlist_bl walk, typically looping only on the d_name.hash mismatch check and eventually triggering RCU stall reports like this one:
rcu: INFO: rcu_sched self-detected stall on CPU rcu: 87-....: (2100 ticks this GP) idle=3a4c/1/0x4000000000000000 softirq=25003319/25003319 fqs=829 rcu: (t=2101 jiffies g=79058445 q=698988 ncpus=192) CPU: 87 UID: 2952868916 PID: 3933303 Comm: php-cgi8.3 Not tainted 6.18.17-i1-amd #950 NONE Hardware name: Dell Inc. PowerEdge R7615/0G9DHV, BIOS 1.6.6 09/22/2023 RIP: 0010:__d_lookup+0x46/0xb0 Code: c1 e8 07 48 8d 04 c2 48 8b 00 49 89 fc 49 89 f5 48 89 c3 48 83 e3 fe 48 83 f8 01 77 0f eb 2d 0f 1f 44 00 00 48 8b 1b 48 85 db <74> 20 39 6b 18 75 f3 48 8d 7b 78 e8 ba 85 d0 00 4c 39 63 10 74 1f RSP: 0018:ff745a70c8253898 EFLAGS: 00000282 RAX: ff26e470054cb208 RBX: ff26e470054cb208 RCX: 000000006e958966 RDX: ff26e48267340000 RSI: ff745a70c82539b0 RDI: ff26e458f74655c0 RBP: 000000006e958966 R08: 0000000000000180 R09: 9cd08d909b919a89 R10: ff26e458f74655c0 R11: 0000000000000000 R12: ff26e458f74655c0 R13: ff745a70c82539b0 R14: d0d0d0d0d0d0d0d0 R15: 2f2f2f2f2f2f2f2f FS: 00007f5770896980(0000) GS:ff26e482c5d88000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f5764de50c0 CR3: 000000a72abb5001 CR4: 0000000000771ef0 PKRU: 55555554 Call Trace: <TASK> lookup_fast+0x9f/0x100 walk_component+0x1f/0x150 link_path_walk+0x20e/0x3d0 path_lookupat+0x68/0x180 filename_lookup+0xdc/0x1e0 vfs_statx+0x6c/0x140 vfs_fstatat+0x67/0xa0 __do_sys_newfstatat+0x24/0x60 do_syscall_64+0x6a/0x230 entry_SYSCALL_64_after_hwframe+0x76/0x7e
This is reachable with reused cached negative dentries. A Ceph lookup or atomic_open can be handed a negative dentry that is already hashed, and fs/ceph/dir.c then hits one of two paths that incorrectly assume "negative" also means "unhashed":
- ceph_finish_lookup():
MDS reply is -ENOENT with no trace
-> d_add(dentry, NULL)
- ceph_lookup():
local ENOENT fast path for a complete directory with shared caps -> d_add(dentry, NULL)
Both paths can therefore re-add an already-hashed negative dentry.
Ceph already uses the correct pattern elsewhere: ceph_fill_trace() only calls d_add(dn, NULL) for a negative null-dentry reply when d_unhashed(dn) is true.
Fix both fs/ceph/dir.c sites the same way: only call d_add() for a negative dentry when it is actually unhashed. If the negative dentry is already hashed, leave it in place and reuse it as-is.
This preserves the existing behavior for unhashed dentries while avoiding d_hash list corruption for reused hashed negatives.
--- fs/ceph/dir.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
fs/ceph/dir.c +4 -2
@@ -769,7 +769,8 @@ struct dentry *ceph_finish_lookup(structd_drop (dentry); err = -ENOENT ; }else { -d_add (dentry,NULL ); +if (d_unhashed (dentry)) +d_add (dentry,NULL ); } } }
@@ -840,7 +841,8 @@ static struct dentry *ceph_lookup(structspin_unlock (&ci->i_ceph_lock);doutc (cl," dir %llx.%llx complete, -ENOENT\n" ,ceph_vinop (dir)); -d_add (dentry,NULL ); +if (d_unhashed (dentry)) +d_add (dentry,NULL ); di->lease_shared_gen =atomic_read (&ci->i_shared_gen);return NULL ; }
Greg Kroah-Hartman
maintainerPATCH 274/307 gtp: disable BH before calling udp_tunnel_xmit_skb()
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Carlier <[email protected]>
commit 5638504a2aa9e1b9d72af9060df1a160cce2d379 upstream.
gtp_genl_send_echo_req() runs as a generic netlink doit handler in process context with BH not disabled. It calls udp_tunnel_xmit_skb(), which eventually invokes iptunnel_xmit() — that uses __this_cpu_inc/dec on softnet_data.xmit.recursion to track the tunnel xmit recursion level.
Without local_bh_disable(), the task may migrate between dev_xmit_recursion_inc() and dev_xmit_recursion_dec(), breaking the per-CPU counter pairing. The result is stale or negative recursion levels that can later produce false-positive SKB_DROP_REASON_RECURSION_LIMIT drops on either CPU.
The other udp_tunnel_xmit_skb() call sites in gtp.c are unaffected:
the data path runs under ndo_start_xmit and the echo response handlers run from the UDP encap rx softirq, both with BH already disabled.
Fix it by disabling BH around the udp_tunnel_xmit_skb() call, mirroring commit 2cd7e6971fc2 ("sctp: disable BH before calling udp_tunnel_xmit_skb()").
--- drivers/net/gtp.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/gtp.c +2 -0
@@ -2400,6 +2400,7 @@ static int gtp_genl_send_echo_req(structreturn -ENODEV ; } +local_bh_disable (); udp_tunnel_xmit_skb(rt, sk, skb_to_send, fl4.saddr, fl4.daddr, inet_dscp_to_dsfield(fl4.flowi4_dscp),
@@ -2409,6 +2410,7 @@ static int gtp_genl_send_echo_req(struct !net_eq (sock_net (sk),dev_net (gtp->dev)), false, 0); +local_bh_enable ();return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 275/307 IB/core: Fix zero dmac race in neighbor resolution
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chen Zhao <[email protected]>
commit 5e6de34d82b49cab9d8a42063e9cd0f22a4f31e5 upstream.
dst_fetch_ha() checks nud_state without holding the neighbor lock, then copies ha under the seqlock. A race in __neigh_update() where nud_state is set to NUD_REACHABLE before ha is written allows dst_fetch_ha() to read a zero MAC address while the seqlock reports no concurrent writer.
netevent_callback amplifies this by waking ALL pending addr_req workers when ANY neighbor becomes NUD_VALID. At scale (N peers resolving ARP concurrently), the hit probability scales as N^2, making it near-certain for large RDMA workloads.
N(A): neigh_update(A) W(A): addr_resolve(A)
| [sleep] | write_lock_bh(&A->lock) | | A->nud_state = NUD_REACHABLE | | // A->ha is still 0 | | [woken by netevent_cb() of | another neighbour] | | dst_fetch_ha(A) | | A->nud_state & NUD_VALID | | read_seqbegin(&A->ha_lock) | | snapshot = A->ha /* 0 */ | | read_seqretry(&A->ha_lock) | | return snapshot | seqlock(&A->ha_lock) | A->ha = mac_A /* too late */ | sequnlock(&A->ha_lock) | write_unlock_bh(&A->lock)
The incorrect/zero mac is read and programmed in the device QP while it was not yet updated. This causes silent packet loss and eventual RETRY_EXC_ERR.
Fix by holding the neighbor read lock across the nud_state check and ha copy in dst_fetch_ha(), ensuring it synchronizes with __neigh_update() which is updating while holding the write lock.
--- drivers/infiniband/core/addr.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/infiniband/core/addr.c +3 -0
@@ -321,11 +321,14 @@ static int dst_fetch_ha(const struct dstif (!n)return -ENODATA ; +read_lock_bh (&n->lock);if (!(n->nud_state &NUD_VALID )) { +read_unlock_bh (&n->lock);neigh_event_send (n,NULL ); ret = -ENODATA ; }else {neigh_ha_snapshot (dev_addr->dst_dev_addr, n, dst->dev); +read_unlock_bh (&n->lock); }neigh_release (n);
Greg Kroah-Hartman
maintainerPATCH 276/307 ktest: Fix the month in the name of the failure directory
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Steven Rostedt <[email protected]>
commit 768059ede35f197575a38b10797b52402d9d4d2f upstream.
The Perl localtime() function returns the month starting at 0 not 1. This caused the date produced to create the directory for saving files of a failed run to have the month off by one.
machine-test-useconfig-fail-20260314073628
The above happened in April, not March. The correct name should have been:
machine-test-useconfig-fail-20260414073628
This was somewhat confusing.
--- tools/testing/ktest/ktest.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/ktest/ktest.pl +1 -1
@@ -1815,7 +1815,7 @@ sub save_logs { my ($result, $basedir) = @_; my @t = localtime; my $date = sprintf "%04d%02d%02d%02d%02d%02d", - 1900+$t[5],$t[4],$t[3],$t[2],$t[1],$t[0]; + 1900+$t[5],$t[4]+1,$t[3],$t[2],$t[1],$t[0]; my $type = $build_type; if ($type =~ /useconfig/) {
Greg Kroah-Hartman
maintainerPATCH 277/307 NFSv4.1: Apply session size limits on clone path
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tushar Sariya <[email protected]>
commit 8c787b286f39c7584440b97b92f87cbe934c13ff upstream.
nfs4_clone_server() builds a child nfs_server for same-server automounted submounts but never calls nfs4_session_limit_rwsize() or nfs4_session_limit_xasize() after nfs_clone_server(). This means the child mount can end up with rsize/wsize values that exceed the negotiated session channel limits, causing NFS4ERR_REQ_TOO_BIG and EIO on servers that enforce tight max_request_size budgets.
Top-level mounts go through nfs4_server_common_setup() which calls these limiters after nfs_probe_server(). Apply the same clamping on the clone path for consistency.
--- fs/nfs/internal.h | 2 ++ fs/nfs/nfs4client.c | 4 ++-- fs/nfs/nfs4proc.c | 3 +++ 3 files changed, 7 insertions(+), 2 deletions(-)
fs/nfs/internal.h +2 -0
@@ -253,6 +253,8 @@ extern struct nfs_client *nfs4_set_ds_cl u32 minor_version);extern struct rpc_clnt *nfs4_find_or_create_ds_client (struct nfs_client *,struct inode *); +extern void nfs4_session_limit_rwsize (struct nfs_server *server); +extern void nfs4_session_limit_xasize (struct nfs_server *server); extern struct nfs_client *nfs3_set_ds_client(struct nfs_server *mds_srv, const struct sockaddr_storage *ds_addr, int ds_addrlen, int ds_proto, unsigned int ds_timeo,
fs/nfs/nfs4client.c +2 -2
@@ -855,7 +855,7 @@ EXPORT_SYMBOL_GPL(nfs4_set_ds_client);* Limit the mount rsize, wsize and dtsize using negotiated fore * channel attributes. */ -static void nfs4_session_limit_rwsize (struct nfs_server *server) +void nfs4_session_limit_rwsize (struct nfs_server *server) {struct nfs4_session *sess;u32 server_resp_sz;
@@ -878,7 +878,7 @@ static void nfs4_session_limit_rwsize(st/* * Limit xattr sizes using the channel attributes. */ -static void nfs4_session_limit_xasize (struct nfs_server *server) +void nfs4_session_limit_xasize (struct nfs_server *server) {#ifdef CONFIG_NFS_V4_2 struct nfs4_session *sess;
fs/nfs/nfs4proc.c +3 -0
@@ -10618,6 +10618,9 @@ static struct nfs_server *nfs4_clone_serif (IS_ERR (server))return server; +nfs4_session_limit_rwsize (server); +nfs4_session_limit_xasize (server); + error =nfs4_delegation_hash_alloc (server);if (error) {nfs_free_server (server);
Greg Kroah-Hartman
maintainerPATCH 278/307 ntfs3: add buffer boundary checks to run_unpack()
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tobias Gaertner <[email protected]>
commit b62567bca47408e6739dee75f02a2113548af875 upstream.
run_unpack() checks run_buf < run_last at the top of the while loop but then reads size_size and offset_size bytes via run_unpack_s64() without verifying they fit within the remaining buffer. A crafted NTFS image with truncated run data in an MFT attribute triggers an OOB heap read of up to 15 bytes when the filesystem is mounted.
Add boundary checks before each run_unpack_s64() call to ensure the declared field size does not exceed the remaining buffer.
Found by fuzzing with a source-patched harness (LibAFL + QEMU).
--- fs/ntfs3/run.c | 6 ++++++ 1 file changed, 6 insertions(+)
fs/ntfs3/run.c +6 -0
@@ -1008,6 +1008,9 @@ int run_unpack(struct runs_tree *run, stif (size_size >sizeof (len))return -EINVAL ; +if (run_buf + size_size > run_last) +return -EINVAL ; + len =run_unpack_s64 (run_buf, size_size,0 );/* Skip size_size. */ run_buf += size_size;
@@ -1020,6 +1023,9 @@ int run_unpack(struct runs_tree *run, stelse if (offset_size <=sizeof (s64)) {s64 dlcn; +if (run_buf + offset_size > run_last) +return -EINVAL ; +/* Initial value of dlcn is -1 or 0. */ dlcn = (run_buf[offset_size -1 ] &0x80 ) ? (s64)-1 :0 ; dlcn =run_unpack_s64 (run_buf, offset_size, dlcn);
Greg Kroah-Hartman
maintainerPATCH 279/307 ntfs3: fix integer overflow in run_unpack() volume boundary check
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tobias Gaertner <[email protected]>
commit 984a415f019536ea2d24de9010744e5302a9a948 upstream.
The volume boundary check lcn + len > sbi->used.bitmap.nbits uses raw addition which can wrap around for large lcn and len values, bypassing the validation. Use check_add_overflow() as is already done for the adjacent prev_lcn + dlcn and vcn64 + len checks added by commit 3ac37e100385 ("ntfs3: Fix integer overflow in run_unpack()").
Found by fuzzing with a source-patched harness (LibAFL + QEMU).
--- fs/ntfs3/run.c | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
fs/ntfs3/run.c +9 -3
@@ -1065,9 +1065,15 @@ int run_unpack(struct runs_tree *run, st return -EOPNOTSUPP; }#endif -if (lcn !=SPARSE_LCN64 && lcn + len > sbi->used.bitmap.nbits) { -/* LCN range is out of volume. */ -return -EINVAL ; +if (lcn !=SPARSE_LCN64 ) { +u64 lcn_end; + +if (check_add_overflow (lcn, len, &lcn_end)) +return -EINVAL ; +if (lcn_end > sbi->used.bitmap.nbits) { +/* LCN range is out of volume. */ +return -EINVAL ; + } }if (!run)
Greg Kroah-Hartman
maintainerPATCH 280/307 rtmutex: Use waiter::task instead of current in remove_waiter()
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Keenan Dong <[email protected]>
commit 3bfdc63936dd4773109b7b8c280c0f3b5ae7d349 upstream.
remove_waiter() is used by the slowlock paths, but it is also used for proxy-lock rollback in rt_mutex_start_proxy_lock() when invoked from futex_requeue().
In the latter case waiter::task is not current, but remove_waiter() operates on current for the dequeue operation. That results in several problems:
1) the rbtree dequeue happens without waiter::task::pi_lock being held
2) the waiter task's pi_blocked_on state is not cleared, which leaves a dangling pointer primed for UAF around.
3) rt_mutex_adjust_prio_chain() operates on the wrong top priority waiter task
Use waiter::task instead of current in all related operations in remove_waiter() to cure those problems.
[ tglx: Fixup rt_mutex_adjust_prio_chain(), add a comment and amend the
changelog ]
--- kernel/locking/rtmutex.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-)
kernel/locking/rtmutex.c +8 -5
@@ -1535,20 +1535,23 @@ static bool rtmutex_spin_on_owner(struct* * Must be called with lock->wait_lock held and interrupts disabled. It must * have just failed to try_to_take_rt_mutex(). +* +* When invoked from rt_mutex_start_proxy_lock() waiter::task != current ! */ static void __sched remove_waiter(struct rt_mutex_base *lock,struct rt_mutex_waiter *waiter) {bool is_top_waiter = (waiter ==rt_mutex_top_waiter (lock));struct task_struct *owner =rt_mutex_owner (lock); +struct task_struct *waiter_task = waiter->task;struct rt_mutex_base *next_lock;lockdep_assert_held (&lock->wait_lock); -raw_spin_lock (¤t->pi_lock); -rt_mutex_dequeue (lock, waiter); - current->pi_blocked_on =NULL ; -raw_spin_unlock (¤t->pi_lock); + scoped_guard(raw_spinlock, &waiter_task->pi_lock) { +rt_mutex_dequeue (lock, waiter); + waiter_task->pi_blocked_on =NULL ; + }/* * Only update priority if the waiter was the highest priority
@@ -1584,7 +1587,7 @@ static void __sched remove_waiter(structraw_spin_unlock_irq (&lock->wait_lock);rt_mutex_adjust_prio_chain (owner,RT_MUTEX_MIN_CHAINWALK , lock, - next_lock,NULL , current); + next_lock,NULL , waiter_task);raw_spin_lock_irq (&lock->wait_lock); }
Greg Kroah-Hartman
maintainerPATCH 281/307 rxgk: Fix potential integer overflow in length check
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Howells <[email protected]>
commit 6929350080f4da292d111a3b33e53138fee51cec upstream.
Fix potential integer overflow in rxgk_extract_token() when checking the length of the ticket. Rather than rounding up the value to be tested (which might overflow), round down the size of the available data.
--- net/rxrpc/rxgk_app.c | 2 +- net/rxrpc/rxgk_common.h | 1 + 2 files changed, 2 insertions(+), 1 deletion(-)
net/rxrpc/rxgk_app.c +1 -1
@@ -214,7 +214,7 @@ int rxgk_extract_token(struct rxrpc_conn ticket_len =ntohl (container.token_len); ticket_offset = token_offset +sizeof (container); -if (xdr_round_up (ticket_len) > token_len -sizeof (container)) +if (ticket_len >xdr_round_down (token_len -sizeof (container))) goto short_packet;_debug ("KVNO %u" , kvno);
net/rxrpc/rxgk_common.h +1 -0
@@ -34,6 +34,7 @@ struct rxgk_context { };#define xdr_round_up (x) (round_up((x), sizeof(__be32))) +#define xdr_round_down (x) (round_down((x), sizeof(__be32)))#define xdr_object_len (x) (4 + xdr_round_up(x))/*
Greg Kroah-Hartman
maintainerPATCH 282/307 sched_ext: Documentation: Clarify ops.dispatch() role in task lifecycle
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andrea Righi <[email protected]>
commit a313357a346839d40b3a4dec393c71bf30cbb34c upstream.
ops.dispatch() is invoked when a CPU becomes available. This can occur when a task voluntarily yields the CPU, exhausts its time slice, or is preempted for other reasons.
If the task is still runnable, refilling its time slice in ops.dispatch() (either by the BPF scheduler or the sched_ext core) allows it to continue running without triggering ops.stopping(). However, this behavior is not clearly reflected in the current task lifecycle diagram.
Update the diagram to better represent this interaction.
--- Documentation/scheduler/sched-ext.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-)
Documentation/scheduler/sched-ext.rst +7 -5
@@ -320,13 +320,15 @@ by a sched_ext scheduler: ops.dispatch(); /* Task is moved to a local DSQ */ } ops.running(); /* Task starts running on its assigned CPU */ - while (task->scx.slice > 0 && task is runnable) - ops.tick(); /* Called every 1/HZ seconds */ - ops.stopping(); /* Task stops running (time slice expires or wait) */ - /* Task's CPU becomes available */ + while task_is_runnable(p) { + while (task->scx.slice > 0 && task_is_runnable(p)) + ops.tick(); /* Called every 1/HZ seconds */ + + ops.dispatch(); /* task->scx.slice can be refilled */ + } - ops.dispatch(); /* task->scx.slice can be refilled */ + ops.stopping(); /* Task stops running (time slice expires or wait) */ } ops.quiescent(); /* Task releases its assigned CPU (wait) */
Greg Kroah-Hartman
maintainerPATCH 283/307 scsi: sd: fix missing put_disk() when device_add(&disk_dev) fails
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yang Xiuwei <[email protected]>
commit 1e111c4b3a726df1254670a5cc4868cedb946d37 upstream.
If device_add(&sdkp->disk_dev) fails, put_device() runs scsi_disk_release(), which frees the scsi_disk but leaves the gendisk referenced. The device_add_disk() error path in sd_probe() calls put_disk(gd); call put_disk(gd) here to mirror that cleanup.
--- drivers/scsi/sd.c | 1 + 1 file changed, 1 insertion(+)
drivers/scsi/sd.c +1 -0
@@ -4018,6 +4018,7 @@ static int sd_probe(struct scsi_device * error =device_add (&sdkp->disk_dev);if (error) {put_device (&sdkp->disk_dev); +put_disk (gd); goto out; }
Greg Kroah-Hartman
maintainerPATCH 284/307 seg6: fix seg6 lwtunnel output redirect for L2 reduced encap mode
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andrea Mayer <[email protected]>
commit ade67d5f588832c7ba131aadd4215a94ce0a15c8 upstream.
When SEG6_IPTUN_MODE_L2ENCAP_RED (L2ENCAP_RED) was introduced, the condition in seg6_build_state() that excludes L2 encap modes from setting LWTUNNEL_STATE_OUTPUT_REDIRECT was not updated to account for the new mode.
As a consequence, L2ENCAP_RED routes incorrectly trigger seg6_output() on the output path, where the packet is silently dropped because skb_mac_header_was_set() fails on L3 packets.
Extend the check to also exclude L2ENCAP_RED, consistent with L2ENCAP.
--- net/ipv6/seg6_iptunnel.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/ipv6/seg6_iptunnel.c +2 -1
@@ -715,7 +715,8 @@ static int seg6_build_state(struct net * newts->type =LWTUNNEL_ENCAP_SEG6 ; newts->flags |=LWTUNNEL_STATE_INPUT_REDIRECT ; -if (tuninfo->mode !=SEG6_IPTUN_MODE_L2ENCAP ) +if (tuninfo->mode !=SEG6_IPTUN_MODE_L2ENCAP && + tuninfo->mode !=SEG6_IPTUN_MODE_L2ENCAP_RED ) newts->flags |=LWTUNNEL_STATE_OUTPUT_REDIRECT ; newts->headroom =seg6_lwt_headroom (tuninfo);
Greg Kroah-Hartman
maintainerPATCH 285/307 perf loongarch: Fix build failure with CONFIG_LIBDW_DWARF_UNWIND
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: WANG Rui <[email protected]>
commit 841dbf4871c57ce2da18c4ea7ffac5487d0eda16 upstream.
Building perf for LoongArch fails when CONFIG_LIBDW_DWARF_UNWIND is enabled because unwind-libdw.o is still referenced in arch/loongarch/util/Build.
--- tools/perf/arch/loongarch/util/Build | 1 - 1 file changed, 1 deletion(-)
tools/perf/arch/loongarch/util/Build +0 -1
@@ -1,4 +1,3 @@ perf-util-y += header.o perf-util-$(CONFIG_LOCAL_LIBUNWIND) += unwind-libunwind.o -perf-util-$(CONFIG_LIBDW_DWARF_UNWIND) += unwind-libdw.o
Greg Kroah-Hartman
maintainerPATCH 286/307 iio: frequency: admv1013: add dev variable
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Antoniu Miclaus <[email protected]>
[ Upstream commit e61b5bb0e91390adee41eaddc0a1a7d55d5652b2 ]
Introduce a local struct device pointer in functions that reference &spi->dev for device-managed resource calls and device property reads, improving code readability.
Stable-dep-of: aac0a51b1670 ("iio: frequency: admv1013: fix NULL pointer dereference on str")
--- drivers/iio/frequency/admv1013.c | 29 +++++++++++++++-------------- 1 file changed, 15 insertions(+), 14 deletions(-)
drivers/iio/frequency/admv1013.c +15 -14
@@ -518,11 +518,11 @@ static int admv1013_properties_parse(str {int ret;const char *str; -struct spi_device *spi = st->spi; +struct device *dev = &st->spi->dev; - st->det_en =device_property_read_bool (&spi->dev,"adi,detector-enable" ); + st->det_en =device_property_read_bool (dev,"adi,detector-enable" ); - ret =device_property_read_string (&spi->dev,"adi,input-mode" , &str); + ret =device_property_read_string (dev,"adi,input-mode" , &str);if (ret) st->input_mode =ADMV1013_IQ_MODE ;
@@ -533,7 +533,7 @@ static int admv1013_properties_parse(strelse return -EINVAL ; - ret =device_property_read_string (&spi->dev,"adi,quad-se-mode" , &str); + ret =device_property_read_string (dev,"adi,quad-se-mode" , &str);if (ret) st->quad_se_mode =ADMV1013_SE_MODE_DIFF ;
@@ -546,11 +546,11 @@ static int admv1013_properties_parse(strelse return -EINVAL ; - ret =devm_regulator_bulk_get_enable (&st->spi->dev, + ret =devm_regulator_bulk_get_enable (dev,ARRAY_SIZE (admv1013_vcc_regs), admv1013_vcc_regs);if (ret) { -dev_err_probe (&spi->dev, ret, +dev_err_probe (dev, ret,"Failed to request VCC regulators\n" );return ret; }
@@ -562,9 +562,10 @@ static int admv1013_probe(struct spi_dev {struct iio_dev *indio_dev;struct admv1013_state *st; +struct device *dev = &spi->dev;int ret, vcm_uv; - indio_dev =devm_iio_device_alloc (&spi->dev,sizeof (*st)); + indio_dev =devm_iio_device_alloc (dev,sizeof (*st));if (!indio_dev)return -ENOMEM ;
@@ -581,20 +582,20 @@ static int admv1013_probe(struct spi_devif (ret)return ret; - ret =devm_regulator_get_enable_read_voltage (&spi->dev,"vcm" ); + ret =devm_regulator_get_enable_read_voltage (dev,"vcm" );if (ret <0 ) -return dev_err_probe (&spi->dev, ret, +return dev_err_probe (dev, ret,"failed to get the common-mode voltage\n" ); vcm_uv = ret; - st->clkin =devm_clk_get_enabled (&spi->dev,"lo_in" ); + st->clkin =devm_clk_get_enabled (dev,"lo_in" );if (IS_ERR (st->clkin)) -return dev_err_probe (&spi->dev,PTR_ERR (st->clkin), +return dev_err_probe (dev,PTR_ERR (st->clkin),"failed to get the LO input clock\n" ); st->nb.notifier_call = admv1013_freq_change; - ret =devm_clk_notifier_register (&spi->dev, st->clkin, &st->nb); + ret =devm_clk_notifier_register (dev, st->clkin, &st->nb);if (ret)return ret;
@@ -606,11 +607,11 @@ static int admv1013_probe(struct spi_devreturn ret; } - ret =devm_add_action_or_reset (&spi->dev, admv1013_powerdown, st); + ret =devm_add_action_or_reset (dev, admv1013_powerdown, st);if (ret)return ret; -return devm_iio_device_register (&spi->dev, indio_dev); +return devm_iio_device_register (dev, indio_dev); }static const struct spi_device_id admv1013_id[] = {
Greg Kroah-Hartman
maintainerPATCH 287/307 iio: frequency: admv1013: fix NULL pointer dereference on str
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Antoniu Miclaus <[email protected]>
[ Upstream commit aac0a51b16700b403a55b67ba495de021db78763 ]
When device_property_read_string() fails, str is left uninitialized but the code falls through to strcmp(str, ...), dereferencing a garbage pointer. Replace manual read/strcmp with device_property_match_property_string() and consolidate the SE mode enums into a single sequential enum, mapping to hardware register values via a switch consistent with other bitfields in the driver.
Several cleanup patches have been applied to this driver recently so this will need a manual backport.
--- drivers/iio/frequency/admv1013.c | 67 ++++++++++++++++++++++----------------- 1 file changed, 38 insertions(+), 29 deletions(-)
drivers/iio/frequency/admv1013.c +38 -29
@@ -85,9 +85,9 @@ enum { };enum { -ADMV1013_SE_MODE_POS =6 , -ADMV1013_SE_MODE_NEG =9 , -ADMV1013_SE_MODE_DIFF =12 +ADMV1013_SE_MODE_POS , +ADMV1013_SE_MODE_NEG , +ADMV1013_SE_MODE_DIFF , };struct admv1013_state {
@@ -470,10 +470,23 @@ static int admv1013_init(struct admv1013if (ret)return ret; - data =FIELD_PREP (ADMV1013_QUAD_SE_MODE_MSK , st->quad_se_mode); +switch (st->quad_se_mode) { +case ADMV1013_SE_MODE_POS : + data =6 ; +break ; +case ADMV1013_SE_MODE_NEG : + data =9 ; +break ; +case ADMV1013_SE_MODE_DIFF : + data =12 ; +break ; +default : +return -EINVAL ; + } ret =__admv1013_spi_update_bits (st,ADMV1013_REG_QUAD , -ADMV1013_QUAD_SE_MODE_MSK , data); +ADMV1013_QUAD_SE_MODE_MSK , +FIELD_PREP (ADMV1013_QUAD_SE_MODE_MSK , data));if (ret)return ret;
@@ -514,37 +527,33 @@ static void admv1013_powerdown(void *datadmv1013_spi_update_bits (data,ADMV1013_REG_ENABLE , enable_reg_msk, enable_reg); } +static const char *const admv1013_input_modes[] = { + [ADMV1013_IQ_MODE ] ="iq" , + [ADMV1013_IF_MODE ] ="if" , +}; + +static const char *const admv1013_quad_se_modes[] = { + [ADMV1013_SE_MODE_POS ] ="se-pos" , + [ADMV1013_SE_MODE_NEG ] ="se-neg" , + [ADMV1013_SE_MODE_DIFF ] ="diff" , +}; +static int admv1013_properties_parse (struct admv1013_state *st) {int ret; -const char *str;struct device *dev = &st->spi->dev; st->det_en =device_property_read_bool (dev,"adi,detector-enable" ); - ret =device_property_read_string (dev,"adi,input-mode" , &str); -if (ret) - st->input_mode =ADMV1013_IQ_MODE ; - -if (!strcmp (str,"iq" )) - st->input_mode =ADMV1013_IQ_MODE ; -else if (!strcmp (str,"if" )) - st->input_mode =ADMV1013_IF_MODE ; -else -return -EINVAL ; - - ret =device_property_read_string (dev,"adi,quad-se-mode" , &str); -if (ret) - st->quad_se_mode =ADMV1013_SE_MODE_DIFF ; - -if (!strcmp (str,"diff" )) - st->quad_se_mode =ADMV1013_SE_MODE_DIFF ; -else if (!strcmp (str,"se-pos" )) - st->quad_se_mode =ADMV1013_SE_MODE_POS ; -else if (!strcmp (str,"se-neg" )) - st->quad_se_mode =ADMV1013_SE_MODE_NEG ; -else -return -EINVAL ; + ret =device_property_match_property_string (dev,"adi,input-mode" , + admv1013_input_modes, +ARRAY_SIZE (admv1013_input_modes)); + st->input_mode = ret >=0 ? ret :ADMV1013_IQ_MODE ; + + ret =device_property_match_property_string (dev,"adi,quad-se-mode" , + admv1013_quad_se_modes, +ARRAY_SIZE (admv1013_quad_se_modes)); + st->quad_se_mode = ret >=0 ? ret :ADMV1013_SE_MODE_DIFF ; ret = devm_regulator_bulk_get_enable(dev, ARRAY_SIZE(admv1013_vcc_regs),
Greg Kroah-Hartman
maintainerPATCH 288/307 wifi: mt76: mt792x: describe USB WFSYS reset with a descriptor
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Wang <[email protected]>
[ Upstream commit e6f48512c1ceebcd1ce6bb83df3b3d56a261507d ]
Prepare mt792xu_wfsys_reset() for chips that share the same USB WFSYS reset flow but use different register definitions.
This is a pure refactor of the current mt7921u path and keeps the reset sequence unchanged.
Stable-dep-of: 56154fef47d1 ("wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling")
--- drivers/net/wireless/mediatek/mt76/mt792x_usb.c | 40 +++++++++++++++++++----- 1 file changed, 32 insertions(+), 8 deletions(-)
drivers/net/wireless/mediatek/mt76/mt792x_usb.c +32 -8
@@ -206,6 +206,24 @@ static void mt792xu_epctl_rst_opt(structmt792xu_uhw_wr (&dev->mt76,MT_SSUSB_EPCTL_CSR_EP_RST_OPT , val); } +struct mt792xu_wfsys_desc { +u32 rst_reg; +u32 done_reg; +u32 done_mask; +u32 done_val; +u32 delay_ms; +bool need_status_sel; +}; + +static const struct mt792xu_wfsys_desc mt7921_wfsys_desc = { + .rst_reg =MT_CBTOP_RGU_WF_SUBSYS_RST , + .done_reg =MT_UDMA_CONN_INFRA_STATUS , + .done_mask =MT_UDMA_CONN_WFSYS_INIT_DONE , + .done_val =MT_UDMA_CONN_WFSYS_INIT_DONE , + .delay_ms =0 , + .need_status_sel = true, +}; +int mt792xu_dma_init (struct mt792x_dev *dev,bool resume) {int err;
@@ -236,25 +254,31 @@ EXPORT_SYMBOL_GPL(mt792xu_dma_init);int mt792xu_wfsys_reset (struct mt792x_dev *dev) { +const struct mt792xu_wfsys_desc *desc = &mt7921_wfsys_desc;u32 val;int i;mt792xu_epctl_rst_opt (dev, false); - val =mt792xu_uhw_rr (&dev->mt76,MT_CBTOP_RGU_WF_SUBSYS_RST ); + val =mt792xu_uhw_rr (&dev->mt76, desc->rst_reg); val |=MT_CBTOP_RGU_WF_SUBSYS_RST_WF_WHOLE_PATH ; -mt792xu_uhw_wr (&dev->mt76,MT_CBTOP_RGU_WF_SUBSYS_RST , val); +mt792xu_uhw_wr (&dev->mt76, desc->rst_reg, val); -usleep_range (10 ,20 ); +if (desc->delay_ms) +msleep (desc->delay_ms); +else +usleep_range (10 ,20 ); - val =mt792xu_uhw_rr (&dev->mt76,MT_CBTOP_RGU_WF_SUBSYS_RST ); + val =mt792xu_uhw_rr (&dev->mt76, desc->rst_reg); val &= ~MT_CBTOP_RGU_WF_SUBSYS_RST_WF_WHOLE_PATH ; -mt792xu_uhw_wr (&dev->mt76,MT_CBTOP_RGU_WF_SUBSYS_RST , val); +mt792xu_uhw_wr (&dev->mt76, desc->rst_reg, val); + +if (desc->need_status_sel) +mt792xu_uhw_wr (&dev->mt76,MT_UDMA_CONN_INFRA_STATUS_SEL ,0 ); -mt792xu_uhw_wr (&dev->mt76,MT_UDMA_CONN_INFRA_STATUS_SEL ,0 );for (i =0 ; i < MT792x_WFSYS_INIT_RETRY_COUNT; i++) { - val =mt792xu_uhw_rr (&dev->mt76,MT_UDMA_CONN_INFRA_STATUS ); -if (val &MT_UDMA_CONN_WFSYS_INIT_DONE ) + val =mt792xu_uhw_rr (&dev->mt76, desc->done_reg); +if ((val & desc->done_mask) == desc->done_val)break ;msleep (100 );
Greg Kroah-Hartman
maintainerPATCH 289/307 wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Wang <[email protected]>
[ Upstream commit 56154fef47d104effa9f29ed3db4f805cbc0d640 ]
mt7925u uses different reset/status registers from mt7921u. Reusing the mt7921u register set causes the WFSYS reset to fail.
Add a chip-specific descriptor in mt792xu_wfsys_reset() to select the correct registers and fix mt7925u failing to initialize after a warm reboot.
--- drivers/net/wireless/mediatek/mt76/mt792x_regs.h | 4 ++++ drivers/net/wireless/mediatek/mt76/mt792x_usb.c | 13 ++++++++++++- 2 files changed, 16 insertions(+), 1 deletion(-)
drivers/net/wireless/mediatek/mt76/mt792x_regs.h +4 -0
@@ -390,6 +390,10 @@#define MT_CBTOP_RGU_WF_SUBSYS_RST MT_CBTOP_RGU(0x600)#define MT_CBTOP_RGU_WF_SUBSYS_RST_WF_WHOLE_PATH BIT(0) +#define MT7925_CBTOP_RGU_WF_SUBSYS_RST 0x70028600 +#define MT7925_WFSYS_INIT_DONE_ADDR 0x184c1604 +#define MT7925_WFSYS_INIT_DONE 0x00001d1e +#define MT_HW_BOUND 0x70010020#define MT_HW_CHIPID 0x70010200#define MT_HW_REV 0x70010204
drivers/net/wireless/mediatek/mt76/mt792x_usb.c +12 -1
@@ -224,6 +224,15 @@ static const struct mt792xu_wfsys_desc m .need_status_sel = true, }; +static const struct mt792xu_wfsys_desc mt7925_wfsys_desc = { + .rst_reg =MT7925_CBTOP_RGU_WF_SUBSYS_RST , + .done_reg =MT7925_WFSYS_INIT_DONE_ADDR , + .done_mask =U32_MAX , + .done_val =MT7925_WFSYS_INIT_DONE , + .delay_ms =20 , + .need_status_sel = false, +}; +int mt792xu_dma_init (struct mt792x_dev *dev,bool resume) {int err;
@@ -254,7 +263,9 @@ EXPORT_SYMBOL_GPL(mt792xu_dma_init);int mt792xu_wfsys_reset (struct mt792x_dev *dev) { -const struct mt792xu_wfsys_desc *desc = &mt7921_wfsys_desc; +const struct mt792xu_wfsys_desc *desc =is_mt7925 (&dev->mt76) ? + &mt7925_wfsys_desc : + &mt7921_wfsys_desc;u32 val;int i;
Greg Kroah-Hartman
maintainerPATCH 290/307 mm: various small mmap_prepare cleanups
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Lorenzo Stoakes (Oracle)" <[email protected]>
[ Upstream commit 3e4bb2706817710d9461394da8b75be79981586b ]
Patch series "mm: expand mmap_prepare functionality and usage", v4.
This series expands the mmap_prepare functionality, which is intended to replace the deprecated f_op->mmap hook which has been the source of bugs and security issues for some time.
This series starts with some cleanup of existing mmap_prepare logic, then adds documentation for the mmap_prepare call to make it easier for filesystem and driver writers to understand how it works.
It then importantly adds a vm_ops->mapped hook, a key feature that was missing from mmap_prepare previously - this is invoked when a driver which specifies mmap_prepare has successfully been mapped but not merged with another VMA.
mmap_prepare is invoked prior to a merge being attempted, so you cannot manipulate state such as reference counts as if it were a new mapping.
The vm_ops->mapped hook allows a driver to perform tasks required at this stage, and provides symmetry against subsequent vm_ops->open,close calls.
The series uses this to correct the afs implementation which wrongly manipulated reference count at mmap_prepare time.
It then adds an mmap_prepare equivalent of vm_iomap_memory() - mmap_action_simple_ioremap(), then uses this to update a number of drivers.
It then splits out the mmap_prepare compatibility layer (which allows for invocation of mmap_prepare hooks in an mmap() hook) in such a way as to allow for more incremental implementation of mmap_prepare hooks.
It then uses this to extend mmap_prepare usage in drivers.
Finally it adds an mmap_prepare equivalent of vm_map_pages(), which lays the foundation for future work which will extend mmap_prepare to DMA coherent mappings.
This patch (of 21):
Rather than passing arbitrary fields, pass a vm_area_desc pointer to mmap prepare functions to mmap prepare, and an action and vma pointer to mmap complete in order to put all the action-specific logic in the function actually doing the work.
Additionally, allow mmap prepare functions to return an error so we can error out as soon as possible if there is something logically incorrect in the input.
Update remap_pfn_range_prepare() to properly check the input range for the CoW case.
Also remove io_remap_pfn_range_complete(), as we can simply set up the fields correctly in io_remap_pfn_range_prepare() and use remap_pfn_range_complete() for this.
While we're here, make remap_pfn_range_prepare_vma() a little neater, and pass mmap_action directly to call_action_complete().
Then, update compat_vma_mmap() to perform its logic directly, as __compat_vma_map() is not used by anything so we don't need to export it.
Also update compat_vma_mmap() to use vfs_mmap_prepare() rather than calling the mmap_prepare op directly.
Finally, update the VMA userland tests to reflect the changes.
Stable-dep-of: f96e1d5f15b7 ("mm: avoid deadlock when holding rmap on mmap_prepare error")
--- include/linux/fs.h | 2 include/linux/mm.h | 7 -- mm/internal.h | 34 +++++----- mm/memory.c | 45 +++++++++----- mm/util.c | 121 ++++++++++++++++---------------------- mm/vma.c | 24 ++++--- tools/testing/vma/include/dup.h | 7 +- tools/testing/vma/include/stubs.h | 8 +- 8 files changed, 127 insertions(+), 121 deletions(-)
include/linux/fs.h +0 -2
@@ -2058,8 +2058,6 @@ static inline bool can_mmap_file(structreturn true; } -int __compat_vma_mmap (const struct file_operations *f_op, -struct file *file,struct vm_area_struct *vma);int compat_vma_mmap (struct file *file,struct vm_area_struct *vma);static inline int vfs_mmap (struct file *file,struct vm_area_struct *vma)
include/linux/mm.h +3 -4
@@ -4078,10 +4078,9 @@ static inline void mmap_action_ioremap_fmmap_action_ioremap (desc, desc->start, start_pfn,vma_desc_size (desc)); } -void mmap_action_prepare (struct mmap_action *action, -struct vm_area_desc *desc); -int mmap_action_complete (struct mmap_action *action, -struct vm_area_struct *vma); +int mmap_action_prepare (struct vm_area_desc *desc); +int mmap_action_complete (struct vm_area_struct *vma, +struct mmap_action *action);/* Look up the first VMA which exactly match the interval vm_start ... vm_end */ static inline struct vm_area_struct *find_exact_vma(struct mm_struct *mm,
mm/internal.h +18 -16
@@ -1757,26 +1757,28 @@ int walk_page_range_debug(struct mm_struvoid dup_mm_exe_file (struct mm_struct *mm,struct mm_struct *oldmm);int dup_mmap (struct mm_struct *mm,struct mm_struct *oldmm); -void remap_pfn_range_prepare (struct vm_area_desc *desc,unsigned long pfn); -int remap_pfn_range_complete (struct vm_area_struct *vma,unsigned long addr, -unsigned long pfn,unsigned long size,pgprot_t pgprot); +int remap_pfn_range_prepare (struct vm_area_desc *desc); +int remap_pfn_range_complete (struct vm_area_struct *vma, +struct mmap_action *action); -static inline void io_remap_pfn_range_prepare (struct vm_area_desc *desc, -unsigned long orig_pfn,unsigned long size) +static inline int io_remap_pfn_range_prepare (struct vm_area_desc *desc) { +struct mmap_action *action = &desc->action; +const unsigned long orig_pfn = action->remap.start_pfn; +const pgprot_t orig_pgprot = action->remap.pgprot; +const unsigned long size = action->remap.size;const unsigned long pfn =io_remap_pfn_range_pfn (orig_pfn, size); +int err; -return remap_pfn_range_prepare (desc, pfn); -} - -static inline int io_remap_pfn_range_complete (struct vm_area_struct *vma, -unsigned long addr,unsigned long orig_pfn,unsigned long size, -pgprot_t orig_prot) -{ -const unsigned long pfn =io_remap_pfn_range_pfn (orig_pfn, size); -const pgprot_t prot =pgprot_decrypted (orig_prot); - -return remap_pfn_range_complete (vma, addr, pfn, size, prot); + action->remap.start_pfn = pfn; + action->remap.pgprot =pgprot_decrypted (orig_pgprot); + err =remap_pfn_range_prepare (desc); +if (err) +return err; + +/* Remap does the actual work. */ + action->type =MMAP_REMAP_PFN ; +return 0 ; }#endif /* __MM_INTERNAL_H */
mm/memory.c +29 -16
65 lines not on this page · raw message
mm/util.c +54 -67
192 lines not on this page · raw message
mm/vma.c +14 -10
@@ -2611,15 +2611,18 @@ static void __mmap_complete(struct mmap_vma_set_page_prot (vma); } -static void call_action_prepare (struct mmap_state *map, -struct vm_area_desc *desc) +static int call_action_prepare (struct mmap_state *map, +struct vm_area_desc *desc) { -struct mmap_action *action = &desc->action; +int err; -mmap_action_prepare (action, desc); + err =mmap_action_prepare (desc); +if (err) +return err; -if (action->hide_from_rmap_until_complete) +if (desc->action.hide_from_rmap_until_complete) map->hold_file_rmap_lock = true; +return 0 ; }/*
@@ -2643,7 +2646,9 @@ static int call_mmap_prepare(struct mmapif (err)return err; -call_action_prepare (map, desc); + err =call_action_prepare (map, desc); +if (err) +return err;/* Update fields permitted to be changed. */ map->pgoff = desc->pgoff;
@@ -2698,13 +2703,12 @@ static bool can_set_ksm_flags_early(stru }static int call_action_complete (struct mmap_state *map, -struct vm_area_desc *desc, +struct mmap_action *action,struct vm_area_struct *vma) { -struct mmap_action *action = &desc->action;int ret; - ret =mmap_action_complete (action, vma); + ret =mmap_action_complete (vma, action);/* If we held the file rmap we need to release it. */ if (map->hold_file_rmap_lock) {
@@ -2766,7 +2770,7 @@ static unsigned long __mmap_region(struc__mmap_complete (&map, vma);if (have_mmap_prepare && allocated_new) { - error =call_action_complete (&map, &desc, vma); + error =call_action_complete (&map, &desc.action, vma);if (error)return error;
tools/testing/vma/include/dup.h +5 -2
@@ -1093,9 +1093,12 @@ static inline int __compat_vma_mmap(consif (err)return err; -mmap_action_prepare (&desc.action, &desc); + err =mmap_action_prepare (&desc); +if (err) +return err; +set_vma_from_desc (vma, &desc); -return mmap_action_complete (&desc.action, vma); +return mmap_action_complete (vma, &desc.action); } static inline int compat_vma_mmap(struct file *file,
tools/testing/vma/include/stubs.h +4 -4
@@ -81,13 +81,13 @@ static inline void free_anon_vma_name(st { } -static inline void mmap_action_prepare (struct mmap_action *action, -struct vm_area_desc *desc) +static inline int mmap_action_prepare (struct vm_area_desc *desc) { +return 0 ; } -static inline int mmap_action_complete (struct mmap_action *action, -struct vm_area_struct *vma) +static inline int mmap_action_complete (struct vm_area_struct *vma, +struct mmap_action *action) {return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 291/307 mm: avoid deadlock when holding rmap on mmap_prepare error
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Lorenzo Stoakes (Oracle)" <[email protected]>
[ Upstream commit f96e1d5f15b7c854a6a9ec1225d68a12fe7dcda6 ]
Commit ac0a3fc9c07d ("mm: add ability to take further action in vm_area_desc") added the ability for drivers to instruct mm to take actions after the .mmap_prepare callback is complete.
To make life simpler and safer, this is done before the VMA/mmap write lock is dropped but when the VMA is completely established.
So on error, we simply munmap() the VMA.
As part of this implementation, unfortunately a horrible hack had to be implemented to support some questionable behaviour hugetlb relies upon - that is that the file rmap lock is held until the operation is complete.
The implementation, for convenience, did this in mmap_action_finish() so both the VMA and mmap_prepare compatibility layer paths would have this correctly handled.
However, it turns out there is a mistake here - the rmap lock cannot be held on munmap, as free_pgtables() -> unlink_file_vma_batch_add() -> unlink_file_vma_batch_process() takes the file rmap lock.
We therefore currently have a deadlock issue that might arise.
Resolve this by leaving it to callers to handle the unmap.
The compatibility layer does not support this rmap behaviour, so we simply have it unmap on error after calling mmap_action_complete().
In the VMA implementation, we only perform the unmap after the rmap lock is dropped.
This resolves the issue by ensuring the rmap lock is always dropped when the unmap occurs.
--- mm/util.c | 12 +++++++----- mm/vma.c | 13 ++++++++++--- 2 files changed, 17 insertions(+), 8 deletions(-)
mm/util.c +7 -5
@@ -1186,7 +1186,13 @@ int compat_vma_mmap(struct file *file, sreturn err;set_vma_from_desc (vma, &desc); -return mmap_action_complete (vma, &desc.action); + err =mmap_action_complete (vma, &desc.action); +if (err) { +const size_t len =vma_pages (vma) <<PAGE_SHIFT ; + +do_munmap (current->mm, vma->vm_start, len,NULL ); + } +return err; }EXPORT_SYMBOL (compat_vma_mmap);
@@ -1279,10 +1285,6 @@ static int mmap_action_finish(struct vm_* invoked if we do NOT merge, so we only clean up the VMA we created. */ if (err) { -const size_t len =vma_pages (vma) <<PAGE_SHIFT ; - -do_munmap (current->mm, vma->vm_start, len,NULL ); -if (action->error_hook) {/* We may want to filter the error. */ err = action->error_hook (err);
mm/vma.c +10 -3
@@ -2706,9 +2706,9 @@ static int call_action_complete(struct mstruct mmap_action *action, struct vm_area_struct *vma) { - int ret; + int err; - ret =mmap_action_complete (vma, action); + err =mmap_action_complete (vma, action);/* If we held the file rmap we need to release it. */ if (map->hold_file_rmap_lock) {
@@ -2716,7 +2716,14 @@ static int call_action_complete(struct mi_mmap_unlock_write (file->f_mapping); } -return ret; + +if (err) { +const size_t len =vma_pages (vma) <<PAGE_SHIFT ; + +do_munmap (current->mm, vma->vm_start, len,NULL ); + } + +return err; } static unsigned long __mmap_region(struct file *file, unsigned long addr,
Greg Kroah-Hartman
maintainerPATCH 292/307 mei: me: use PCI_DEVICE_DATA macro
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Usyskin <[email protected]>
[ Upstream commit 9e7a2409ecf4d411b7cc91615b08f6a7576f0aaa ]
Drop old local MEI_PCI_DEVICE macro and use common PCI_DEVICE_DATA instead.
Update defines to adhere to current naming convention.
Stable-dep-of: a5a1804332af ("mei: me: add nova lake point H DID")
--- drivers/misc/mei/bus-fixup.c | 6 - drivers/misc/mei/hw-me-regs.h | 162 +++++++++++++++++----------------- drivers/misc/mei/hw-me.h | 6 - drivers/misc/mei/pci-me.c | 200 +++++++++++++++++++++--------------------- 4 files changed, 184 insertions(+), 190 deletions(-)
drivers/misc/mei/bus-fixup.c +3 -3
@@ -303,9 +303,9 @@ static void mei_wd(struct mei_cl_device {struct pci_dev *pdev =to_pci_dev (cldev->dev.parent); -if (pdev->device ==MEI_DEV_ID_WPT_LP || - pdev->device ==MEI_DEV_ID_SPT || - pdev->device ==MEI_DEV_ID_SPT_H ) +if (pdev->device ==PCI_DEVICE_ID_INTEL_MEI_WPT_LP || + pdev->device ==PCI_DEVICE_ID_INTEL_MEI_SPT || + pdev->device ==PCI_DEVICE_ID_INTEL_MEI_SPT_H ) cldev->me_cl->props.protocol_version =0x2 ; cldev->do_match =1 ;
drivers/misc/mei/hw-me-regs.h +81 -81
201 lines not on this page · raw message
drivers/misc/mei/hw-me.h +0 -6
@@ -33,12 +33,6 @@ struct mei_cfg { u32 hw_trc_supported:1; }; - -#define MEI_PCI_DEVICE (dev, cfg) \ - .vendor = PCI_VENDOR_ID_INTEL, .device = (dev), \ - .subvendor = PCI_ANY_ID, .subdevice = PCI_ANY_ID, \ - .driver_data = (kernel_ulong_t)(cfg), -#define MEI_ME_RPM_TIMEOUT 500/* ms */ /**
drivers/misc/mei/pci-me.c +100 -100
210 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 293/307 mei: me: add nova lake point H DID
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Usyskin <[email protected]>
[ Upstream commit a5a1804332afc7035d5c5b880548262e81d796bc ]
Add Nova Lake H device id.
--- drivers/misc/mei/hw-me-regs.h | 1 + drivers/misc/mei/pci-me.c | 1 + 2 files changed, 2 insertions(+)
drivers/misc/mei/hw-me-regs.h +1 -0
@@ -123,6 +123,7 @@#define PCI_DEVICE_ID_INTEL_MEI_WCL_P 0x4D70/* Wildcat Lake P */ #define PCI_DEVICE_ID_INTEL_MEI_NVL_S 0x6E68/* Nova Lake Point S */ +#define PCI_DEVICE_ID_INTEL_MEI_NVL_H 0xD370/* Nova Lake Point H */ /* * MEI HW Section
drivers/misc/mei/pci-me.c +1 -0
@@ -130,6 +130,7 @@ static const struct pci_device_id mei_me {PCI_DEVICE_DATA(INTEL, MEI_WCL_P, MEI_ME_PCH15_CFG)}, {PCI_DEVICE_DATA(INTEL, MEI_NVL_S, MEI_ME_PCH15_CFG)}, + {PCI_DEVICE_DATA(INTEL, MEI_NVL_H, MEI_ME_PCH15_CFG)},/* required last entry */ {0, }
Greg Kroah-Hartman
maintainerPATCH 294/307 crypto: authencesn - reject short ahash digests during instance creation
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yucheng Lu <[email protected]>
commit 5db6ef9847717329f12c5ea8aba7e9f588a980c0 upstream.
authencesn requires either a zero authsize or an authsize of at least 4 bytes because the ESN encrypt/decrypt paths always move 4 bytes of high-order sequence number data at the end of the authenticated data.
While crypto_authenc_esn_setauthsize() already rejects explicit non-zero authsizes in the range 1..3, crypto_authenc_esn_create() still copied auth->digestsize into inst->alg.maxauthsize without validating it. The AEAD core then initialized the tfm's default authsize from that value.
As a result, selecting an ahash with digest size 1..3, such as cbcmac(cipher_null), exposed authencesn instances whose default authsize was invalid even though setauthsize() would have rejected the same value. AF_ALG could then trigger the ESN tail handling with a too-short tag and hit an out-of-bounds access.
Reject authencesn instances whose ahash digest size is in the invalid non-zero range 1..3 so that no tfm can inherit an unsupported default authsize.
--- crypto/authencesn.c | 5 +++++ 1 file changed, 5 insertions(+)
crypto/authencesn.c +5 -0
@@ -390,6 +390,11 @@ static int crypto_authenc_esn_create(str auth =crypto_spawn_ahash_alg (&ctx->auth); auth_base = &auth->base; +if (auth->digestsize >0 && auth->digestsize <4 ) { + err = -EINVAL ; + goto err_free_inst; + } + err =crypto_grab_skcipher (&ctx->enc,aead_crypto_instance (inst),crypto_attr_alg_name (tb[2 ]),0 , mask);if (err)
Greg Kroah-Hartman
maintainerPATCH 295/307 driver core: Add kernel-doc for DEV_FLAG_COUNT enum value
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Douglas Anderson <[email protected]>
commit 5b484311507b5d403c1f7a45f6aa3778549e268b upstream.
Even though nobody should use this value (except when declaring the "flags" bitmap), kernel-doc still gets upset that it's not documented. It reports:
WARNING: ../include/linux/device.h:519 Enum value 'DEV_FLAG_COUNT' not described in enum 'struct_device_flags'
Add the description of DEV_FLAG_COUNT.
--- include/linux/device.h | 1 + 1 file changed, 1 insertion(+)
include/linux/device.h +1 -0
@@ -466,6 +466,7 @@ struct device_physical_location {* * @DEV_FLAG_READY_TO_PROBE: If set then device_add() has finished enough * initialization that probe could be called. +* @DEV_FLAG_COUNT: Number of defined struct_device_flags. */ enum struct_device_flags {DEV_FLAG_READY_TO_PROBE =0 ,
Greg Kroah-Hartman
maintainerPATCH 296/307 ALSA: caiaq: Fix potentially leftover ep1_in_urb at error path
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit 0a7b5221b5b51cc798fcfc3be00d02eade149d69 upstream.
The previous fix for handling the error from setup_card() missed that an internal URB cdev->ep1_in_urb might have been already submitted beforehand. In the normal case, this URB gets killed at the disconnection, but in the error path, we didn't do it, hence there can be a potential leak.
Fix it in the error path for setup_card(), too.
--- sound/usb/caiaq/device.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/usb/caiaq/device.c +1 -1
@@ -514,7 +514,7 @@ static int init_card(struct snd_usb_caia card->private_free = card_free; err =setup_card (cdev);if (err <0 ) -return err; + goto err_kill_urb;return 0 ;
Greg Kroah-Hartman
maintainerPATCH 297/307 ALSA: caiaq: Dont abort when no input device is available
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit b32ae47a2b0a1fb4bd4942242847966d9b178222 upstream.
The previous fix to handle the error from setup_card() caused a regression for the models that have no dedicated input device; snd_usb_caiaq_input_init() just returns -EINVAL, and we treat it as a fatal error although it should be ignored.
As a regression fix, change the error code to -ENODEV, and ignore this error in the callee, to continue probing.
--- sound/usb/caiaq/device.c | 2 +- sound/usb/caiaq/input.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
sound/usb/caiaq/device.c +1 -1
@@ -366,7 +366,7 @@ static int setup_card(struct snd_usb_cai#ifdef CONFIG_SND_USB_CAIAQ_INPUT ret =snd_usb_caiaq_input_init (cdev); -if (ret <0 ) { +if (ret <0 && ret != -ENODEV ) {dev_err (dev,"Unable to set up input system (ret=%d)\n" , ret);return ret; }
sound/usb/caiaq/input.c +1 -1
@@ -804,7 +804,7 @@ int snd_usb_caiaq_input_init(struct snd_default :/* no input methods supported on this device */ - ret = -EINVAL ; + ret = -ENODEV ; goto exit_free_idev; }
Greg Kroah-Hartman
maintainerPATCH 298/307 ipv6: rpl: reserve mac_len headroom when recompressed SRH grows
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Greg Kroah-Hartman <[email protected]>
commit 9e6bf146b55999a095bb14f73a843942456d1adc upstream.
ipv6_rpl_srh_rcv() decompresses an RFC 6554 Source Routing Header, swaps the next segment into ipv6_hdr->daddr, recompresses, then pulls the old header and pushes the new one plus the IPv6 header back. The recompressed header can be larger than the received one when the swap reduces the common-prefix length the segments share with daddr (CmprI=0, CmprE>0, seg[0][0] != daddr[0] gives the maximum +8 bytes).
pskb_expand_head() was gated on segments_left == 0, so on earlier segments the push consumed unchecked headroom. Once skb_push() leaves fewer than skb->mac_len bytes in front of data, skb_mac_header_rebuild()'s call to:
skb_set_mac_header(skb, -skb->mac_len);
will store (data - head) - mac_len into the u16 mac_header field, which wraps to ~65530, and the following memmove() writes mac_len bytes ~64KiB past skb->head.
A single AF_INET6/SOCK_RAW/IPV6_HDRINCL packet over lo with a two segment type-3 SRH (CmprI=0, CmprE=15) reaches headroom 8 after one pass; KASAN reports a 14-byte OOB write in ipv6_rthdr_rcv.
Fix this by expanding the head whenever the remaining room is less than the push size plus mac_len, and request that much extra so the rebuilt MAC header fits afterwards.
--- net/ipv6/exthdrs.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
net/ipv6/exthdrs.c +6 -3
@@ -491,6 +491,7 @@ static int ipv6_rpl_srh_rcv(struct sk_bustruct net *net =dev_net (skb->dev);struct inet6_dev *idev;struct ipv6hdr *oldhdr; +unsigned int chdr_len;unsigned char *buf;int accept_rpl_seg;int i, err;
@@ -592,8 +593,10 @@ looped_back:skb_pull (skb, ((hdr->hdrlen +1 ) <<3 ));skb_postpull_rcsum (skb, oldhdr,sizeof (struct ipv6hdr ) + ((hdr->hdrlen +1 ) <<3 )); -if (unlikely (!hdr->segments_left)) { -if (pskb_expand_head (skb,sizeof (struct ipv6hdr ) + ((chdr->hdrlen +1 ) <<3 ),0 , + chdr_len =sizeof (struct ipv6hdr ) + ((chdr->hdrlen +1 ) <<3 ); +if (unlikely (!hdr->segments_left || +skb_headroom (skb) < chdr_len + skb->mac_len)) { +if (pskb_expand_head (skb, chdr_len + skb->mac_len,0 ,GFP_ATOMIC )) {__IP6_INC_STATS (net,ip6_dst_idev (skb_dst (skb)),IPSTATS_MIB_OUTDISCARDS );kfree_skb (skb);
@@ -603,7 +606,7 @@ looped_back: oldhdr =ipv6_hdr (skb); } -skb_push (skb, ((chdr->hdrlen +1 ) <<3 ) +sizeof (struct ipv6hdr )); +skb_push (skb, chdr_len);skb_reset_network_header (skb);skb_mac_header_rebuild (skb);skb_set_transport_header (skb,sizeof (struct ipv6hdr ));
Greg Kroah-Hartman
maintainerPATCH 299/307 drm/amdgpu: fix zero-size GDS range init on RDNA4
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Arjan van de Ven <[email protected]>
commit 095a8b0ad3c3b5cdc3850d961adb8a8f735220bb upstream.
RDNA4 (GFX 12) hardware removes the GDS, GWS, and OA on-chip memory resources. The gfx_v12_0 initialisation code correctly leaves adev->gds.gds_size, adev->gds.gws_size, and adev->gds.oa_size at zero to reflect this.
amdgpu_ttm_init() unconditionally calls amdgpu_ttm_init_on_chip() for each of these resources regardless of size. When the size is zero, amdgpu_ttm_init_on_chip() forwards the call to ttm_range_man_init(), which calls drm_mm_init(mm, 0, 0). drm_mm_init() immediately fires DRM_MM_BUG_ON(start + size <= start) -- trivially true when size is zero -- crashing the kernel during modprobe of amdgpu on an RX 9070 XT.
Guard against this by returning 0 early from amdgpu_ttm_init_on_chip() when size_in_page is zero. This skips TTM resource manager registration for hardware resources that are absent, without affecting any other GPU type.
DRM_MM_BUG_ON() only asserts if CONFIG_DRM_DEBUG_MM is enabled in the kernel config. This is apparently rarely enabled as these chips have been in the market for over a year and this issue was only reported now.
Oops-Analysis: http://oops.fenrus.org/reports/bugzilla.korg/221376/report.html
--- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c +3 -0
@@ -75,6 +75,9 @@ static int amdgpu_ttm_init_on_chip(struc unsigned int type, uint64_t size_in_page) { +if (!size_in_page) +return 0 ; +return ttm_range_man_init (&adev->mman.bdev, type, false, size_in_page); }
Greg Kroah-Hartman
maintainerPATCH 300/307 drm/imagination: Fix segfault when updating ftrace mask
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Brajesh Gupta <[email protected]>
commit 5dfd429591f8d7185bf63a08b5c30863fb605611 upstream.
Fix invalid data access by passing right data for debugfs entry.
[ 171.549793] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ 171.559248] Mem abort info: [ 171.562173] ESR = 0x0000000096000044 [ 171.566227] EC = 0x25: DABT (current EL), IL = 32 bits [ 171.573108] SET = 0, FnV = 0 [ 171.576448] EA = 0, S1PTW = 0 [ 171.579745] FSC = 0x04: level 0 translation fault [ 171.584760] Data abort info: [ 171.588012] ISV = 0, ISS = 0x00000044, ISS2 = 0x00000000 [ 171.593734] CM = 0, WnR = 1, TnD = 0, TagAccess = 0 [ 171.598962] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 171.604471] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000083837000 [ 171.611358] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 [ 171.618500] Internal error: Oops: 0000000096000044 [#1] SMP [ 171.624222] Modules linked in: powervr drm_shmem_helper drm_gpuvm... [ 171.656580] CPU: 0 UID: 0 PID: 549 Comm: bash Not tainted 7.0.0-rc2-g730b257ba723-dirty #13 PREEMPT [ 171.665773] Hardware name: BeagleBoard.org BeaglePlay (DT) [ 171.671296] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 171.678306] pc : pvr_fw_trace_mask_set+0x78/0x154 [powervr] [ 171.683959] lr : pvr_fw_trace_mask_set+0x4c/0x154 [powervr] [ 171.689593] sp : ffff8000835ebb90 [ 171.692929] x29: ffff8000835ebc00 x28: ffff000005c60f80 x27: 0000000000000000 [ 171.700130] x26: 0000000000000000 x25: ffff00000504af28 x24: 0000000000000000 [ 171.707324] x23: ffff00000504af50 x22: 0000000000000203 x21: 0000000000000000 [ 171.714518] x20: ffff000005c44a80 x19: ffff000005c457b8 x18: 0000000000000000 [ 171.721715] x17: 0000000000000000 x16: 0000000000000000 x15: 0000aaaae8887580 [ 171.728908] x14: 0000000000000000 x13: 0000000000000000 x12: ffff8000835ebc30 [ 171.736095] x11: ffff00000504af2a x10: ffff00008504af29 x9 : 0fffffffffffffff [ 171.743286] x8 : ffff8000835ebbf8 x7 : 0000000000000000 x6 : 000000000000002a [ 171.750479] x5 : ffff00000504af2e x4 : 0000000000000000 x3 : 0000000000000010 [ 171.757674] x2 : 0000000000000203 x1 : 0000000000000000 x0 : ffff8000835ebba0 [ 171.764871] Call trace: [ 171.767342] pvr_fw_trace_mask_set+0x78/0x154 [powervr] (P) [ 171.772984] simple_attr_write_xsigned.isra.0+0xe0/0x19c [ 171.778341] simple_attr_write+0x18/0x24 [ 171.782296] debugfs_attr_write+0x50/0x98 [ 171.786341] full_proxy_write+0x6c/0xa8 [ 171.790208] vfs_write+0xd4/0x350 [ 171.793561] ksys_write+0x70/0x108 [ 171.796995] __arm64_sys_write+0x1c/0x28 [ 171.800952] invoke_syscall+0x48/0x10c [ 171.804740] el0_svc_common.constprop.0+0x40/0xe0 [ 171.809487] do_el0_svc+0x1c/0x28 [ 171.812834] el0_svc+0x34/0x108 [ 171.816013] el0t_64_sync_handler+0xa0/0xe4 [ 171.820237] el0t_64_sync+0x198/0x19c [ 171.823939] Code: 32000262 b90ac293 1a931056 9134e293 (b9000036) [ 171.830073] ---[ end trace 0000000000000000 ]---
--- drivers/gpu/drm/imagination/pvr_fw_trace.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/imagination/pvr_fw_trace.c +1 -1
@@ -558,6 +558,6 @@ pvr_fw_trace_debugfs_init(struct pvr_device *pvr_dev, struct dentry *dir) &pvr_fw_trace_fops); } -debugfs_create_file ("trace_mask" ,0600 , dir, fw_trace, +debugfs_create_file ("trace_mask" ,0600 , dir, pvr_dev, &pvr_fw_trace_mask_fops); }
Signature · 1 line
2.54.0
Greg Kroah-Hartman
maintainerPATCH 301/307 ALSA: caiaq: fix usb_dev refcount leak on probe failure
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Deepanshu Kartikey <[email protected]>
commit 7a5f1cd22d47f8ca4b760b6334378ae42c1bd24b upstream.
create_card() takes a reference on the USB device with usb_get_dev() and stores the matching usb_put_dev() in card_free(), which is installed as the snd_card's ->private_free destructor.
However, ->private_free is only assigned near the end of init_card(), after several failure points (usb_set_interface(), EP type checks, usb_submit_urb(), the EP1_CMD_GET_DEVICE_INFO exchange, and its timeout). When any of those fail, init_card() returns an error to snd_probe(), which calls snd_card_free(card). Because ->private_free is still NULL, card_free() never runs, the usb_get_dev() reference is not dropped, and the struct usb_device leaks along with its descriptor allocations and device_private.
syzbot reproduces this with a malformed UAC3 device whose only valid altsetting is 0; init_card()'s usb_set_interface(usb_dev, 0, 1) call fails with -EIO and triggers the leak.
Move the ->private_free assignment into create_card(), immediately after usb_get_dev(), so that every error path reaching snd_card_free() balances the reference. card_free()'s callees (snd_usb_caiaq_input_free, free_urbs, kfree) already tolerate the partially-initialized state because the chip private area is zero-initialized by snd_card_new().
--- sound/usb/caiaq/device.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/usb/caiaq/device.c +1 -1
@@ -423,6 +423,7 @@ static int create_card(struct usb_device cdev =caiaqdev (card); cdev->chip.dev =usb_get_dev (usb_dev); + card->private_free = card_free; cdev->chip.card = card; cdev->chip.usb_id =USB_ID (le16_to_cpu (usb_dev->descriptor.idVendor),le16_to_cpu (usb_dev->descriptor.idProduct));
@@ -511,7 +512,6 @@ static int init_card(struct snd_usb_caiascnprintf (card->longname,sizeof (card->longname),"%s %s (%s)" , cdev->vendor_name, cdev->product_name, usbpath); - card->private_free = card_free; err =setup_card (cdev);if (err <0 ) goto err_kill_urb;
Greg Kroah-Hartman
maintainerPATCH 302/307 ALSA: aloop: Fix peer runtime UAF during format-change stop
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Cássio Gabriel <[email protected]>
commit e5c33cdc6f402eab8abd36ecf436b22c9d3a8aff upstream.
loopback_check_format() may stop the capture side when playback starts with parameters that no longer match a running capture stream. Commit 826af7fa62e3 ("ALSA: aloop: Fix racy access at PCM trigger") moved the peer lookup under cable->lock, but the actual snd_pcm_stop() still runs after dropping that lock.
A concurrent close can clear the capture entry from cable->streams[] and detach or free its runtime while the playback trigger path still holds a stale peer substream pointer.
Keep a per-cable count of in-flight peer stops before dropping cable->lock, and make free_cable() wait for those stops before detaching the runtime. This preserves the existing behavior while making the peer runtime lifetime explicit.
--- sound/drivers/aloop.c | 43 ++++++++++++++++++++++++++++++------------- 1 file changed, 30 insertions(+), 13 deletions(-)
sound/drivers/aloop.c +30 -13
@@ -99,6 +99,9 @@ struct loopback_ops {struct loopback_cable {spinlock_t lock;struct loopback_pcm *streams[2 ]; +/* in-flight peer stops running outside cable->lock */ +atomic_t stop_count; +wait_queue_head_t stop_wait;struct snd_pcm_hardware hw;/* flags */ unsigned int valid;
@@ -366,8 +369,11 @@ static int loopback_check_format(structreturn 0 ;if (stream ==SNDRV_PCM_STREAM_CAPTURE )return -EIO ; -else if (cruntime->state ==SNDRV_PCM_STATE_RUNNING ) +else if (cruntime->state ==SNDRV_PCM_STATE_RUNNING ) { +/* close must not free the peer runtime below */ +atomic_inc (&cable->stop_count); stop_capture = true; + } } setup =get_setup (dpcm_play);
@@ -396,8 +402,11 @@ static int loopback_check_format(struct } } -if (stop_capture) +if (stop_capture) {snd_pcm_stop (dpcm_capt->substream,SNDRV_PCM_STATE_DRAINING ); +if (atomic_dec_and_test (&cable->stop_count)) +wake_up (&cable->stop_wait); + }return 0 ; }
@@ -1049,23 +1058,29 @@ static void free_cable(struct snd_pcm_sustruct loopback *loopback = substream->private_data;int dev =get_cable_index (substream);struct loopback_cable *cable; +struct loopback_pcm *dpcm; +bool other_alive; cable = loopback->cables[substream->number][dev];if (!cable)return ; -if (cable->streams[!substream->stream]) { -/* other stream is still alive */ -guard (spinlock_irq)(&cable->lock); - cable->streams[substream->stream] =NULL ; - }else { -struct loopback_pcm *dpcm = substream->runtime->private_data; -if (cable->ops && cable->ops->close_cable && dpcm) - cable->ops->close_cable (dpcm); -/* free the cable */ - loopback->cables[substream->number][dev] =NULL ; -kfree (cable); + scoped_guard(spinlock_irq, &cable->lock) { + cable->streams[substream->stream] =NULL ; + other_alive = cable->streams[!substream->stream]; } + +/* Pair with the stop_count increment in loopback_check_format(). */ +wait_event (cable->stop_wait, !atomic_read (&cable->stop_count)); +if (other_alive) +return ; + + dpcm = substream->runtime->private_data; +if (cable->ops && cable->ops->close_cable && dpcm) + cable->ops->close_cable (dpcm); +/* free the cable */ + loopback->cables[substream->number][dev] =NULL ; +kfree (cable); }static int loopback_jiffies_timer_open (struct loopback_pcm *dpcm)
@@ -1260,6 +1275,8 @@ static int loopback_open(struct snd_pcm_ goto unlock; }spin_lock_init (&cable->lock); +atomic_set (&cable->stop_count,0 ); +init_waitqueue_head (&cable->stop_wait); cable->hw = loopback_pcm_hardware;if (loopback->timer_source) cable->ops = &loopback_snd_timer_ops;
Greg Kroah-Hartman
maintainerPATCH 303/307 vmalloc: fix buffer overflow in vrealloc_node_align()
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marco Elver <[email protected]>
commit 82d1f01292d3f09bf063f829f8ab8de12b4280a1 upstream.
Commit 4c5d3365882d ("mm/vmalloc: allow to set node and align in vrealloc") added the ability to force a new allocation if the current pointer is on the wrong NUMA node, or if an alignment constraint is not met, even if the user is shrinking the allocation.
On this path (need_realloc), the code allocates a new object of 'size' bytes and then memcpy()s 'old_size' bytes into it. If the request is to shrink the object (size < old_size), this results in an out-of-bounds write on the new buffer.
Fix this by bounding the copy length by the new allocation size.
--- mm/vmalloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/vmalloc.c +1 -1
@@ -4361,7 +4361,7 @@ need_realloc:return NULL ;if (p) { -memcpy (n, p, old_size); +memcpy (n, p,min (size, old_size));vfree (p); }
Greg Kroah-Hartman
maintainerPATCH 304/307 mm/page_alloc: return NULL early from alloc_frozen_pages_nolock() in NMI on UP
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Harry Yoo (Oracle) <[email protected]>
commit 620b46ed6ae17c8438d889c8c0cfddab36a1476c upstream.
On UP kernels (!CONFIG_SMP), spin_trylock() is a no-op that unconditionally succeeds even when the lock is already held. As a result, alloc_frozen_pages_nolock() called from NMI context can re-enter rmqueue() and acquire the zone lock that the interrupted context is already holding, corrupting the freelists.
With CONFIG_DEBUG_SPINLOCK on UP, the following BUG is triggered with the slub_kunit test module:
BUG: spinlock trylock failure on UP on CPU#0, kunit_try_catch/243 [...] Call Trace: <NMI> dump_stack_lvl+0x3f/0x60 do_raw_spin_trylock+0x41/0x50 _raw_spin_trylock+0x24/0x50 rmqueue.isra.0+0x2a9/0xa70 get_page_from_freelist+0xeb/0x450 alloc_frozen_pages_nolock_noprof+0x111/0x1e0 allocate_slab+0x42a/0x500 ___slab_alloc+0xa7/0x4c0 kmalloc_nolock_noprof+0x164/0x310 [...] </NMI>
Fix this by returning NULL early when invoked from NMI on a UP kernel.
--- mm/page_alloc.c | 5 +++++ 1 file changed, 5 insertions(+)
mm/page_alloc.c +5 -0
@@ -7806,6 +7806,11 @@ struct page *alloc_frozen_pages_nolock_n*/ if (IS_ENABLED (CONFIG_PREEMPT_RT ) && (in_nmi () ||in_hardirq ()))return NULL ; + +/* On UP, spin_trylock() always succeeds even when it is locked */ +if (!IS_ENABLED (CONFIG_SMP ) &&in_nmi ()) +return NULL ; +if (!pcp_allowed_order (order))return NULL ;
Greg Kroah-Hartman
maintainerPATCH 305/307 mm/slab: return NULL early from kmalloc_nolock() in NMI on UP
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Harry Yoo (Oracle) <[email protected]>
commit 5b31044e649e3e54c2caef135c09b371c2fbcd08 upstream.
On UP kernels (!CONFIG_SMP), spin_trylock() is a no-op that unconditionally succeeds even when the lock is already held. As a result, kmalloc_nolock() called from NMI context can re-enter the slab allocator and acquire n->list_lock that the interrupted context is already holding, corrupting slab state.
With CONFIG_DEBUG_SPINLOCK on UP, the following BUG is triggered with the slub_kunit test module:
BUG: spinlock trylock failure on UP on CPU#0, kunit_try_catch/243 [...] Call Trace: <NMI> dump_stack_lvl+0x3f/0x60 do_raw_spin_trylock+0x41/0x50 _raw_spin_trylock+0x24/0x50 get_from_partial_node+0x120/0x4d0 ___slab_alloc+0x8a/0x4c0 kmalloc_nolock_noprof+0x164/0x310 [...] </NMI>
Fix this by returning NULL early when invoked from NMI on a UP kernel.
--- mm/slub.c | 4 ++++ 1 file changed, 4 insertions(+)
mm/slub.c +4 -0
@@ -5304,6 +5304,10 @@ void *kmalloc_nolock_noprof(size_t size,if (IS_ENABLED (CONFIG_PREEMPT_RT ) && (in_nmi () ||in_hardirq ()))return NULL ; +/* On UP, spin_trylock() always succeeds even when it is locked */ +if (!IS_ENABLED (CONFIG_SMP ) &&in_nmi ()) +return NULL ; + retry:if (unlikely (size >KMALLOC_MAX_CACHE_SIZE ))return NULL ;
Greg Kroah-Hartman
maintainerPATCH 306/307 net: ipv6: fix NOREF dst use in seg6 and rpl lwtunnels
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andrea Mayer <[email protected]>
commit f9c52a6ba9780bd27e0bf4c044fd91c13c778b6e upstream.
seg6_input_core() and rpl_input() call ip6_route_input() which sets a NOREF dst on the skb, then pass it to dst_cache_set_ip6() invoking dst_hold() unconditionally.
On PREEMPT_RT, ksoftirqd is preemptible and a higher-priority task can release the underlying pcpu_rt between the lookup and the caching through a concurrent FIB lookup on a shared nexthop. Simplified race sequence:
ksoftirqd/X higher-prio task (same CPU X)
----------- --------------------------------
seg6_input_core(,skb)/rpl_input(skb)
dst_cache_get()
-> miss
ip6_route_input(skb)
-> ip6_pol_route(,skb,flags)
[RT6_LOOKUP_F_DST_NOREF in flags]
-> FIB lookup resolves fib6_nh
[nhid=N route]
-> rt6_make_pcpu_route()
[creates pcpu_rt, refcount=1]
pcpu_rt->sernum = fib6_sernum
[fib6_sernum=W]
-> cmpxchg(fib6_nh.rt6i_pcpu,
NULL, pcpu_rt)
[slot was empty, store succeeds]
-> skb_dst_set_noref(skb, dst)
[dst is pcpu_rt, refcount still 1]
rt_genid_bump_ipv6()
-> bumps fib6_sernum
[fib6_sernum from W to Z]
ip6_route_output()
-> ip6_pol_route()
-> FIB lookup resolves fib6_nh
[nhid=N]
-> rt6_get_pcpu_route()
pcpu_rt->sernum != fib6_sernum
[W <> Z, stale]
-> prev = xchg(rt6i_pcpu, NULL)
-> dst_release(prev)
[prev is pcpu_rt,
refcount 1->0, dead]
dst = skb_dst(skb)
[dst is the dead pcpu_rt]
dst_cache_set_ip6(dst)
-> dst_hold() on dead dst
-> WARN / use-after-freeFor the race to occur, ksoftirqd must be preemptible (PREEMPT_RT without PREEMPT_RT_NEEDS_BH_LOCK) and a concurrent task must be able to release the pcpu_rt. Shared nexthop objects provide such a path, as two routes pointing to the same nhid share the same fib6_nh and its rt6i_pcpu entry.
Fix seg6_input_core() and rpl_input() by calling skb_dst_force() after ip6_route_input() to force the NOREF dst into a refcounted one before caching.
The output path is not affected as ip6_route_output() already returns a refcounted dst.
--- net/ipv6/rpl_iptunnel.c | 9 +++++++++ net/ipv6/seg6_iptunnel.c | 9 +++++++++ 2 files changed, 18 insertions(+)
net/ipv6/rpl_iptunnel.c +9 -0
@@ -287,7 +287,16 @@ static int rpl_input(struct sk_buff *skbif (!dst) {ip6_route_input (skb); + +/* ip6_route_input() sets a NOREF dst; force a refcount on it +* before caching or further use. +*/ +skb_dst_force (skb); dst =skb_dst (skb); +if (unlikely (!dst)) { + err = -ENETUNREACH ; + goto drop; + }/* cache only if we don't create a dst reference loop */ if (!dst->error && lwtst != dst->lwtstate) {
net/ipv6/seg6_iptunnel.c +9 -0
@@ -500,7 +500,16 @@ static int seg6_input_core(struct net *nif (!dst) {ip6_route_input (skb); + +/* ip6_route_input() sets a NOREF dst; force a refcount on it +* before caching or further use. +*/ +skb_dst_force (skb); dst =skb_dst (skb); +if (unlikely (!dst)) { + err = -ENETUNREACH ; + goto drop; + }/* cache only if we don't create a dst reference loop */ if (!dst->error && lwtst != dst->lwtstate) {
Greg Kroah-Hartman
maintainerPATCH 307/307 netfilter: reject zero shift in nft_bitwise
In reply to Greg Kroah-Hartman7.0-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kai Ma <[email protected]>
commit fe11e5c40817b84abaa5d83bfb6586d8412bfd07 upstream.
Reject zero shift operands for nft_bitwise left and right shift expressions during initialization.
The carry propagation logic computes the carry from the adjacent 32-bit word using BITS_PER_TYPE(u32) - shift. A zero shift operand turns this into a 32-bit shift, which is undefined behaviour.
Reject zero shift operands in the control plane, alongside the existing check for values greater than or equal to 32, so malformed rules never reach the packet path.
--- net/netfilter/nft_bitwise.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/netfilter/nft_bitwise.c +2 -1
@@ -196,7 +196,8 @@ static int nft_bitwise_init_shift(structif (err <0 )return err; -if (priv->data.data[0 ] >=BITS_PER_TYPE (u32)) { +if (!priv->data.data[0 ] || + priv->data.data[0 ] >=BITS_PER_TYPE (u32)) {nft_data_release (&priv->data, desc.type);return -EINVAL ; }
# Librecast Test Results
020/020 [ OK ] liblcrq
010/010 [ OK ] libmld
120/120 [ OK ] liblibrecast
CPU/kernel: Linux auntie 7.0.4-rc1-g4a299534048e #3 SMP PREEMPT_DYNAMIC Mon May 4 14:06:50 -00 2026 x86_64 AMD Ryzen 9 9950X 16-Core Processor AuthenticAMD GNU/Linux
Hi
no regressions here on x86_64 (Intel 11th Gen. CPU)
Thanks
Am 04.05.2026 um 15:48 schrieb Greg Kroah-Hartman:
Quoted 4 lines
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Builds, boots and works on my 2-socket Ivy Bridge Xeon E5-2697 v2 server. No dmesg oddities or regressions found.
Beste Grüße,
Peter Schneider
Signature · 8 lines
Climb the mountain not to plant your flag, but to embrace the challenge, enjoy the air and behold the view. Climb it so you can see the world, not so the world can see you. -- David McCullough Jr. OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244 Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc https://keys.mailvelope.com/pks/lookup?op=get&[email protected] https://keys.mailvelope.com/pks/lookup?op=get&[email protected]
Hi Greg
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 06 May 2026 13:50:49 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.0.4-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-7.0.y
and the diffstat can be found below.thanks,
greg k-h
Linux version 7.0.4-rc1 tested.
Build successfully completed.
Boot successfully completed.
No dmesg regressions.
Video output normal.
Sound output normal.
Lenovo ThinkPad X1 Carbon Gen10(Intel i7-1260P(x86_64) arch linux)
[ 0.000000] Linux version 7.0.4-rc1rv-g4a299534048e
(takeshi@ThinkPadX1Gen10J0764) (gcc (GCC) 16.1.1 20260430, GNU ld (GNU Binutils) 2.46.0) #1 SMP PREEMPT_DYNAMIC Tue May 5 05:03:52 JST 2026
Thanks
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 06 May 2026 13:50:49 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.0.4-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-7.0.y
and the diffstat can be found below.thanks,
greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on BMIPS_GENERIC:
Signature · 1 line
Florian
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 06 May 2026 13:50:49 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.0.4-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-7.0.y
and the diffstat can be found below.thanks,
greg k-h
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Quoted 8 lines · On Mon, 04 May 2026 15:48:05 +0200 Greg Kroah-Hartman…
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 06 May 2026 13:50:49 +0000. Anything received after that time might be too late.
Boot-tested under QEMU for Rust x86_64, arm64 and riscv64; built-tested for loongarch64:
Thanks!
Cheers,
Miguel
Luna Jernberg
Tested-byAMD Ryzen 5 5600 6-Core Processor:
https://www.inet.se/produkt/5304697/amd-ryzen-5-5600-3-5-ghz-35mb on a
https://www.gigabyte.com/Motherboard/B550-AORUS-ELITE-V2-rev-12
https://www.inet.se/produkt/1903406/gigabyte-b550-aorus-elite-v2
motherboard :)
Den tis 5 maj 2026 kl 11:54 skrev Miguel Ojeda <[email protected]>:
Quoted 21 lines · On Mon, 04 May 2026 15:48:05 +0200 Greg Kroah-Hartman…
Quoted 8 lines
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 06 May 2026 13:50:49 +0000. Anything received after that time might be too late.
Boot-tested under QEMU for Rust
x86_64, arm64 and riscv64; built-tested for loongarch64:Tested-by Miguel Ojeda <[email protected]>Thanks!
Cheers,
Miguel
Quoted 4 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 06 May 2026 13:50:49 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.0.4-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-7.0.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 06 May 2026 13:50:49 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.0.4-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-7.0.y
and the diffstat can be found below.thanks,
greg k-h
Tested rc1 against the Fedora build system (aarch64, ppc64le, s390x, x86_64), and boot tested x86_64. No regressions noted.
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 06 May 2026 13:50:49 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.0.4-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-7.0.y
and the diffstat can be found below.thanks,
greg k-h
Tested on 3 different amd64 systems. Working well, no regressions observed.
Signature · 1 line
-Barry K. Nathan <[email protected]>
Quoted 15 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 7.0.4 release. There are 307 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 06 May 2026 13:50:49 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v7.x/stable-review/patch-7.0.4-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-7.0.y
and the diffstat can be found below.
Quoted 5 lines
thanks,
greg k-h
-------------
The kernel was built successfully and booted without any issues in the virtual environment. No dmesg regressions were observed during testing.
kernel version: 7.0.4-rc1
Configurations: x86_64_defconfig, defconfig
Architectures: arm64, x86_64
Kernel Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Commit: 4a299534048e330448f6cd13a87bb7d23549b6d6
Regards,
Dileep Malepu.