Re:Google Proposes New Mseal() Memory Sealing Syscall for Linux
by dbsmith83 on Tuesday October 17, 2023 @10:40AM
(#37915861)
Your review doesn't take the time to explain why something is a bad idea though. I didn't think his tone was that bad. I think it depends on how you imagine the conversation in real life.
[ Parent
| on HN ]
Re:Google Proposes New Mseal() Memory Sealing Syscall for Linux
by eviks on Tuesday October 17, 2023 @11:31AM
(#37916717)
Where is "why" in this repetitive review? Also, what is the values of bluntly repeating in a more aggressive style vs bluntly saying the same thing once in a more professional manner while also explaining the reason (lack of details)
> First off, the simple stuff: the commit messages are worthless. Having
check seal for mmap(2)
as the commit message is not even remotely acceptable, to pick one
random example from the series (7/8).
Re:Google Proposes New Mseal() Memory Sealing Syscall for Linux
by dbsmith83 on Tuesday October 17, 2023 @05:26PM
(#37921803)
Try reading the rest of the review and you will see multiple explanations for why things are not a good idea. I don't even think your cherry picked example is that repetitive. It sounds like a normal conversation to me.
Re:Google Proposes New Mseal() Memory Sealing Syscall for Linux
by eviks on Wednesday October 18, 2023 @01:20AM
(#37925073)
I've read the rest of the review, but "cherry picking" another example wouldn't help when you ignore the issues of the first one and have to add qualifiers (yeah, it's not "that repetitive", it's just repetitive)