https://mp.weixin.qq.com/s/G0CofYHly1uVekuE3fpywg 泪目,开源精神
❤4

Channel
@k77777777777k
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
167subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003461337233 |
|---|---|
| Type | Channel |
| Username | @k77777777777k |
| Created | Between 1 November 2025 and 26 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 5 times, most recently 19 September 2026 |
| On Telegram | t.me/k77777777777k |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 10:16 | 167 | +1 |
| 15 Aug 2026, 01:25 | 166 | -1 |
| 8 Aug 2026, 15:46 | 167 | no change |
| 6 Aug 2026, 22:03 | 167 | first reading |
20 posts held, back to 26 February 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
49 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 32.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 16 | 32.7% | |
| 🔥 | 8 | 16.3% | |
| 😁 | 8 | 16.3% | |
| 🫡 | 7 | 14.3% | |
| ❤ | 6 | 12.2% | |
| 👏 | 4 | 8.16% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 11 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 49 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 26 February 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
https://mp.weixin.qq.com/s/G0CofYHly1uVekuE3fpywg 泪目,开源精神
❤4
[LLM 01] 你打的字,大模型一个都不看 https://mp.weixin.qq.com/s/vFbr3fKHjbH6GktQm5hLzQ
prediction = compression 😄
This is nothing to vibe-code. This needs a real expert. 你品,细品
Reviewer +3
🔥5❤1
刚看了个 kmemleak 的 soft lockup RFC [1]。大概就是一个内核线程在 RCU 里扫所有 task stack,线程一多,CPU 就可能被它一直占着,最后 watchdog 报 soft lockup。 感觉这种桃子应该不少。内核里有很多后台线程会扫 task、扫全局链表、扫各种对象,只要循环够长,中间又没法直接睡一下,就可能有类似问题。 可以参考 hung task 那边的 pattern:先把当前游标 pin 住,临时退出 RCU,cond_resched() 一下,再重新进 RCU;如果游标还活着就继续扫,不活了就停掉这一轮。 有空可以去翻翻,搞不好还能捡几个。 Good luck ~ [1] https://lore.kernel.org/linux-mm/[email protected]/
👍3❤1
以后报 hung task 的时候,大家顺手看下CONFIG_DETECT_HUNG_TASK_BLOCKER=y 有没有开。这个一般默认开,但不少 report 的 config 都没开启,为什么!!! 目前能识别 mutex / sem / rwsem 这几类,命中的话能把likely owner / last holder 打出来。就算没法一步到 root cause,也能少猜很多。 https://lore.kernel.org/linux-mm/[email protected]/ https://lore.kernel.org/linux-mm/[email protected]/
👍1
Loop is power 预设 BUG 存在,怀疑、验证、筛选,循环往复 效果远超出想象 。。。No bug, no stop
LPE 昙花四现:Copy Fail、Dirty Frag、Fragnesia、PinTheft PinTheft 似乎威力不大,我们 CONFIG_RDS 都没有开启,你们呢? https://www.openwall.com/lists/oss-security/2026/05/19/6
You gave me a u32. I gave you root. (io_uring ZCRX freelist LPE) https://ze3tar.github.io/post-zcrx.html 又来一个 LPE ??? 标题看着很帅,实则 AI slop it is ... 两位大佬直接盖棺定论: Jens Axboe (iouring Maintainer) > If you already have CAP_SYS_ADMIN, what is the point? Solar Designer (Openwall) > That is indeed ridiculous, and puts everything else in this report in (greater) doubt. https://seclists.org/oss-sec/2026/q2/438
😁5
Subject: Dirty Frag: Universal Linux LPE https://www.openwall.com/lists/oss-security/2026/05/07/8 又来???
😁3
David H 正式接管 MM 子系统[1],倒计时开启 🎉🎉🎉 第一时间就给他发了祝福,他也坦言挑战不小,但同样很期待接下来这一年。一个旧时代的结束,也意味着一个新时代的开始,感谢 Andrew 这些年的辛苦付出,MM 会越来越好! [1] https://lore.kernel.org/linux-mm/[email protected]/
🔥3👍1
Showing the 12 most recent of 20 posts we hold for @k77777777777k. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 21 August 2026 — this entry's latest reading, not the date you are reading this.
“Kernel Jungler #1” (@k77777777777k), 167 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/k77777777777k.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.