Conversation
vbabka

Vlastimil Babka

The mm-hotfixes pull request was merged yesterday, including my two fixes for two embarrassing bugs introduced also by myself several/many releases ago. If there's a rc8 instead of 6.8 final tomorrow, you know why...
3
0
5
ljs

Lorenzo Stoakes

Reply to @vbabka
@vbabka ha! Imagine doing some really embarrassing mistake that somebody fixes later that'd never happen to me *anxious cough*
0
0
1
hny@mastodonczech.cz

hny

Reply to @vbabka

@vbabka

0
0
1
vbabka

Vlastimil Babka

Reply to @vbabka
Alright so that didn't result in rc8, so 6.8 is now final, the first kernel since 2.6.16 (March 2006) to have no choice of a slab allocator. And I need a new dead horse to beat.
5
3
15
flameeyes@mastodon.social

Diego Elio Pettenò

Reply to @vbabka

@vbabka HID quirks!

0
0
1
oleksandr@natalenko.name

Oleksandr Natalenko

Reply to @vbabka

@vbabka make THP work with PREEMPT_RT

1
0
1
vbabka

Vlastimil Babka

Reply to @oleksandr@natalenko.name
@oleksandr Sir, I don't do miracles.
0
1
1
lkundrak@metalhead.club

HAMMER SMASHED FILESYSTEM 🇺🇦

Reply to @vbabka

@vbabka what CVE number is that?

1
0
1
vegard@mastodon.social

Vegard Nossum 🥑

Reply to @vbabka

@vbabka Maybe you could write some high-level docs about page allocation? We already have some, but it's a bit on the short side: https://docs.kernel.org/mm/page_allocation.html

0
0
1
ptesarik@fosstodon.org

Petr Tesarik

Reply to @lkundrak@metalhead.club
Edited 3 months ago

@lkundrak @vbabka All Linux CNA Team members are currently busy processing earlier commits. Please hold, and your fixes will be assigned a CVE as soon as possible.

1
0
2
lkundrak@metalhead.club

HAMMER SMASHED FILESYSTEM 🇺🇦

Reply to @ptesarik@fosstodon.org

@ptesarik @vbabka assign a CVE number, then assign a CVE number for the CVE number

0
0
2
osandov@fosstodon.org

Omar Sandoval

Reply to @vbabka

@vbabka obviously the logical conclusion of this work is to delete SLUB, too

1
0
1
oleksandr@natalenko.name

Oleksandr Natalenko

Reply to @osandov@fosstodon.org

@vbabka @osandov pending https://lore.kernel.org/lkml/20230401094658.11146-1-vbabka@suse.cz/

1
0
1
ptesarik@fosstodon.org

Petr Tesarik

Reply to @oleksandr@natalenko.name

@oleksandr @vbabka @osandov I see. Reducing the attack surface should be good for security. But can we then also remove the buddy allocator at some point in the future? The bootmem allocator looks much simpler in comparison…

0
2
1
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: