This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1029.33 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1010.10 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1056.61+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-aws-fips' to
This bug is awaiting verification that the linux-aws/5.15.0-1056.61
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-oracle/5.15.0-1053.59
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-oracle' to 'verification-done-
jammy-linux-oracle'.
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1050.56 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-25.25~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
hwe-6.5' to
This bug is awaiting verification that the linux-azure/6.5.0-1016.16
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-aws/6.5.0-1015.15
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the
** Tags removed: verification-needed-jammy-linux-ibm-gt-fips
** Tags added: verification-done-jammy-linux-ibm-gt-fips
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2047634
Title:
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1055.58+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-ibm-gt-fips' to
booting with 6.5.0-25.25, and run L2CAP test case, all testcase in PTS
could pass. Verification done for Mantic.
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
** Tags removed: verification-needed-mantic-linux
** Tags added:
booting with 5.15.0-100.110, and run L2CAP test case, all testcase in
PTS could pass. Verification done for Jammy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2047634
Title:
Reject
This bug is awaiting verification that the linux/6.5.0-25.25 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/5.15.0-100.110 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: High => Medium
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
**
The review request is for Jammy kernel, I sent the review request on
Jan 9, and already got 2 Acks. This patch will be handled in the cycle
2024.02.05, and will finish the SRU in the week of 04-Mar.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2047634
Title:
Reject connection when malformed L2CAP signal packet
** Description changed:
+ The patch is merged in mainline kernel v6.7-rc7, so Noble kernel
+ already have this fix. And this patch is CCed to sta...@vger.kernel.org,
+ M and L kernel will have this fix with the SRU update sooner or later.
+ For Jammy kernel, an OEM customer is waiting for this
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2047634
Title:
Reject connection when malformed L2CAP signal packet
noble kernel will have this patch automatically since the version of
noble kernel is v6.7 at least (Probably v6.8).
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Hui Wang (hui.wang)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
--
You received this
The patch is merged to mainline kernel v6.7-rc7, and this patch is also
CCed to sta...@vger.kernel.org, so in theory, this patch will be merged
to ubuntu kernel (jammy & noble) automatically with the SRU update.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2047634
Title:
Reject connection when malformed L2CAP
32 matches
Mail list logo
