Posts
229
Following
38
Followers
266
Linux Kernel developer and maintainer
#standwithukraine πŸ‡΅πŸ‡± πŸ‡ͺπŸ‡Ί πŸ‡ΊπŸ‡¦ πŸ‡¨πŸ‡­
IRC: krzk
Kernel work related account. Other accounts of mine: @krzk@mastodon.social
@gregkh @jakub ID is needed for the press release, TicToc, Snapchat and all the hype :)
1
0
3

Krzysztof Kozlowski

Trimmed diffstat of v6.6-rc1 pull request ARM SoC changes from @arnd - the most active platforms for v6.6:

18.9% arch/arm64/boot/dts/qcom/
0.6% arch/arm/boot/dts/qcom/
1.0% drivers/soc/qcom/
...
9.6% arch/arm64/boot/dts/freescale/
3.6% arch/arm/boot/dts/nxp/imx/
0.7% arch/arm/boot/dts/nxp/ls/
0.9% arch/arm/boot/dts/nxp/mxs/
...
8.1% arch/arm/boot/dts/aspeed/
...
8.2% arch/arm64/boot/dts/ti/
0.5% arch/arm/boot/dts/ti/
...
6.6% arch/arm64/boot/dts/nvidia/
...
6.3% arch/arm64/boot/dts/rockchip/

Way to go Qualcomm SoC community!
Source: https://lore.kernel.org/all/4f60d13e-f060-491a-88c7-6f25323a48f8@app.fastmail.com/
0
3
5

Krzysztof Kozlowski

Edited 2 years ago
Corporate rules going mad: After replying to Nuvoton patches, I received now automated Out-of-office reply with "confidentiality" clause: "The privileged confidential information contained in this email is intended for use only". This is Out-of-office auto-reply, not confidential message. Get your silly systems together people...
0
0
1
@linuxplumbersconf Thanks. Good to know, although better would be to have in the Mastodon profile. It would avoid any misunderstandings.
0
0
0

Krzysztof Kozlowski

@linuxplumbersconf Hey Linux Plumbers! What is the point of the your mastodon account if you do not interact and do not respond here to any questions?
2
0
2

Krzysztof Kozlowski

Edited 2 years ago
@siddhesh_p @gregkh @sj You did not really cover the case. Either this customer had outdated kernel, thus the group should not even start creating CVE, or this kernel did not have basic fix which was fixed 7 years ago. In the latter case it would be enough just to backport the fix, not go through ridiculous CVE assignment.

Anyway, it is not really professional and what RedHat is doing with CVEs is awesome example how useless CVEs are.
1
0
2
@siddhesh_p @gregkh @sj Independently? Something fixed 7 years ago? How can you trigger such bug?

I can barely believe that any customer discovered now a bug which was fixed 7 years ago. Even if this is possible, I can hardly believe any sane person on distro side would request for CVE for such bug, instead of replying: "dude, you forgot to update your system for the last 7 years".

So no, much more likely is that RedHat was actually shipping some crazy old kernel to some people without that fix and needed CVE to justify touching this old stuff...
1
0
0

Krzysztof Kozlowski

Edited 2 years ago
@siddhesh_p @gregkh @sj Yeah, maybe they do not require CVE for every backport anymore... but then:
"Heh, apparently Red Hat recently assigned a CVE for a random kernel fix I did 7 years ago"
so not really.
https://mastodon.social/@vegard/110933167051678536
1
0
1
@yassie_j So the time came for: "Oh, you solved captcha in your first try, you clearly must be a robot. Bye.".
0
0
0
@sj I will not quote here @gregkh, but you can easily find his opinion on usefulness of CVEs (e.g. https://kernel-recipes.org/en/2019/talks/cves-are-dead-long-live-the-cve/ or current KSummit threads about vulnerabilities and security mailing lists).
1
2
1
@sj Just in case - I was not offended and I just discuss the idea of measuring anything against CVEs.
I believe that in open-source work we should not be participating in this ridiculous CVE dance, unless of course it's our profession or job. Then... well, life. :) It was my job once too.
I understand why CVEs were invented and why they are still used, even though they were effectively made pointless in last few years. However, just because some corporations believe in them ("believe" is a key word here, because their decision about CVE was based on feelings not facts), does not mean we should be endorsing this or participating in this.
1
0
1
@sj Since CVEs are basically useless, any percentage here or calling it "worst case time" is pointless. It's like measuring number of celebrities and mapping it to Linux kernel commits... Worse, it suggests that some bugs are not addressed (not fixed) or addressed slowly. This is in fact misleading.
1
0
1
@linuxplumbersconf Deadline for LPC 2023 refereed track and Kernel Summit passed two weeks ago. Any plans for sharing the schedule/program so people can do some planning?
0
0
0

Krzysztof Kozlowski

When review happens too fast:
"You replied within the same minute of me posting that patch, which is the fastest review I've had to date on an upstream kernel list. Before we continue, please verify:

[ ] I am not a robot"

From Brian Masney: https://lore.kernel.org/all/ZN5KIlI+RDu92jsi@brian-x1/
0
1
9
@monsieuricon Nice try, looks exactly like Teams background. :)
0
0
0
@marcan ... and you can poke a hornet's nest by changing the Broadcom drivers maintenance level from Supported to Odd Fixes. I don't see many reviews from existing maintainers, so I guess it fits better current state.
0
0
0
@marcan You look for developers, not maintainers. Maintainer, as name suggests, maintains the code, which does not necessarily mean active development. However, based on what you wrote, the key point is that existing maintainers did not bother to answer any questions or provide help, so most likely they do not fit the maintainer profile either...
1
0
0
@linuxplumbersconf That's cool, but when are you planning to announce accepted talks for LPC Refereed Track? I need to start planning the trip (including passport renewal which is a lot of time in my case, booking tickets and hotels etc)... not mentioning the need to actually write meaningful talk.
0
0
1
@ljs You mean sad is that maybe the president ordered the assassination? :)
1
0
1

Krzysztof Kozlowski

@kwilczynski The sales trick is neat! Let's suck out of maintainers even money, not only their time!

RE: https://fosstodon.org/users/kwilczynski/statuses/110864258072128850
0
0
1
Show older