Re:Google Proposes New Mseal() Memory Sealing Syscall for Linux
by orangepurple on Tuesday October 17, 2023 @11:04AM
(#37916274)
Matthew Wilcox dunked on it savagely too in https://lore.kernel.org/lkml/ZS6Ea4%[email protected]...
[ Parent
| on HN ]
Re:Google Proposes New Mseal() Memory Sealing Syscall for Linux
by cozzyd on Tuesday October 17, 2023 @03:08PM
(#37920078)
And to add to the submitter's rough day, Theo de Raadt has joined the conversation. https://lore.kernel.org/lkml/[email protected]...
mseal() is a clone of mimmutable(2), but with an extremely over-complicated API based upon dubious arguments.
Re:Google Proposes New Mseal() Memory Sealing Syscall for Linux
by alain94040 on Tuesday October 17, 2023 @03:41PM
(#37920524)
And notice how his comment is constructive despite the lack of name calling or abusive language.
Re:Google Proposes New Mseal() Memory Sealing Syscall for Linux
by withinboredom on Tuesday October 17, 2023 @04:33PM
(#37921184)
I'd love to see the name calling. I've read it several times now. I see him saying that this random patch out of the blue, without any discussion, doesn't follow any of the guidelines to submit a kernel patch, doesn't make any sense (in fact, seems to reimplement things already in the kernel), and isn't being accepted without a significant rework.
He never, ever, once, demeans the person who submitted the patch or shows a pattern of abuse to that person -- if you look up the definition of "abusive" you'll see it says (emphasis mine): "extremely offensive AND insulting". While the text may be offensive (to some, to my ex-military eyes, this is being nice), he never once insulted the author.