lp:~ubuntu-kernel/ubuntu/+source/linux/+git/noble
- Get this repository:
-
git clone
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble
Branches
Name | Last Modified | Last Commit |
---|---|---|
hwe-6.11-next | 2025-02-17 09:40:21 UTC |
UBUNTU: Ubuntu-hwe-6.11-6.11.0-19.19~24.04.1
Author:
Stefan Bader
UBUNTU: Ubuntu- Signed-off-by: Stefan Bader <stefan. |
master-prep | 2025-02-14 13:04:26 UTC |
UBUNTU: Ubuntu-6.8.0-56.58
Author:
Mehmet Basaran
UBUNTU: Ubuntu-6.8.0-56.58 Signed-off-by: Mehmet Basaran <mehmet. |
master-next | 2025-02-14 13:04:26 UTC |
UBUNTU: Ubuntu-6.8.0-56.58
Author:
Mehmet Basaran
UBUNTU: Ubuntu-6.8.0-56.58 Signed-off-by: Mehmet Basaran <mehmet. |
master- |
2025-02-12 17:13:41 UTC |
UBUNTU: [Packaging] linux-tools: Fall back to old python perf path
Author:
Juerg Haefliger
UBUNTU: [Packaging] linux-tools: Fall back to old python perf path BugLink: https:/ linux-tools from older kernels without these patches provide the Signed-off-by: Juerg Haefliger <juerg. |
lowlatency- |
2025-02-08 20:32:06 UTC |
UBUNTU: Ubuntu-lowlatency-hwe-6.11-6.11.0-1010.11~24.04.1
Author:
Manuel Diewald
UBUNTU: Ubuntu- Signed-off-by: Manuel Diewald <manuel. |
lowlatency-next | 2025-02-08 00:16:40 UTC |
UBUNTU: Ubuntu-lowlatency-6.8.0-54.56.1
Author:
Manuel Diewald
UBUNTU: Ubuntu- Signed-off-by: Manuel Diewald <manuel. |
master- |
2025-01-10 11:27:46 UTC |
net: sched: fix ordering of qlen adjustment
Author:
Lion Ackermann
net: sched: fix ordering of qlen adjustment Changes to sch->q.qlen around qdisc_tree_ Signed-off-by: Lion Ackermann <nnamrec@gmail.com> |
lowlatency- |
2024-12-04 02:48:36 UTC |
UBUNTU: Ubuntu-lowlatency-6.8.0-50.51.1
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu- Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
hwe-6.11- |
2024-12-04 02:01:07 UTC |
UBUNTU: Ubuntu-hwe-6.11-6.11.0-13.14~24.04.1
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu- Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
master- |
2024-12-02 15:17:18 UTC |
UBUNTU: Ubuntu-6.8.0-51.52
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu-6.8.0-51.52 Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
master- |
2024-11-30 17:52:54 UTC |
mm/mglru: only clear kswapd_failures if reclaimable
Author:
Wei Xu
mm/mglru: only clear kswapd_failures if reclaimable BugLink: https:/ lru_gen_ Only clear kswap_failures in lru_gen_ I happened to run into this problem in one of my tests recently. It Link: https:/ (cherry picked from commit b130ba4a6259f6b |
master- |
2024-11-21 22:15:47 UTC |
UBUNTU: Ubuntu-6.8.0-51.51
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu-6.8.0-51.51 Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
lowlatency- |
2024-11-15 16:29:06 UTC |
UBUNTU: Ubuntu-lowlatency-6.8.0-49.49.1
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu- Signed-off-by: Ubuntu Kernel Bot <kernel- |
master- |
2024-11-15 14:56:22 UTC |
UBUNTU: Ubuntu-6.8.0-49.49
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu-6.8.0-49.49 Signed-off-by: Ubuntu Kernel Bot <kernel- |
lowlatency- |
2024-11-09 20:38:45 UTC |
UBUNTU: Ubuntu-lowlatency-6.8.0-49.49.1
Author:
Mehmet Basaran
UBUNTU: Ubuntu- Signed-off-by: Mehmet Basaran <mehmet. |
master- |
2024-11-08 07:24:30 UTC |
UBUNTU: Ubuntu-6.8.0-50.50
Author:
Mehmet Basaran
UBUNTU: Ubuntu-6.8.0-50.50 Signed-off-by: Mehmet Basaran <mehmet. |
master | 2024-11-01 10:56:32 UTC |
UBUNTU: Ubuntu-6.8.0-49.49
Author:
Manuel Diewald
UBUNTU: Ubuntu-6.8.0-49.49 Signed-off-by: Manuel Diewald <manuel. |
master- |
2024-10-31 13:41:40 UTC |
sch/netem: fix use after free in netem_dequeue
Author:
Stephen Hemminger
sch/netem: fix use after free in netem_dequeue commit 3b3a2a9c6349e25 If netem_dequeue() enqueues packet to inner qdisc and that qdisc Commands to trigger KASAN UaF: ip link add type dummy Fixes: 50612537e9ab ("netem: fix classful handling") |
lowlatency- |
2024-10-25 21:55:54 UTC |
UBUNTU: Ubuntu-lowlatency-6.8.0-48.48.1
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu- Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
master- |
2024-10-25 21:07:43 UTC |
UBUNTU: Ubuntu-6.8.0-48.48
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu-6.8.0-48.48 Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
lowlatency- |
2024-10-24 10:39:44 UTC |
UBUNTU: Ubuntu-lowlatency-6.8.0-47.47.1
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu- Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
master- |
2024-09-25 18:05:46 UTC |
netem: fix return value if duplicate enqueue fails
Author:
Stephen Hemminger
netem: fix return value if duplicate enqueue fails There is a bug in netem_enqueue() introduced by This commit made netem_enqueue() always return NET_XMIT_SUCCESS There are two ways for the bug happen: - If the duplicated packet is dropped by rootq->enqueue() and then In both cases NET_XMIT_SUCCESS is returned even though no packets The fix is to defer the enqueue of the duplicate packet until after Fixes: 5845f706388a ("net: netem: fix skb length BUG_ON in __skb_to_sgvec") CVE-2024-45016 |
lowlatency- |
2024-09-02 15:25:58 UTC |
UBUNTU: Ubuntu-lowlatency-6.8.0-45.45.1
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu- Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
master- |
2024-09-02 04:07:59 UTC |
UBUNTU: Ubuntu-6.8.0-45.45
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu-6.8.0-45.45 Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
master- |
2024-08-28 20:03:58 UTC |
bpf: Fix overrunning reservations in ringbuf
Author:
Daniel Borkmann
bpf: Fix overrunning reservations in ringbuf BugLink: https:/ [ Upstream commit cfa1a2329a691ff The BPF ring buffer internally is implemented as a power-of-2 sized circular Each time a record is reserved, the producer that "owns" the record will One aspect that simplifies and thus speeds up the implementation of both Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for For example, consider the creation of a BPF_MAP_ Fix it by calculating the oldest pending_pos and check whether the range Fixes: 457f44363a88 ("bpf: Implement BPF ring buffer and verifier support for it") |
master- |
2024-08-25 19:40:18 UTC |
UBUNTU: Ubuntu-6.8.0-40.40
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu-6.8.0-40.40 Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
master- |
2024-08-25 19:28:55 UTC |
UBUNTU: Ubuntu-6.8.0-39.39
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu-6.8.0-39.39 Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
master- |
2024-08-23 17:57:58 UTC |
UBUNTU: Ubuntu-6.8.0-41.41
Author:
Ubuntu Kernel Bot
UBUNTU: Ubuntu-6.8.0-41.41 Signed-off-by: Ubuntu Kernel Bot <ubuntu- |
master- |
2024-07-30 17:00:13 UTC |
md/md-bitmap: fix writing non bitmap pages
Author:
Ofir Gal
md/md-bitmap: fix writing non bitmap pages BugLink: https:/ __write_sb_page() rounds up the io size to the optimal io size if it For example: The final io size would be 256K (64 pages) but md_bitmap_ This issue caused a data transfer failure in nvme-tcp. The network As of now the network layer assumes all the pages of the IO are The bitmap pages aren't slab pages, the first page of the IO is The bug is reproducible, in order to reproduce we need nvme-over-tcp In order to simulate large optimal IO size you can use dm-stripe with a I have added some logs to test the theory: Cc: stable@ |
master- |
2024-07-05 07:42:08 UTC |
drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access
Author:
=?utf-8?b?VmlsbGUgU3lyasOkbMOk?=
drm/i915: Bypass LMEMBAR/GTTMMADR for MTL stolen memory access BugLink: https:/ On MTL accessing stolen memory via the BARs is somehow borked, Note that on every other platform this itself would hang the The raw stolen memory areas won't be passed to VMs so we'll v2: Don't use direct GSM/DSM access on guests Cc: Joonas Lahtinen <joonas. (cherry picked from commit c08c364102d0728 |
master- |
2024-07-04 19:02:03 UTC |
x86/sev: Check for MWAITX and MONITORX opcodes in the #VC handler
Author:
Tom Lendacky
x86/sev: Check for MWAITX and MONITORX opcodes in the #VC handler The MWAITX and MONITORX instructions generate the same #VC error code as Fixes: e3ef461af35a ("x86/sev: Harden #VC instruction emulation somewhat") CVE-2024-25742 |
master- |
2024-06-07 10:28:52 UTC |
netfilter: nft_set_pipapo: do not free live element
Author:
Florian Westphal
netfilter: nft_set_pipapo: do not free live element [ Upstream commit 3cfc9ec039af60d Pablo reports a crash with large batches of elements with a add_elem( 1) nft_pipapo_remove() removes element 0000000X Looking at the remove function there is a chance that we will drop a Removal happens in two steps, first we do a lookup for key k and return the The _remove function does not work correctly if we have more than one This can happen if we insert an element into a set when the set already In such case its possible that removal will unmap the wrong element. The element that got deactivated (and will be freed later) will Add a check that the fully matching key does in fact map to the element Add a bug/warn trap at the end of the function as well, the remove v2: avoid uneeded temporary variable (Stefano) Fixes: 3c4287f62044 ("nf_tables: Add set type for arbitrary concatenation of ranges") |
master- |
2024-06-07 09:27:56 UTC |
sched/eevdf: Prevent vlag from going out of bounds in reweight_eevdf()
Author:
Xuewen Yan
sched/eevdf: Prevent vlag from going out of bounds in reweight_eevdf() BugLink: https:/ It was possible to have pick_eevdf() return NULL, which then causes a Specifically, reweight_eevdf() computes the vlag without considering Thus limit the range of vlag accordingly. All this was quite rare, but fatal when it does happen. Closes: https:/ (cherry picked from commit 1560d1f6eb6b398 |
lowlatency | 2023-03-15 12:03:00 UTC |
UBUNTU: Ubuntu-lowlatency-6.2.0-1001.1
Author:
Paolo Pisati
UBUNTU: Ubuntu- Signed-off-by: Paolo Pisati <paolo. |
1 → 34 of 34 results | First • Previous • Next • Last |