kernellogger, to linux
@kernellogger@fosstodon.org avatar

The @LWN article on 6.9 development statistics is now freely available: https://lwn.net/Articles/972605/

'"[…] we are happy to launch the LWN Kernel Source Database as an experimental, subscriber-only feature. Much of the information found in these articles is available there, along with quite a bit more. We encourage readers to play with the system and to let us know what they think. To be clear: there is no plan to stop publishing these articles anytime soon […]"'

kernellogger, to linux
@kernellogger@fosstodon.org avatar

The @LWN article about the latest push of the extensible scheduler class (or "") for is now freely available: https://lwn.net/Articles/972710/

"'[…] Despite having attracted a fair amount of interest from the development community, sched_ext has run into considerable opposition and seems far from acceptance into the mainline. The posting by Tejun Heo of a new version of the sched_ext series at the beginning of May has restarted this long-running discussion[…]'"

mkwadee, to linux
@mkwadee@mastodon.org.uk avatar

Now running 6.8.10.

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

Not sure what this human tried to achieve with the private reply[1] shown in the screenshot, but somehow it made me smile and brightened up my day. 😄

[1] a reply to a regression tracking mail I sent yesterday: https://lore.kernel.org/all/83df4e94-e1ec-42f6-8a15-6439ef4a25b7@leemhuis.info/

wloczykij, to random Polish

Są tu spece od Dockera? Próbuję uruchomić kontener Dockera używają Podmana (https://github.com/TechnitiumSoftware/DnsServer/blob/master/CHANGELOG.md), ale utknąłem. Po wielu próbach, kombinowaniu, aktualizacji setek programów, utknąłem na niemożności uruchomienia kontenera, bo twierdzi, że port 53/tcp jest w użyciu. Zrobiłęm już chyba wszystko, co mi wpadło do głowy, czyli wyłączenie systemd, wyłączenie nasłuchiwania przez systemd na porcie 53 i nic to nie daje. Co ciekawe, netstat nie pokazuje portu 53 jakoby był w użyciu, więc nie wiem nawet, jaki program może tego używać. Co ciekawe, jak wziąłem nmapa z innego hosta, to pokazuje, ze port 53 jest zamkniety, wiec cos tam nasluchuje, ale nie wiem co.
Podobno podman używa jakiegoś własnego serwera DNS do zarządzania siecią między kontenerami, ale nie ogarniam tego, a i nie wiem, czy tu może być problem. Poza tym serwerem podmana, nie przychodzi mi juz nic do glowy.

Macie jakiś pomysł, jak to rozwiązać?

#Podman
#docker
#kontenery
#containers
#networks
#net
#dns
#dnsServer
#port53
#error

wloczykij,

@centopus
Jakiś czas temu zaczałem używać komendy
make localmodconfig
która wycina zbędne moduły. Niestety, ale czasami wycina za dużo i trzeba się bawić potem, więc kernel ma sporo do tego.
Normalnie kernel z kernel.org ma wrzucone mnostwo zbednych modulow i po zbudowaniu, w katalogu /lib/modules/ jest sporo katalogów które zajmują po kilka gigabajtów. Po użyciu tej komendy, katalog z modułami jądra zmniejsza się do kilkudziesięciu megabajtów (czasami kilkaset), więc jest to spora różnica.

Co do kernela i dockera, to znalazłem skrypt
https://raw.githubusercontent.com/moby/moby/master/contrib/check-config.sh
który sprawdza moduły, które są potrzebne do działania dockera. W moim przypadku, marudził, że nie może utworzyć łańcucha DOCKER. Po zaznaczeniu wszystkich opcji, które wskazał ten skrypt, docker ruszył. Niestety, ale po majstrowaniu z kernelem, przestało mi działać jedno urządzeniu i teraz z tym się bawię. Dodatkowo, nad ranem kernel zaliczył zwiechę. Nie jest to ciekawe.

Co do portu, to najwyraźniej przy instalacji dockera, zainstalował się dnsmasq i to on blokował port53.

Na obecną chwilę, wydaje się, że docker działa, ale szczerze mówiąc, nie testowałem go za dużo, bo mam teraz na głowie próby uruchomienia tego urządzenia. Mam nadzieję, że nic innego nie skopało się.

Dam znać, jeśli się okaże, że docker znowu marudzi.
Co do tego urządzenia, to jeśli nic nie poradzę, to pewnie zacznę kolejny wątek i może ktoś pomoże.

#linux
@linux_pl
#linux_kernel
#kernel
#docker

elb, to linux
@elb@social.sdf.org avatar

I was just reminded of following releases via comp.os.linux.announce and downloading .patch.gz minor version updates (because the full kernel took so long!) from SunSite back in the day. make clean; make oldconfig, then make zImage modules modules-install and WAIT. I spent so much time updating kernels for probably no reason. Then the PowerPC came along and I spent a lot of time updating kernels for critical reasons.

jarkko, to linux
@jarkko@social.kernel.org avatar

OK, I submitted an abstract for kernel summit track: "TPM2 story so far...". It would be from the angle of thinking it more like a protocol or contract that all kinds of hardware and TEE's can speak than just a chip per se...

Not that motivated to travel, so not a huge disappointment if not accepted :-) But yeah I have an angle and will prepare that one properly if accepted. So done my duty I guess at least...

https://lpc.events/event/18/abstracts/1801/

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

Jeremy Allison writes:

'" The data shows that “frozen” vendor kernels, created by branching off a release point and then using a team of engineers to select specific patches to back-port to that branch, are buggier than the upstream “stable” Linux created by Greg Kroah-Hartman. '"

https://ciq.com/blog/why-a-frozen-linux-kernel-isnt-the-safest-choice-for-security/

kernellogger, to linux
@kernellogger@fosstodon.org avatar

2024-05-10 8:22 #Linux #kernel #regression report[1]

2024-05-10 13:04 a fix is proposed, which a bit later is confirmed to be working[2]; a msg stating "I'll send out the formal patch next week" follows a few hours later

2024-05-16 14:11 six days later the "Formal patch is still under internal review"[3]

🤨 🥴 😟 😠 #LinuxKernel

[1] https://lore.kernel.org/all/D15TIIDIIESY.D1EKKJLZINMA@fairphone.com/
[2] https://lore.kernel.org/all/4d60ccf3-455d-4189-9100-d35488b00236@quicinc.com/
[3] https://lore.kernel.org/all/4d72f74a-b2eb-43d3-92a2-1311081ce72c@quicinc.com/

jbzfn, to linux
@jbzfn@mastodon.social avatar

👀 PowerPC 40x Processor Support To Be Dropped From The Linux Kernel
@phoronix

"Back in 2020 was a proposal for dropping PowerPC 40x support from the Linux kernel given that the code was orphaned for a long time with no apparent users. The PowerPC 40x processors were found in thin clients, set-top boxes, and other devices during the 90's. Finally now it looks like that the PowerPC 40x removal is set to happen"

https://www.phoronix.com/news/PowerPC-40x-Removal-Patches

kernellogger, to linux
@kernellogger@fosstodon.org avatar

Theo de Raadt and Linus Torvalds are debating mseal(), a #Linux variant of OpenBSD's mimmutable() syscall – which might or might not be merged for #kernel 6.10, as can be seen from other parts of the discussion:

https://lore.kernel.org/all/CAHk-=wgsGCKvN0Db6ZRZqJwXQrmhZyWB6RmABaOp4DiZbXgNew@mail.gmail.com/T/#u

jbzfn, to Amd
@jbzfn@mastodon.social avatar

⚡Linux 6.10 AMD P-State To Deliver Fixes, Better Support On Older Zen CPUs
@phoronix

https://www.phoronix.com/news/Linux-6.10-AMD-P-State

kernellogger, to linux
@kernellogger@fosstodon.org avatar

Linus added a farewell notice to the merge commit that removed alpha EV5 support from mainline (and thus for version 6.10): https://git.kernel.org/torvalds/c/736676f5c3abd1fc01c41813a95246e892937f6d

kernellogger, to linux
@kernellogger@fosstodon.org avatar

Hmm, looks like "NT synchronization primitive emulation" ( aka emulation of Windows NT synchronization primitives) a few people are really looking forward to and meant to be merged for 6.10 might be marked as broken for now (and thus would be impossible to enable) – at least it looks like this from this patch Greg posted, who maintains the subsystem the code resists in:

https://lore.kernel.org/all/2024051450-abrasion-swizzle-550b@gregkh/

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

The latest discussion about the extensible scheduler class (or "sched_ext") for the since yesterday is active again after a post from peterz:

https://lore.kernel.org/all/20240513080359.GI30852@noisy.programming.kicks-ass.net/t/#u

"'That is, from where I am sitting I see $vendor mandate their $enterprise product needs their $BPF scheduler. At which point $vendor will have no incentive to ever contribute back.

[…]

[…] GPL forces people to contribute back […] And I see the whole BPF thing as a run-around on that. '"

solarisfire, to linux
@solarisfire@mast.solarisfire.com avatar

So playing with 6.9 on an AMD 5800X3D - Started looking through the documentation and noticed that there were some Kernel flags for amd_pstate and amd_pcore. Set these to "amd_pstate=active amd_prefcore=enable" in grub and rebooted and now benchmarks are ever so slightly higher, but also geekbench reports a different clockspeed.

image/png

kernellogger, to linux
@kernellogger@fosstodon.org avatar

"'In this post, I’ll describe our track record in supporting Linux on laptops with Windows on Snapdragon and how that continues with the Snapdragon X Elite. You’ll see what’s already merged in the mainline , what’s pending and what’s on our roadmap.

https://www.qualcomm.com/developer/blog/2024/05/upstreaming-linux-kernel-support-for-the-snapdragon-x-elite

kernellogger, to linux
@kernellogger@fosstodon.org avatar

A question for experts on #git bisecting the #Linux #Kernel:

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, 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, 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.

mkwadee, to linux
@mkwadee@mastodon.org.uk avatar

Now running 6.8.9.

sima, to random
@sima@chaos.social avatar

when both the kernel implementation and the manpages are indecipherable enough that you end up writing a little test program in C ...

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • kavyap
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • tacticalgear
  • khanakhh
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • everett
  • ngwrru68w68
  • Durango
  • megavids
  • InstantRegret
  • cubers
  • GTA5RPClips
  • cisconetworking
  • ethstaker
  • osvaldo12
  • modclub
  • normalnudes
  • provamag3
  • tester
  • anitta
  • Leos
  • lostlight
  • All magazines