Exploiting a heap overflow in the FreeBSD wi-fi stack

Re:Exploiting a heap overflow in the FreeBSD wi-fi stack by naniwaduni on Friday June 17, 2022 @04:49PM (#31784177)

It's not that it isn't a fantastic design—I believe as much as the next person that UFS2 is basically best-in-class as a "traditional" dumb filesystem, and that soft updates is fundamentally a Right Approach. I wouldn't have mentioned it if I didn't!

But it's hard not to see that it's darn near barren ground for further work in filesystem design. And it's easy to see why if you scan the first paper—just look at the dependency flowcharts! Fundamentally the design is ... hard for mere mortals to work on. It's practically a miracle that it even happened once; nobody is keen on starting any new implementations.

I choose to fault filesystem implementers for not being (more) superhuman for this failing, obviously.

[ Parent | on HN ]

Re:Exploiting a heap overflow in the FreeBSD wi-fi stack by trasz on Monday June 20, 2022 @10:01AM (#31810455)

I’m not sure where the legend about softupdates being more complicated then journaling came from, but even comparing number of lines of code between SU and XFS journaling is enough to disprove it.

[ Parent | on HN ]

Re:Exploiting a heap overflow in the FreeBSD wi-fi stack by naniwaduni on Tuesday June 21, 2022 @03:16AM (#31821114)

The difficulty is not that there's too much code.

[ Parent | on HN ]

Re:Exploiting a heap overflow in the FreeBSD wi-fi stack by trasz on Tuesday June 21, 2022 @04:26AM (#31821628)

The difficulty is allegedly that the mechanism is too complex. Which seems to be just an urban legend.

[ Parent | on HN ]