@kernellogger@fosstodon.org
@kernellogger@fosstodon.org avatar

kernellogger

@kernellogger@fosstodon.org

Mainly tooting about #Linux the #kernel and things related to the #LinuxKernel – e.g. #bootloader, #compiler, #git, #glibc, #mesa, #qemu, #xorg, #X11, #wayland, and other stuff in the 'plumbing' layer.

Opinions are my own.

Topic account. Other accounts of mine:

https://social.linux.pizza/@knurd42 (EN): #FLOSS, #Fedora as well as Life, the Universe and Everything
https://norden.social/@thleemhuis (DE): Das Leben, das Universum und der ganze Rest
https://social.tchncs.de/@thleemhuisfoss (DE): #FLOSS

searchable

This profile is from a federated server and may be incomplete. Browse more on the original instance.

kernellogger, to linux
@kernellogger@fosstodon.org avatar

A question for experts on bisecting the :

Assume someone runs into a regression when updating from 6.1.90[1] to 6.6.30 that needs bisecting. What do you suggest:

  • Check manually which mainline release (e.g. 6.2, 6.3, ...) introduced the problem and afterwards bisect between that and the previous release.

  • Bisect straight between 6.1 and 6.6.30.

1/ I guess I would definitely go for…

[1] let's assume that 6.1 was fine for this scenario to keep things simpler

kernellogger,
@kernellogger@fosstodon.org avatar

2/ …the first option, if the user has access to pre-compiled kernel packages that make it easy to test those mainline releases (or stable kernels derived from it) .

But what's the better approach if the user has no such packages at hand?

kernellogger,
@kernellogger@fosstodon.org avatar

@klausman

Yeah, definitely.

Another dragon in that field: .config changes where the packager enabled some new feature (say a new security technique that is known to cause problems for some old apps) that causes a regression.

Is rare, but does happen.

kernellogger, to linux
@kernellogger@fosstodon.org avatar

6.9 is out.

LWN.net's list of new features:

Linus' release announcement: https://lore.kernel.org/lkml/CAHk-=whnKYL-WARzrZhVTZ8RP3WZc24C9_DT7JMJooONNT2udQ@mail.gmail.com/

[The kernelnewbies text is not yet ready]

kernellogger,
@kernellogger@fosstodon.org avatar

2/ From Linus' announcement:

"'So Thorsten is still reporting a few regression fixes that haven't made it to me yet, but none of them look big or worrisome enough to delay the release for another week. […]

So 6.9 is now out, and last week has looked quite stable […]

And I now have a more powerful arm64 machine (thanks to Ampere), so the last week I've been doing almost as many arm64 builds as I have x86-64 […]

[…] obviously this means that tomorrow the merge window for 6.10 opens […]"'

kernellogger,
@kernellogger@fosstodon.org avatar

3/ If anyone wants details on "So Thorsten is still reporting a few regression fixes that haven't made it to me yet[…]", see https://lore.kernel.org/all/171552254677.1971316.17732013113090096417@leemhuis.info/

kernellogger, to linux
@kernellogger@fosstodon.org avatar

might soon start supporting the 5 thx to patches from Andrea della Porta:

https://lore.kernel.org/lkml/cover.1715332922.git.andrea.porta@suse.com/ – Add minimal boot support for Raspberry Pi 5

If you just thought "But Linux already supports the , see ", then you just learned why differentiating between the called Linux (meant here) and operating systems called Linux (often build from forks of the former carrying modifications and enhancements) is important.

kernellogger, to linux
@kernellogger@fosstodon.org avatar

Looks like 6.10 will drop support for a few old machines:

https://lore.kernel.org/all/20240503081125.67990-1-arnd@kernel.org/

"'[…]
alpha: remove DECpc AXP150 (Jensen) support
alpha: sable: remove early machine support
alpha: remove LCA and APECS based machines
alpha: cabriolet: remove EV5 CPU support
alpha: drop pre-EV56 support
[…]
72 files changed, 166 insertions(+), 4545 deletions(-)'"

These changes from @arnd since today can be found in linux-next, too.

pid_eins, to random
@pid_eins@mastodon.social avatar

1️⃣0️⃣ Here's the 10th installment of posts highlighting key new features of the upcoming v256 release of systemd.

You might be aware of systemd-sysext: a component of systemd that can overlay immutable disk images (DDIs) on top of /usr/, to extend it in a secure, and again, immutable fashion. It has a companion tool systemd-confext that does the same over /etc/.

kernellogger,
@kernellogger@fosstodon.org avatar

@pid_eins

Nitpicking: I like the series a lot, but here is a tip from a former writer/editor:

I'm pretty sure you would reach a (much?) bigger audience if the first toot in the thread has the most interesting bit, e.g. something to make people want to read that thread – and not somewhat boring sentence they might have read a few times before plus a sentence + some also somewhat boring toots that just set the stage.

E.g. make it look more like this: [see reply to self]

kernellogger,
@kernellogger@fosstodon.org avatar

@pid_eins

1️⃣0️⃣ Highlights in the upcoming systemd v256:

The new --mutable= switch to systemd-sysext/systemd-confext makes it easier to tinker with immutable systems created by these tools: it allows opting into a writable layer to the top of the stack, to perform local modifications in /usr/ or /etc/. This writable layer can either be on a tmpfs, or backed by a writable fs – so that the resulting layer when finished can become a proper sysext layer of its own right later on, if desired.

kernellogger,
@kernellogger@fosstodon.org avatar

@pid_eins

Ha, I can understand that to a point. 😄 🥴 😬

But at the same time I doubt that the approach I suggested will make a difference in that area, as I expect some of the "problematic folks" will look out for things they dislike and then will try to alarm the others no matter what… :eyeroll:

kernellogger, to random
@kernellogger@fosstodon.org avatar

A History of C Compilers - Part 1: Performance, Portability and Freedom

The first part of a whistle stop tour of the history of C compilers. Also GNU/Linux, dragons and lots of architectures!

https://thechipletter.substack.com/p/a-history-of-c-compilers-part-1-performance

kernellogger, to linux
@kernellogger@fosstodon.org avatar

6.9-rc7 is out:

https://lore.kernel.org/all/CAHk-%3DwiT0EJV%2BX-%3D-dMmL%2Bq3_kyQCxV-WPxb8m8Q6dtWOxjCcg@mail.gmail.com/

"'The stats for 6.9 continue to look very normal, and nothing looks particularly alarming. […]'"

kernellogger, to linux
@kernellogger@fosstodon.org avatar

Even wanted to know what this iomap thing in the is?

Then check out this docs rfc patch from Ritesh Harjani:

https://lore.kernel.org/all/17e84cbae600898269e9ad35046ce6dc929036ae.1714744795.git.ritesh.list@gmail.com/

"'[…] is a filesystem centric mapping layer that maps file's logical offset ranges to physical extents. It provides several iterator APIs which filesystems can use for doing various file_operations, address_space_operations, vm_operations, inode_operations etc. It supports APIs for doing direct-io, buffered-io, lseek, dax-io, page-mkwrite, […]'"

kernellogger, (edited ) to linux
@kernellogger@fosstodon.org avatar

The 's team just published their thousandth CVE[1]. 🥳 🙃

This happened 78 days after the effort was announced[2].

Note, 26 of the 1003 CVE entries published so far were later rejected. For details check https://git.kernel.org/pub/scm/linux/security/vulns.git/ or https://lore.kernel.org/linux-cve-announce/

[1] https://git.kernel.org/pub/scm/linux/security/vulns.git/commit/?id=55441d0dd1f40c5762cd7cf8c9ca312ed0964c4a

[2] http://www.kroah.com/log/blog/2024/02/13/linux-is-a-cna/

kernellogger,
@kernellogger@fosstodon.org avatar

@gregkh

Thx for the additional details (but FWIW, seems you missed that the toot already had mentioned that 26 were rejected 😬 whatever, easy to miss).

And thx for all your work, too!

kernellogger, (edited ) to linux
@kernellogger@fosstodon.org avatar

The Kernel Report - Jonathan Corbet (@corbet), @LWN

The recording of this recent talk is now available on the schedule page: https://ossna2024.sched.com/event/1aBNs/the-kernel-report-jonathan-corbet-lwnnet

Slides can be found here: https://static.lwn.net/talks/2024/kr-ossna.pdf

Direct link to the recording: https://www.youtube.com/watch?v=DAqjl_x4hZc

kernellogger, to linux
@kernellogger@fosstodon.org avatar
kernellogger, to random
@kernellogger@fosstodon.org avatar

The recording of Linus Torvalds' (@torvalds) fireside chat with Dirk Hohndel (@dirkhh) recently held at the North America is now online:

https://www.youtube.com/watch?v=cPvRIWXNgaM

kernellogger, to random
@kernellogger@fosstodon.org avatar

v2.45.0 is out.

GitHub blog post with some highlights: https://github.blog/2024-04-29-highlights-from-git-2-45/

Announcement: https://lore.kernel.org/lkml/xmqq8r0ww0sj.fsf@gitster.g/

From the former:

'"[…] introduces preliminary support for a new reference storage backend called “reftable,” promising faster lookups, reads, and writes for repositories with any number of references. […]

Preliminary support for SHA-1 and SHA-256 interoperability

[…] git config learned a new option to help document your .gitconfig file […]"'

kernellogger, (edited ) to random
@kernellogger@fosstodon.org avatar

Moving GPU drivers out of the initramfs https://hansdegoede.dreamwidth.org/28291.html

Hans de Goede writes: "'The firmware which drm/kms drivers need is becoming bigger and bigger and there is a push […]

This has made me think about dropping the GPU drivers from the initramfs and instead make plymouth work well/better with simpledrm (on top of efifb). A while ago I discussed making this change for Fedora with the Red Hat graphics team spoiler: For now nothing is going to change. […]'"

codonell, to random
@codonell@fosstodon.org avatar

Don't forget that Y2038 is coming...

kernellogger,
@kernellogger@fosstodon.org avatar

@codonell

Following @countdownY2K38 IMHO is the best way to not forget that Y2038 is coming. 😬

kernellogger, to linux
@kernellogger@fosstodon.org avatar

6.9-rc6 is out:

https://lore.kernel.org/lkml/CAHk-=witYatGg+jW1kVu2Moq6yF2JNFe3wn7G0sMNhE=H=9voA@mail.gmail.com/

"'Things continue to look pretty normal, and nothing here really stands out. The biggest single change that stands out in the diffstat is literally a documentation update[1], […]

[…] please do keep testing,

Linus'"

[1] upps, sorry, guess that's my fault https://git.kernel.org/torvalds/c/4d2008430ce87061c9cefd4f83daf2d5bb323a96 🥴

kernellogger, (edited )
@kernellogger@fosstodon.org avatar

The changes[1] that triggered Linus' "The biggest single change that stands out in the diffstat is literally a documentation update" comment in the 6.9-rc6 announcement were the last I had in the works for the "How to verify bugs and bisect regressions" text added earlier this cycle.

But if you spot any errors, there are still at least 13 days to point them out to me so I can fix them before the 6.9 release: https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html

[1] https://git.kernel.org/torvalds/c/4d2008430ce87061c9cefd4f83daf2d5bb323a96

kernellogger, to linux
@kernellogger@fosstodon.org avatar

How Allegro reduced latency outliers by 82% by switching to :

https://blog.allegro.tech/2024/03/kafka-performance-analysis.html

"'Using a combination of packet sniffing, , and async-profiler we managed to identify the root cause of slow produce requests in our Kafka cluster. We then tested a couple of solutions to the problem: data=writeback journaling mode, fast commits, and changing the file system to XFS.[…] With XFS, the number of produce requests exceeding 65ms (our SLO) was lowered by 82%.'"

kernellogger,
@kernellogger@fosstodon.org avatar

@Lalufu

well, you know how it is with "well known": https://xkcd.com/1053/

  • All
  • Subscribed
  • Moderated
  • Favorites
  • Leos
  • khanakhh
  • magazineikmin
  • Durango
  • thenastyranch
  • Youngstown
  • slotface
  • cisconetworking
  • InstantRegret
  • ngwrru68w68
  • rosin
  • kavyap
  • tsrsr
  • DreamBathrooms
  • modclub
  • hgfsjryuu7
  • everett
  • osvaldo12
  • mdbf
  • tester
  • tacticalgear
  • PowerRangers
  • GTA5RPClips
  • vwfavf
  • ethstaker
  • normalnudes
  • cubers
  • anitta
  • All magazines