Re: [RFC PATCH 3/6] mm: nommu: fix an issue on map request to /dev/zero
"Lorenzo Stoakes (ARM)" <[email protected]>
| Newsgroups | gmane.linux.file-systems,gmane.linux.kernel.mm |
|---|---|
| Message-ID | <an3COKVbgQKdY52d@lucifer> |
On Thu, Aug 13, 2026 at 09:43:37PM +0900, Daniel Palmer wrote: > Hi Greg, > > On Thu, 13 Aug 2026 at 21:26, Greg Kroah-Hartman > <[email protected]> wrote: > > > Given the age of this issue, I don't think anyone uses no-mmu systems > > anymore :( > > There are a few of us using it for hobby stuff[0][1] and there are > apparently people using it for actual commercial stuff. > There was a session about this at LPC 2025... > > One of the big problems for nommu seems to be that everyone is > convinced it is completely unused and totally broken. :) No, the issue is that nobody seems to do any testing or contribute any code aside from at least Hajime (thanks Haijme :), and possibly others (forgive me if I am missing people's names here!) There's been situtions where nommu has been broken for a year and _nobody noticed_. And yet whenever nommu comes up people always seem to pop up and say how important it is, then mention a talk etc. Well if it's important, test it. Test the tip kernel. Report bugs. Contribute code. Any or all of it :) Meanwhile we in mm have to _constantly_ fix stuff up in nommu because it's a total mess and has real maintenance overhead. Having to account for legacy systems that make no sense in 2026 when you're trying to make improvements to systems people use, or not being able to do certain things, really grates after a while. I mean if you don't believe me git log mm/nommu.c. This overhead reason is why I now co-maintain it. So I'm honestly a bit tired of people popping up when the whole 'why nommu' thing comes up, then disappearing when there's work to be done. In general - it's not really for those not doing the work to dictate terms to those who do, IMO. So while I appreciate you confirming there are users (yes we know :) frankly that's not the question. The question is - why isn't a downstream kernel enough for you? Last time I brought this up I basically got radio silence, a couple times before that I was told 'nommu has no maintenance overhead and is perfectly good code and we have products' by somebody who contributes little to nothing in terms of code and nothing no testing. So bah humbug. AFAIC it needs to go and we should never have allowed risc v to add a new nommu arch. > > Cheers, > > Daniel > > 0 - Really good example(s) of the 68000 port > https://github.com/crmaykish/mackerel-68k > 1 - https://github.com/LinuxMD/linuxmd my version of the 68000 code > with devicetree like those fancy ARM things running on a sega > megadrive. -- Cheers, Lorenzo