Hacker Newsnew | past | comments | ask | show | jobs | submit | wavemode's commentslogin

> (Some have already landed.)

Do you have links to some of these?


Accepted by maintainers so far:

In mainline:

ext4, xattr cache: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

ocfs2, cluster accounting: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

Taken into Jan Kara's filesystem tree this week, all isofs:

An out-of-bounds read in the multi-extent directory walk: https://lore.kernel.org/all/20260923153220.777907-1-matthias...

A hang in a fix Jan had just written, which he is folding into it: https://lore.kernel.org/all/20260923153134.771632-1-matthias...

A bug Jan fixed himself after my report: https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-f...

Sashiko, the LLM patch reviewer that now comments on kernel mailing lists, merged a fix of mine: https://github.com/sashiko-dev/sashiko/pull/556 (a patch that contained one of its prompt placeholders as text had it replaced).

Not accepted yet, but I think interesting:

libata, reviewed by the maintainer but not applied yet: a faulty ATAPI device could make the kernel write past its sense buffer. https://lore.kernel.org/all/20260922182655.2423663-1-matthia...

e2fsck, the repair tool, could deadlock on some corrupt images and hang forever. Reviewed by Darrick Wong. https://lore.kernel.org/all/20260922110435.1528332-1-matthia...

ntfs: a crafted image makes mount hang forever, because the mount waits on a lock its own read already holds. One of the maintainers asked for a wider fix, which I am testing. https://lore.kernel.org/all/20260922153931.1976405-1-matthia...

Sashiko was reviewing ext4 patches against a tree from 2020: https://github.com/sashiko-dev/sashiko/issues/559, fix in https://github.com/sashiko-dev/sashiko/pull/560, plus a one-line MAINTAINERS patch naming the ext4 branch, which Jan acked: https://lore.kernel.org/all/20260923101749.3505886-1-matthia...

Not posted yet, still being reviewed on my side:

ntfs: writing to a compressed file on a volume whose free space is fragmented silently overwrote clusters belonging to other files. write() reported success; the damage only showed after a remount.

ntfs: reads of a damaged file could return zeros for data that is on disk, and writes to it could be dropped.

Sashiko: on its Claude, Vertex and Gemini backends, a connection that drops mid-response is treated as a permanent error rather than retried.

The rest, mostly more ntfs, are still in review or on my desk. Not all of these came from that first night; the ext4 and ocfs2 ones are older.

I also have a lot of bcachefs contributions, but that's because I'm actively using that filesystem on my desktop; instead of a pure fuzzing run.


You can set up automation and/or configuration such that changes to the docs folder don't require code review.

That explanation doesn't make sense. If the point is anonymity, why not just AI generate the students entirely? They AI-generated the girl on the right in her entirety, so capability clearly isn't the problem. And the guy in the middle is still very much recognizable.

I don't understand what you mean? For me, it appears all 3 students have been changed. The 3rd student is changed into a black female. I am not doubting they want to inject diversity (although i didnt say it above) my contention is they likely view the original as a blank background, which they inserted 3 "new" anonymized students into. Its not that they turned 1 person "black", its that they changed ALL 3 PEOPLE entirely

You think the first 2 students were changed as significantly as the 3rd?

The first 2 are still recognizable, the third is not.


Given how little the two students on the left changed, I highly doubt the AI made a creative decision to completely randomize only the student on the right. I think it's more likely that they did it in two steps: tweak the faces, and replace the student on the right.

But what if (as the commenter you're responding to stated) someone believes that AI will have a positive effect on humanity? Is it morally wrong for them to disagree with your view?

I personally think taking part in an industry that openly and casually argues that the insane losses being racked up are fully affordable as long as people are permanently taken out of the workforce is immoral, yes. Pan-industrial job loss is a harm.

Leaning on "I did what I thought was right for humanity" while not addressing the harms to people along the way is not moral.

Other people can draw their own conclusions.


Personally, I don't know if AI will be a net-positive or net-negative for mankind, but if it's negative it's overwhelmingly likely that it will be due to environmental and/or energy usage concerns. That is, we ought to limit the power consumption and force companies to work more efficiently and sustainably, rather than limiting the research itself.

Arguments as old as time that a new form of automation will put people out of jobs are just not compelling to me, I'm sorry. I also don't believe it's likely that LLMs will ever be ASI, nor ever evil and sentient.


> Arguments as old as time that a new form of automation will put people out of jobs are just not compelling to me, I'm sorry. I also don't believe it's likely that LLMs will ever be ASI, nor ever evil and sentient.

I didn't make either of these arguments.

I was literally talking about what "bad" means, contextually, in the context of a job, responding to the idea that most people just don't see "good/bad" issues in their jobs. When almost all of us do, in fact, see harms we should reduce. Just often smaller harms.

One of the problems in the tech industry is that people always say "well sure, but…" and then try to expand the scenario to an amoral Thanos-level so they can wriggle off what might actually in many cases be much more personal, contextually obvious hooks.

"It happens, I shouldn't worry about my part in it" is not a moral framework.


They're not challenging that at all. The time limit makes it a game rather than an experiment. "You can't tell it's AI if you don't have enough time to examine the details" is not exactly a compelling claim...

When I was doing arbitrage and bonus farming, the process often involved wagering both sides of a bet on different sportsbooks. Result being that my DraftKings account was eventually down thousands of dollars over its lifetime.

So of course... they emailed me offering access to a VIP bonus program! To get in I just needed to keep betting as much as possible. Such nice people.


over 100K lines of code materialized over the course of 3 weeks and is full of em dashes. I think we can reasonably assume here...

You can, since the contracts are transferrable. But SFOFC is not an exchange so you'd have to find a buyer yourself.

well, I just emailed the project just to see if they're aware of it

part of me feels like this is most likely a defunct wallet and nobody involved with the project has the keys anymore


If so they better take it off their site footer so donations don’t get wasted. Let us know if they respond

Many commenters seem to think the author is saying that we should stop caring about uptime, when what he's really saying is that we should be reporting time (i.e. number of hours down in the last month) rather than just reporting an opaque percentage that hides the problem.

I want a good chart not a percentage, because one service being down at 2 am for 3 hours is not the same as another service being down for 45 minutes during my peak hours of productivity.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: