Attention is currently required from: jolly, pespin.

laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/36121?usp=email )

Change subject: osmo_io: Assign const name when stealing TX msg from iofd ctx ......................................................................

Patch Set 1: Code-Review+1

(1 comment)

File src/core/osmo_io.c:

https://gerrit.osmocom.org/c/libosmocore/+/36121/comment/cf4b934b_354b7230 PS1, Line 339: talloc_set_name(msg, "osmo_io_rx_msgb");

Can you point to the place which is setting this name so I can understand what's going on?

It happens at time the msgb is allocated, where as name we use a pointer to the (dynamically allocated) name of the iofd. However, the iofd might be closed befoere the msgb's is released (think of queues, ...) and in that case a talloc report would try to print a string at an already-free'd address.