# Google SoC lwIP Report Week 12

DevFeed: [Google SoC lwIP Report Week 12](<https://devfeed.tech/articles/google-soc-lwip-report-week-12-32787.md>)

Original publisher: [Read original article](<https://reactos.org/blogs/google-soc-lwip-report-week-12/>)

Published: 2016-08-15T00:00:00Z

Content type: article

Language: en

Sources: [Front Page on ReactOS Website](<https://devfeed.tech/sources/front-page-on-reactos-website.md>)

Topics: [lwIP](<https://devfeed.tech/topics/lwip.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Deadlock](<https://devfeed.tech/topics/deadlock.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [concurrency](<https://devfeed.tech/tags/concurrency.md>), [free](<https://devfeed.tech/tags/free.md>), [google](<https://devfeed.tech/tags/google.md>), [lwip](<https://devfeed.tech/tags/lwip.md>), [multithreading](<https://devfeed.tech/tags/multithreading.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [os](<https://devfeed.tech/tags/os.md>), [react](<https://devfeed.tech/tags/react.md>), [reactos](<https://devfeed.tech/tags/reactos.md>), [tcp](<https://devfeed.tech/tags/tcp.md>), [thread](<https://devfeed.tech/tags/thread.md>), [win32](<https://devfeed.tech/tags/win32.md>), [winapi](<https://devfeed.tech/tags/winapi.md>)

## AI overview

A week 12 progress report on rewriting a driver to address lwIP's thread-safety problems. The author redesigns mutex usage to manage protocol control block lifetimes while balancing safe pointer access against performance and deadlock risks.

## Source excerpt

In week 10, I had completed a major rewrite of my driver. In week 11, I dove into the problem of lwIP not being thread-safe once again. While I was able to deal with most of the individual bugs that kept popping up, each one was taking me more time to solve due to the haphazard nature of my previous fixes. At the beginning of last week, it was quickly becoming more apparent that I would need to rework most of my code once again if I wanted to have any hope of circumventing the multithreeading issue once and for all.