Contributed by pitrh on from the make me malloc dept.
It has been a while since I was at a hackathon, due to various reasons the last hackathon I attended was in 2008 where I did commit my implementation of malloc. During the years, various improvements to my malloc were done, both by others and myself.
But now, 8 years later I came back to to commit a important change: make malloc more friendly to multi-threaded programs. Most of the actual work had been done during the months before the hackathon, but in Cambridge I did the last checks, got my OK's and committed! Of course this is not the last commit in this areas, the current approach is simple (but effective), it can be improved after it has been proven to be stable.Apart from that I worked on some changes to newfs(8), disklabel(8) and fsck_ffs(8) to make the code to find alternative superblocks (which is used if the primary superblock is corrupted) work better. Testing that code takes quite some time, but it was good to see my manually corrupted filesystems come back to clean state.
A hackathon is not complete without pub and restaurant visits and some tourist activities, we went punting on the Cam. All in all, I had a very good time, it was really nice to meet other developers in person (again). In the futue, I hope to be able to come more often!
Thanks for the report, Otto! And thanks for continuing to provide excellent code to our favorite operating system!
(Comments are closed)
By Philipp (pb) on
Comments
By Otto Moerbeek (otto) on http://www.drijf.net
Still useful. My changes affect the case of a corrupted primary superblock while the label is still OK.
scan_ffs is used to reconstruct a lost label.
Comments
By pb (84.184.179.216) on
>
> scan_ffs is used to reconstruct a lost label
sure, I was more about the point if scan_ffs needs to be aware of additional superblocks or make use of it.
and also a happy user of scan_ffs to save the day some years back where i messed the label by dd(1) the first megabyte of the disk.