Debian Codegraph @

debian/linux-base-7.0.12+deb14.1-powerpc64le-64k.NEWS.ppc64el

raw
1 linux (6.18~rc4-1~exp1) experimental; urgency=medium
2
3 The XFS V4 filesystem format is no longer supported. The V5 format,
4 supported since Linux 3.15, should be used instead. You MUST convert
5 any V4 filesystems before running this kernel version.
6
7 To check which format your current XFS filesystems use, run this command
8 as root:
9
10 journalctl -k -b 0 --grep '^XFS .* Mounting V.'
11
12 Unfortunately there is no support for in-place conversion of a V4
13 filesystem to V5. You will need to migrate the files onto newly created
14 V5 filesystems.
15
16 -- Ben Hutchings <[email protected]> Sun, 26 Apr 2026 22:47:35 +0200
17
18 linux (6.17.2-1~exp1) experimental; urgency=medium
19
20 * The bcachefs filesystem has been disabled in Debian kernel packages. This
21 filesystem is no longer being developed in the mainline Linux kernel, and
22 the bcachefs-tools package is also not available in Debian.
23
24 We recommend switching to a different filesystem if you are using bcachefs.
25
26 Alternatively you can use the upstream provided bcachefs dkms packages
27 available at https://apt.bcachefs.org/ .
28
29 -- Salvatore Bonaccorso <[email protected]> Tue, 09 Sep 2025 20:41:27 +0200
30
31 linux (6.10.1-1~exp1) unstable; urgency=medium
32
33 * From Linux 6.10, the default kernel on ppc64 and ppc64el
34 architectures uses 4k page size.
35
36 After rebooting, you need to re-create all swap files or partitions.
37 They depend on the page size and will be not longer usable. See
38 mkswap(8) on how to do that.
39
40 Some file systems might be incompatible with the smaller page size.
41 At least btrfs created with default settings is known to be affected
42 and they will not work with this kernel any more.
43
44 A btrfs file system can be checked with file(1) (use file -s). It
45 will show:
46 BTRFS Filesystem sectorsize 65536
47 If this number is larger then 4096, the file system can not be
48 mounted with the default kernel anymore.
49
50 If you are affected and require the 64k page size of older kernels,
51 you can install linux-image-powerpc64-64k or
52 linux-image-powerpc64el-64k packages.
53
54 -- Bastian Blank <[email protected]> Thu, 11 Jul 2024 11:12:35 +0200
55
56 linux (5.10.46-4) unstable; urgency=medium
57
58 * From Linux 5.10.46-4, unprivileged calls to bpf() are disabled by
59 default, mitigating several security issues. However, an admin can
60 still change this setting later on, if needed, by writing 0 or 1 to
61 the kernel.unprivileged_bpf_disabled sysctl.
62
63 If you prefer to keep unprivileged calls to bpf() enabled, set the
64 sysctl:
65
66 kernel.unprivileged_bpf_disabled = 0
67
68 which is the upstream default.
69
70 -- Salvatore Bonaccorso <[email protected]> Mon, 02 Aug 2021 22:59:24 +0200
71
72 linux (5.10~rc7-1~exp2) unstable; urgency=medium
73
74 * From Linux 5.10, all users are allowed to create user namespaces by
75 default. This will allow programs such as web browsers and container
76 managers to create more restricted sandboxes for untrusted or
77 less-trusted code, without the need to run as root or to use a
78 setuid-root helper.
79
80 The previous Debian default was to restrict this feature to processes
81 running as root, because it exposed more security issues in the
82 kernel. However, the security benefits of more widespread sandboxing
83 probably now outweigh this risk.
84
85 If you prefer to keep this feature restricted, set the sysctl:
86
87 kernel.unprivileged_userns_clone = 0
88
89 -- Ben Hutchings <[email protected]> Sun, 13 Dec 2020 17:11:36 +0100
90
91 linux-latest (86) unstable; urgency=medium
92
93 * From Linux 4.13.10-1, AppArmor is enabled by default. This allows
94 defining a "profile" for each installed program that can mitigate
95 security vulnerabilities in it. However, an incorrect profile might
96 disable some functionality of the program.
97
98 In case you suspect that an AppArmor profile is incorrect, see
99 <https://lists.debian.org/debian-devel/2017/11/msg00178.html> and
100 consider reporting a bug in the package providing the profile. The
101 profile may be part of the program's package or apparmor-profiles.
102
103 -- Ben Hutchings <[email protected]> Thu, 30 Nov 2017 20:08:25 +0000
104
105 linux-latest (81) unstable; urgency=medium
106
107 * From Linux 4.10, the old 'virtual syscall' interface on 64-bit PCs
108 (amd64) is disabled. This breaks chroot environments and containers
109 that use (e)glibc 2.13 and earlier, including those based on Debian 7
110 or RHEL/CentOS 6. To re-enable it, set the kernel parameter:
111 vsyscall=emulate
112
113 -- Ben Hutchings <[email protected]> Fri, 30 Jun 2017 23:50:03 +0100
114
115 linux-latest (76) unstable; urgency=medium
116
117 * From Linux 4.8, several changes have been made in the kernel
118 configuration to 'harden' the system, i.e. to mitigate security bugs.
119 Some changes may cause legitimate applications to fail, and can be
120 reverted by run-time configuration:
121 - On most architectures, the /dev/mem device can no longer be used to
122 access devices that also have a kernel driver. This breaks dosemu
123 and some old user-space graphics drivers. To allow this, set the
124 kernel parameter: iomem=relaxed
125 - The kernel log is no longer readable by unprivileged users. To
126 allow this, set the sysctl: kernel.dmesg_restrict=0
127
128 -- Ben Hutchings <[email protected]> Sat, 29 Oct 2016 02:05:32 +0100
129
130 linux-latest (75) unstable; urgency=medium
131
132 * From Linux 4.7, the iptables connection tracking system will no longer
133 automatically load helper modules. If your firewall configuration
134 depends on connection tracking helpers, you should explicitly load the
135 required modules. For more information, see
136 <https://home.regit.org/netfilter-en/secure-use-of-helpers/>.
137
138 -- Ben Hutchings <[email protected]> Sat, 29 Oct 2016 01:53:18 +0100