{"id":1581,"date":"2026-11-16T07:37:24","date_gmt":"2026-11-16T06:37:24","guid":{"rendered":"https:\/\/www.cisilino.com\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/"},"modified":"2026-11-16T08:24:55","modified_gmt":"2026-11-16T07:24:55","slug":"debian-kernel-package-6-1-0-55-ext4-oops-rollback","status":"publish","type":"post","link":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/","title":{"rendered":"Debian kernel package 6.1.0-55: ext4 oops and rollback"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">On Sunday 15 November 2026, at 19:48 Italian time (18:48 UTC), I stepped in on some of the servers I manage after the monitoring alert. The problem had most likely started a few minutes earlier. The common denominator was the update to the Debian kernel package 6.1.0-55, installed a few hours before, and I rolled back to the previous kernel. The fault is insidious, so I am documenting it carefully: what I observed, what the sources say and what I still do not know.<\/p>\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/11\/debian-kernel-package-6-1-0-55-ext4-oops.webp\" alt=\"Diagram of the Debian kernel package 6.1.0-55: ext4 oops and rollback\" width=\"1200\" height=\"630\"\/><\/figure>\n\n\n<h2 class=\"wp-block-heading\">Account: the 19:48 intervention<\/h2>\n\n\n<p class=\"wp-block-paragraph\">The kernel had moved from the 6.1.0-54 series to 6.1.0-55. The packages at fault are <code>linux-image-6.1.0-55-amd64<\/code> and <code>linux-image-6.1.0-55-arm64<\/code>, Debian release <code>6.1.192-1<\/code> (upstream kernel 6.1.192), which came from the <code>bookworm-security<\/code> repository of Debian 12. Before rolling out an update I test it on a monitoring host that I use for exactly this purpose. There the new kernel caused no problem at all, not even during the stress tests.<\/p>\n\n\n<p class=\"wp-block-paragraph\">It was not a clean crash but a performance degradation: a progressive slowdown ending in a system freeze. Meanwhile the TCP layer kept working: ping answered and ports accepted connections. Until application-level monitoring fired, it was impossible to tell whether a server was down, and only by connecting to the individual ports was the timeout visible. That is why 19:48 is the time of the intervention, not the exact time the problem began.<\/p>\n\n\n<p class=\"wp-block-paragraph\">The servers involved are few, but of two architectures: amd64 and arm64. At first I suspected a memory fault or a single disk. The same symptom on two different architectures quickly ruled out a hardware cause.<\/p>\n\n\n<p class=\"wp-block-paragraph\">The problem then showed up on the other servers too. I checked the kernel logs on every machine: all of them showed an Oops, that is, an error the kernel detects in one of its own functions and records with a trace. I therefore decided to go back, and at 20:08 (19:08 UTC) I rolled back the kernel updates, returning the servers to 6.1.0-54.<\/p>\n\n\n<h2 class=\"wp-block-heading\">Incident timeline<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Times for Sunday 15 November 2026, in Italian time (CET) and UTC. Italy is on UTC+1.<\/p>\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Critical phase, 19:48-20:08 (18:48-19:08 UTC):<\/strong> intervention after the application alert, with the degradation having started a few minutes earlier. The servers slow down until they freeze; I analyse the logs, identify the Oops and decide on the rollback.<\/li>\n\n<li><strong>Observation, medium risk, 20:08-24:00 (19:08-23:00 UTC):<\/strong> on the servers back on 6.1.0-54 I check that no other problems have appeared.<\/li>\n\n<li><strong>Closure, at 01:00 on 16 November (00:00 UTC):<\/strong> checks and monitoring end and the activity is closed.<\/li>\n<\/ul>\n\n\n<h2 class=\"wp-block-heading\">An insidious bug: why the tests did not catch it<\/h2>\n\n\n<p class=\"wp-block-paragraph\">This is the aspect that struck me most: the Debian kernel package 6.1.0-55 did not cause an immediate, widespread failure. On servers with little disk load it caused no problem at all. The monitoring host, which I use to test updates before rolling them out, passed the stress tests with no errors or alerts.<\/p>\n\n\n<p class=\"wp-block-paragraph\">As I interpret it, the error does not depend on the kernel alone but on a condition: the page holding the block map must have been evicted from memory. A server with few block writes and releases can go for days without meeting it, and a stress test that loads CPU or network does not touch it. It takes disk traffic, with files being created and deleted, and memory under pressure.<\/p>\n\n\n<p class=\"wp-block-paragraph\">I draw a practical lesson: an &#8220;all green&#8221; test on a lightly loaded machine proves little for a bug of this kind. I say so openly.<\/p>\n\n\n<p class=\"wp-block-paragraph\">There is another reason it is insidious: it does not look like a failure. The system slows down, but ping and ports still answer, so a network-only check reports that everything is fine. Only a check that actually exercises the service notices.<\/p>\n\n\n<h2 class=\"wp-block-heading\">What the Oops says<\/h2>\n\n\n<p class=\"wp-block-paragraph\">An Oops looks unreadable, but three pieces of information are enough to interpret it: the type of error, the function where it occurs and the call chain leading to it.<\/p>\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Type of error:<\/strong> on amd64 a NULL pointer dereference, meaning the kernel read an invalid address. On arm64 the picture is the same, with a trace that starts from a directory removal.<\/li>\n\n<li><strong>Function:<\/strong> <code>ext4_mb_load_buddy_gfp<\/code>, at offset <code>+0xbc<\/code> on amd64. It is the same function on both architectures.<\/li>\n\n<li><strong>Call chain (amd64):<\/strong> closing a file (<code>close()<\/code>) leads to <code>ext4_release_file<\/code>, then to <code>ext4_discard_preallocations<\/code> and finally to the function above. On arm64 the trace starts instead from <code>vfs_rmdir<\/code>.<\/li>\n<\/ul>\n\n\n<p class=\"wp-block-paragraph\">In short, the crash does not depend on an application or a driver but on the ext4 code that handles block allocation on disk: a part of the kernel used by practically every machine with this filesystem. The servers&#8217; filesystem was ext4, in one case with journalled quotas enabled. It remains to be clarified whether disk load is the only factor or whether RAM and quotas also play a part.<\/p>\n\n\n<h2 class=\"wp-block-heading\">The mballoc buddy cache in brief<\/h2>\n\n\n<p class=\"wp-block-paragraph\">ext4 does not allocate blocks at random. Its allocator, called mballoc, keeps for each block group a map of the free ones, organised with the buddy system technique. These maps reside in memory pages, the so-called buddy cache.<\/p>\n\n\n<p class=\"wp-block-paragraph\">When blocks have to be allocated or freed, <code>ext4_mb_load_buddy_gfp<\/code> loads the map of the relevant group. If the page is already in memory it takes it at once. If it has been discarded, for example because memory is scarce, it reads it back from disk.<\/p>\n\n\n<p class=\"wp-block-paragraph\">The case in which the page is no longer in memory is where the two code paths diverge, and that is where, according to the sources, the problem lies.<\/p>\n\n\n<h2 class=\"wp-block-heading\">What the sources say about the Debian kernel package 6.1.0-55<\/h2>\n\n\n<p class=\"wp-block-paragraph\">First, the important thing: the problem is already reported in the Debian bug tracker. <a href=\"https:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=1154101\" target=\"_blank\" rel=\"noopener\">#1154101<\/a> (system freeze after the update) is dated 15 November 2026, <a href=\"https:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=1154108\" target=\"_blank\" rel=\"noopener\">#1154108<\/a> (NULL pointer dereference in <code>ext4_mb_load_buddy_gfp<\/code>, &#8220;regression from 6.1.190-1&#8221;) is from 15 November at 23:09 UTC, <a href=\"https:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=1154119\" target=\"_blank\" rel=\"noopener\">#1154119<\/a> is from 16 November. All of them give version <code>6.1.192-1<\/code> as the one where it appears. They came after my incident: the first, #1154101, is about three hours later. I did not find a CVE.<\/p>\n\n\n<p class=\"wp-block-paragraph\">The picture that emerges is this. Kernel 6.1.191, released on 30 October 2026, brought into the 6.1 branch the conversion of the mballoc buddy cache and bitmap from the old &#8220;page&#8221; to &#8220;folio&#8221;. You can read it in <a href=\"https:\/\/www.kernel.org\/pub\/linux\/kernel\/v6.x\/ChangeLog-6.1.191\" target=\"_blank\" rel=\"noopener\">ChangeLog-6.1.191<\/a>. It is the code where the Oops I observed occurs.<\/p>\n\n\n<p class=\"wp-block-paragraph\">Then there is <a href=\"https:\/\/github.com\/sporevm\/kernels\/pull\/13\" target=\"_blank\" rel=\"noopener\">pull request 13 of the sporevm\/kernels project<\/a>, merged on 11 November 2026. The authors report an identical Oops, in the same function, on their 6.1.191 kernel. Their explanation is this: in the backport the code checks the result of <code>__filemap_get_folio()<\/code> with <code>IS_ERR()<\/code>, but in 6.1 that function, when it does not find the page, returns NULL. The check does not trigger and the NULL pointer is then used. The problem appears when the buddy cache pages are discarded, because of low memory or with <code>drop_caches<\/code>. With 6.1.155 they do not see it, with 6.1.191 they do. They write that the fix for the 6.1 branch is queued and that 6.1.192 does not contain it.<\/p>\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.kernel.org\/pub\/linux\/kernel\/v6.x\/ChangeLog-6.1.192\" target=\"_blank\" rel=\"noopener\">ChangeLog-6.1.192<\/a> gives indirect confirmation: the fix was not there. It contains three commits, all on Xen drivers, and none on ext4. 6.1.192, on which the Debian package 6.1.0-55 is based, therefore came out without the fix, a circumstance consistent with what I observed on the servers.<\/p>\n\n\n<h2 class=\"wp-block-heading\">What is confirmed and what is hypothesis<\/h2>\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Confirmed by my logs:<\/strong> Oops in <code>ext4_mb_load_buddy_gfp<\/code> with kernel 6.1.0-55 on amd64 and arm64, while 6.1.0-54 is stable.<\/li>\n\n<li><strong>Confirmed by the changelogs:<\/strong> 6.1.191 contains the conversion of mballoc to folio and 6.1.192 has nothing on ext4, so no fix.<\/li>\n\n<li><strong>Hypothesis, reported by external sources:<\/strong> the cause is the <code>IS_ERR()<\/code> check on a value that in 6.1 can be NULL. The sporevm pull request and report <a href=\"https:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=1154108\" target=\"_blank\" rel=\"noopener\">#1154108<\/a> both point to it; the latter also says a fix is queued for 6.1.193. These are claims by the reporters and I have not verified them against the source.<\/li>\n\n<li><strong>Not available:<\/strong> a fixed package. As of 16 November 2026 the Debian Package Tracker shows <code>6.1.192-1<\/code> as the latest bookworm-security version. I have not analysed the Debian kernel source line by line.<\/li>\n<\/ul>\n\n\n<p class=\"wp-block-paragraph\">The hypothesis is plausible because it explains all the symptoms: the same function, both architectures, a NULL dereference and the link with memory pressure. It remains a hypothesis.<\/p>\n\n\n<h2 class=\"wp-block-heading\">Why close() and rmdir<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Two different paths lead to the same function. When a file is closed, ext4 releases the block preallocations it had reserved. Removing a directory frees real blocks. In both cases the block group map is needed, hence the buddy cache.<\/p>\n\n\n<p class=\"wp-block-paragraph\">That is why the crash looks random: it only happens if, at that moment, the map page is not in memory. A machine with plenty of free RAM can hold out for a long time, while one with memory under pressure, or that often drops its cache, gets there sooner.<\/p>\n\n\n<h2 class=\"wp-block-heading\">Rolling back the Debian kernel package 6.1.0-55, step by step<\/h2>\n\n\n<p class=\"wp-block-paragraph\">The method is to go back to the previous kernel without deleting anything and to stop the new one from reinstalling itself. The commands below are an example: adapt them to your package names and do not run them on a production machine without knowing what they do. I accept no liability for incorrect use.<\/p>\n\n\n<p class=\"wp-block-paragraph\">First I check which kernel is running and which are installed:<\/p>\n\n\n<pre class=\"wp-block-code\"><code>uname -r\ndpkg -l \"linux-image-*\" | grep ^ii<\/code><\/pre>\n\n\n<p class=\"wp-block-paragraph\">Then I set the previous kernel as the default boot entry in GRUB. Alternatively the new package can be removed after rebooting; I leave it installed but inactive:<\/p>\n\n\n<pre class=\"wp-block-code\"><code># vedo le voci disponibili\ngrep -E \"menuentry |submenu \" \/boot\/grub\/grub.cfg | cut -d\"'\" -f2\n# scelgo il kernel 6.1.0-54 come predefinito (adatta la stringa)\nsudo grub-set-default \"Advanced options for Debian GNU\/Linux&gt;Debian GNU\/Linux, with Linux 6.1.0-54-amd64\"\nsudo update-grub\nsudo reboot<\/code><\/pre>\n\n\n<p class=\"wp-block-paragraph\">After the reboot I check that the correct kernel is running, then I hold the kernel packages. The <code>apt-mark hold<\/code> command prevents apt from upgrading them until I remove it:<\/p>\n\n\n<pre class=\"wp-block-code\"><code>uname -r\nsudo apt-mark hold linux-image-amd64 linux-image-6.1.0-55-amd64   # amd64\nsudo apt-mark hold linux-image-arm64 linux-image-6.1.0-55-arm64   # arm64 (6.1.192-1)\napt-mark showhold<\/code><\/pre>\n\n\n<p class=\"wp-block-paragraph\">On arm64 servers the package is called <code>linux-image-6.1.0-55-arm64<\/code>, again at release <code>6.1.192-1<\/code>. The hold is temporary: when Debian publishes a fixed version I will remove it with <code>apt-mark unhold<\/code>. Keep in mind that a hold on the kernel also covers security updates of the same package, so it should be lifted as soon as possible.<\/p>\n\n\n<p class=\"wp-block-paragraph\">Always check that the hold is active with <code>apt-mark showhold<\/code>: it must list <code>linux-image-amd64<\/code> (or <code>linux-image-arm64<\/code>). A simulation with <code>apt-get -s upgrade<\/code> is not enough: <code>apt-get upgrade<\/code> does not install new packages and keeps the metapackage back even without a hold, whereas <code>apt upgrade<\/code> would install it. For a reliable check use <code>apt -s upgrade | grep -i linux-image<\/code> and make sure no <code>Inst linux-image<\/code> line appears.<\/p>\n\n\n<h2 class=\"wp-block-heading\">How to tell whether a server is exposed<\/h2>\n\n\n<p class=\"wp-block-paragraph\">No special tools are needed: three checks on the machine are enough.<\/p>\n\n\n<pre class=\"wp-block-code\"><code># versione del kernel in esecuzione\nuname -r\n# Oops recenti nei log del kernel\njournalctl -k -b -1 --no-pager | grep -i -E \"ext4_mb_load_buddy|Oops|BUG:\" | head\n# memoria e cache\nfree -h<\/code><\/pre>\n\n\n<p class=\"wp-block-paragraph\">If the Debian kernel package 6.1.0-55 is in use and the filesystem is ext4, you are in scope. The risk grows if the machine runs with little free memory. If <code>ext4_mb_load_buddy_gfp<\/code> appears in the logs of the previous boot, it is the same problem.<\/p>\n\n\n<p class=\"wp-block-paragraph\">One further precaution: if your crons contain a periodic <code>drop_caches<\/code>, remove it while you use this kernel, because dropping the cache is the action that, according to the sources, triggers the error. It is not general advice: normally <code>drop_caches<\/code> is not needed.<\/p>\n\n\n<h2 class=\"wp-block-heading\">What I am watching<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Before putting the Debian kernel package 6.1.0-55 back into production I check the <a href=\"https:\/\/tracker.debian.org\/pkg\/linux\" target=\"_blank\" rel=\"noopener\">Debian Package Tracker<\/a> for a new version of the linux package and read its changelog, looking in particular for an entry on ext4 and mballoc. If one appears, I test it on a single machine before unblocking the others, and this time with real disk load. I have already covered kernel monitoring, for example in the article on <a href=\"https:\/\/www.cisilino.com\/en\/2026\/10\/31\/linux-kernel-vulnerability-tcp-ipv4-cve-2026-98432\/\">the TCP vulnerability from late October<\/a>: that was a security flaw, this is a stability regression, but the method is the same.<\/p>\n\n\n<p class=\"wp-block-paragraph\">I will update this article when Debian publishes the fix.<\/p>\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n<ul class=\"wp-block-list\">\n<li>Debian bugs <a href=\"https:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=1154108\" target=\"_blank\" rel=\"noopener\">#1154108<\/a>, <a href=\"https:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=1154101\" target=\"_blank\" rel=\"noopener\">#1154101<\/a> and <a href=\"https:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=1154119\" target=\"_blank\" rel=\"noopener\">#1154119<\/a>: reports of the same problem on version 6.1.192-1.<\/li>\n\n<li><a href=\"https:\/\/www.kernel.org\/pub\/linux\/kernel\/v6.x\/ChangeLog-6.1.191\" target=\"_blank\" rel=\"noopener\">ChangeLog-6.1.191<\/a>: conversion of mballoc to folio, kernel.org.<\/li>\n\n<li><a href=\"https:\/\/www.kernel.org\/pub\/linux\/kernel\/v6.x\/ChangeLog-6.1.192\" target=\"_blank\" rel=\"noopener\">ChangeLog-6.1.192<\/a>: Xen fixes only, kernel.org.<\/li>\n\n<li><a href=\"https:\/\/github.com\/sporevm\/kernels\/pull\/13\" target=\"_blank\" rel=\"noopener\">pull request 13 of the sporevm\/kernels project<\/a>: Oops in <code>ext4_mb_load_buddy_gfp<\/code> on 6.1.191, explanation with <code>IS_ERR()<\/code> and NULL (single external source).<\/li>\n\n<li><a href=\"https:\/\/tracker.debian.org\/pkg\/linux\" target=\"_blank\" rel=\"noopener\">Debian Package Tracker<\/a>: status of the Debian kernel packages.<\/li>\n<\/ul>\n\n\n<p class=\"wp-block-paragraph\"><em>Debian is a registered trademark of Software in the Public Interest, Inc. Linux is a trademark of Linus Torvalds. Commands are shown for information only, without warranty.<\/em><\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>On Sunday 15 November 2026, at 19:48 Italian time (18:48 UTC), I stepped in on some of the servers I manage after the monitoring alert. The problem had most likely started a few minutes earlier. The common denominator was the update to the Debian kernel package 6.1.0-55, installed a few hours before, and I rolled [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1580,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"wpai_generated_summary":"","footnotes":""},"categories":[361],"tags":[386,598,531,602,411],"class_list":["post-1581","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-servers-databases","tag-debian-en","tag-ext4-en","tag-linux-kernel","tag-rollback-en","tag-server-security"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"The Debian kernel package 6.1.0-55 triggered ext4 oopses on servers I manage: timeline, what the sources say and the rollback to 6.1.0-54.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"matteocisilino\"\/>\n\t<meta name=\"google-site-verification\" content=\"_A-1f0dO30IDVHfP9muflI8kHQs-H4YOi8WLUkYzuLE\" \/>\n\t<link rel=\"canonical\" href=\"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_GB\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Matteo Cisilino - Guide su WordPress, server e sicurezza\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"Debian kernel package 6.1.0-55: ext4 oops and rollback\" \/>\n\t\t<meta property=\"og:description\" content=\"The Debian kernel package 6.1.0-55 triggered ext4 oopses on servers I manage: timeline, what the sources say and the rollback to 6.1.0-54.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/11\/debian-kernel-package-6-1-0-55-ext4-oops.webp\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/11\/debian-kernel-package-6-1-0-55-ext4-oops.webp\" \/>\n\t\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-11-16T06:37:24+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-11-16T07:24:55+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Debian kernel package 6.1.0-55: ext4 oops and rollback\" \/>\n\t\t<meta name=\"twitter:description\" content=\"The Debian kernel package 6.1.0-55 triggered ext4 oopses on servers I manage: timeline, what the sources say and the rollback to 6.1.0-54.\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/11\/debian-kernel-package-6-1-0-55-ext4-oops.webp\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BlogPosting\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#blogposting\",\"name\":\"Debian kernel package 6.1.0-55: ext4 oops and rollback\",\"headline\":\"Debian kernel package 6.1.0-55: ext4 oops and rollback\",\"author\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/author\\\/matteocisilino\\\/#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/#organization\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.cisilino.com\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/debian-kernel-package-6-1-0-55-ext4-oops.webp\",\"width\":1200,\"height\":630,\"caption\":\"Diagram of the Debian kernel package 6.1.0-55: ext4 oops and rollback\"},\"datePublished\":\"2026-11-16T07:37:24+01:00\",\"dateModified\":\"2026-11-16T08:24:55+01:00\",\"inLanguage\":\"en-GB\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#webpage\"},\"articleSection\":\"Servers and databases, Debian, ext4, Linux kernel, rollback, server security\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/category\\\/servers-databases\\\/#listItem\",\"name\":\"Servers and databases\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/category\\\/servers-databases\\\/#listItem\",\"position\":2,\"name\":\"Servers and databases\",\"item\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/category\\\/servers-databases\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#listItem\",\"name\":\"Debian kernel package 6.1.0-55: ext4 oops and rollback\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#listItem\",\"position\":3,\"name\":\"Debian kernel package 6.1.0-55: ext4 oops and rollback\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/category\\\/servers-databases\\\/#listItem\",\"name\":\"Servers and databases\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/#organization\",\"name\":\"Matteo Cisilino\",\"description\":\"Guide su WordPress, server e sicurezza\",\"url\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.cisilino.com\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/logo-cisilino-512.png\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#organizationLogo\",\"width\":512,\"height\":512,\"caption\":\"Logo: un cerchio a sinistra che si divide in cerchi pi\\u00f9 piccoli\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#organizationLogo\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/author\\\/matteocisilino\\\/#author\",\"url\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/author\\\/matteocisilino\\\/\",\"name\":\"matteocisilino\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/639872265f0661e8aee8924ba9d756b00ea816f8286fab99a5116c729d49618f?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"matteocisilino\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#webpage\",\"url\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/\",\"name\":\"Debian kernel package 6.1.0-55: ext4 oops and rollback\",\"description\":\"The Debian kernel package 6.1.0-55 triggered ext4 oopses on servers I manage: timeline, what the sources say and the rollback to 6.1.0-54.\",\"inLanguage\":\"en-GB\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/author\\\/matteocisilino\\\/#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/author\\\/matteocisilino\\\/#author\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.cisilino.com\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/debian-kernel-package-6-1-0-55-ext4-oops.webp\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#mainImage\",\"width\":1200,\"height\":630,\"caption\":\"Diagram of the Debian kernel package 6.1.0-55: ext4 oops and rollback\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/2026\\\/11\\\/16\\\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\\\/#mainImage\"},\"datePublished\":\"2026-11-16T07:37:24+01:00\",\"dateModified\":\"2026-11-16T08:24:55+01:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/\",\"name\":\"Matteo Cisilino\",\"description\":\"Guide su WordPress, server e sicurezza\",\"inLanguage\":\"en-GB\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.cisilino.com\\\/en\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Debian kernel package 6.1.0-55: ext4 oops and rollback","description":"The Debian kernel package 6.1.0-55 triggered ext4 oopses on servers I manage: timeline, what the sources say and the rollback to 6.1.0-54.","canonical_url":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"google-site-verification":"_A-1f0dO30IDVHfP9muflI8kHQs-H4YOi8WLUkYzuLE","miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BlogPosting","@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#blogposting","name":"Debian kernel package 6.1.0-55: ext4 oops and rollback","headline":"Debian kernel package 6.1.0-55: ext4 oops and rollback","author":{"@id":"https:\/\/www.cisilino.com\/en\/author\/matteocisilino\/#author"},"publisher":{"@id":"https:\/\/www.cisilino.com\/en\/#organization"},"image":{"@type":"ImageObject","url":"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/11\/debian-kernel-package-6-1-0-55-ext4-oops.webp","width":1200,"height":630,"caption":"Diagram of the Debian kernel package 6.1.0-55: ext4 oops and rollback"},"datePublished":"2026-11-16T07:37:24+01:00","dateModified":"2026-11-16T08:24:55+01:00","inLanguage":"en-GB","mainEntityOfPage":{"@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#webpage"},"isPartOf":{"@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#webpage"},"articleSection":"Servers and databases, Debian, ext4, Linux kernel, rollback, server security"},{"@type":"BreadcrumbList","@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/www.cisilino.com\/en\/#listItem","position":1,"name":"Home","item":"https:\/\/www.cisilino.com\/en\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.cisilino.com\/en\/category\/servers-databases\/#listItem","name":"Servers and databases"}},{"@type":"ListItem","@id":"https:\/\/www.cisilino.com\/en\/category\/servers-databases\/#listItem","position":2,"name":"Servers and databases","item":"https:\/\/www.cisilino.com\/en\/category\/servers-databases\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#listItem","name":"Debian kernel package 6.1.0-55: ext4 oops and rollback"},"previousItem":{"@type":"ListItem","@id":"https:\/\/www.cisilino.com\/en\/#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#listItem","position":3,"name":"Debian kernel package 6.1.0-55: ext4 oops and rollback","previousItem":{"@type":"ListItem","@id":"https:\/\/www.cisilino.com\/en\/category\/servers-databases\/#listItem","name":"Servers and databases"}}]},{"@type":"Organization","@id":"https:\/\/www.cisilino.com\/en\/#organization","name":"Matteo Cisilino","description":"Guide su WordPress, server e sicurezza","url":"https:\/\/www.cisilino.com\/en\/","logo":{"@type":"ImageObject","url":"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/10\/logo-cisilino-512.png","@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#organizationLogo","width":512,"height":512,"caption":"Logo: un cerchio a sinistra che si divide in cerchi pi\u00f9 piccoli"},"image":{"@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#organizationLogo"}},{"@type":"Person","@id":"https:\/\/www.cisilino.com\/en\/author\/matteocisilino\/#author","url":"https:\/\/www.cisilino.com\/en\/author\/matteocisilino\/","name":"matteocisilino","image":{"@type":"ImageObject","@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/639872265f0661e8aee8924ba9d756b00ea816f8286fab99a5116c729d49618f?s=96&d=mm&r=g","width":96,"height":96,"caption":"matteocisilino"}},{"@type":"WebPage","@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#webpage","url":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/","name":"Debian kernel package 6.1.0-55: ext4 oops and rollback","description":"The Debian kernel package 6.1.0-55 triggered ext4 oopses on servers I manage: timeline, what the sources say and the rollback to 6.1.0-54.","inLanguage":"en-GB","isPartOf":{"@id":"https:\/\/www.cisilino.com\/en\/#website"},"breadcrumb":{"@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#breadcrumblist"},"author":{"@id":"https:\/\/www.cisilino.com\/en\/author\/matteocisilino\/#author"},"creator":{"@id":"https:\/\/www.cisilino.com\/en\/author\/matteocisilino\/#author"},"image":{"@type":"ImageObject","url":"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/11\/debian-kernel-package-6-1-0-55-ext4-oops.webp","@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#mainImage","width":1200,"height":630,"caption":"Diagram of the Debian kernel package 6.1.0-55: ext4 oops and rollback"},"primaryImageOfPage":{"@id":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/#mainImage"},"datePublished":"2026-11-16T07:37:24+01:00","dateModified":"2026-11-16T08:24:55+01:00"},{"@type":"WebSite","@id":"https:\/\/www.cisilino.com\/en\/#website","url":"https:\/\/www.cisilino.com\/en\/","name":"Matteo Cisilino","description":"Guide su WordPress, server e sicurezza","inLanguage":"en-GB","publisher":{"@id":"https:\/\/www.cisilino.com\/en\/#organization"}}]},"og:locale":"en_GB","og:site_name":"Matteo Cisilino - Guide su WordPress, server e sicurezza","og:type":"article","og:title":"Debian kernel package 6.1.0-55: ext4 oops and rollback","og:description":"The Debian kernel package 6.1.0-55 triggered ext4 oopses on servers I manage: timeline, what the sources say and the rollback to 6.1.0-54.","og:url":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/","og:image":"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/11\/debian-kernel-package-6-1-0-55-ext4-oops.webp","og:image:secure_url":"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/11\/debian-kernel-package-6-1-0-55-ext4-oops.webp","og:image:width":1200,"og:image:height":630,"article:published_time":"2026-11-16T06:37:24+00:00","article:modified_time":"2026-11-16T07:24:55+00:00","twitter:card":"summary_large_image","twitter:title":"Debian kernel package 6.1.0-55: ext4 oops and rollback","twitter:description":"The Debian kernel package 6.1.0-55 triggered ext4 oopses on servers I manage: timeline, what the sources say and the rollback to 6.1.0-54.","twitter:image":"https:\/\/www.cisilino.com\/wp-content\/uploads\/2026\/11\/debian-kernel-package-6-1-0-55-ext4-oops.webp"},"aioseo_meta_data":{"post_id":"1581","title":"Debian kernel package 6.1.0-55: ext4 oops and rollback","description":"The Debian kernel package 6.1.0-55 triggered ext4 oopses on servers I manage: timeline, what the sources say and the rollback to 6.1.0-54.","keywords":null,"keyphrases":{"focus":{"keyphrase":"debian kernel package 6.1.0-55"},"additional":[]},"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_custom_url":null,"og_image_custom_fields":null,"og_image_url":null,"og_image_width":null,"og_image_height":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_image_url":null,"twitter_title":null,"twitter_description":null,"schema_type":"default","schema_type_options":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"limit_modified_date":false,"ai":null,"breadcrumb_settings":null,"seo_analyzer_scan_date":null,"created":"2026-11-16 06:37:11","updated":"2026-11-16 06:37:11","focus_keyword":"debian kernel package 6.1.0-55","additional_keywords":null,"truseo_locale":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.cisilino.com\/en\/\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.cisilino.com\/en\/category\/servers-databases\/\" title=\"Servers and databases\">Servers and databases<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tDebian kernel package 6.1.0-55: ext4 oops and rollback\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/www.cisilino.com\/en\/"},{"label":"Servers and databases","link":"https:\/\/www.cisilino.com\/en\/category\/servers-databases\/"},{"label":"Debian kernel package 6.1.0-55: ext4 oops and rollback","link":"https:\/\/www.cisilino.com\/en\/2026\/11\/16\/debian-kernel-package-6-1-0-55-ext4-oops-rollback\/"}],"_links":{"self":[{"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/posts\/1581","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/comments?post=1581"}],"version-history":[{"count":1,"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/posts\/1581\/revisions"}],"predecessor-version":[{"id":1589,"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/posts\/1581\/revisions\/1589"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/media\/1580"}],"wp:attachment":[{"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/media?parent=1581"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/categories?post=1581"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cisilino.com\/en\/wp-json\/wp\/v2\/tags?post=1581"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}