2 ms·

see also: https://lore.kernel.org/all/d9802b6a-949b-b327-c4a6-3dbca485ec20@gmx.com/ https://lore.kernel.org/all/d9802b6a-949b-b327-c4a6-3dbca485... https://lo

• atmosx 4y ago
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=macOS+ https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=macOS+ So? What’s the point here?
  • rrss 4y ago
    I linked threads on LKML that are directly relevant to this subject, about how this (system becomes nonresponsive under memory pressure) is a real problem that people really experience, with a lot of people agreeing that it is a problem and suggesting various mitigations. Most of those ideas presuppose that memory pressure leads to stalls and are about figuring out how to detect when the system is stalled and making no progress and killing processes after it has gone on for a while (often with userspace daemons). I think MGLRU is maybe getting merged in linux 6.x and will hopefully help avoid the stalls. you linked a list of all CVEs in macOS. I don't see how this is relevant at all.
    • atmosx 4y ago
      > [...] is a real problem that people really experience, with a lot of people agreeing that it is a problem and suggesting various mitigations [...] tl;dr: I believe you are overblowing the importance of the bugs. In the bigger scheme of things they're more likely inconsequential. (see my other reply for more)
      • rrss 4y ago
        These links are not just two simple bugs. The first link is a report that the system becomes nonresponsive under memory pressure and a discussion of that report. In that thread, there was not really any agreement about whether this was a bug, let alone what the bug was, or what the fix would be. The second wasn’t a bug at all, it was a patch proposed set of knobs to allow users to avoid the problem.