netdev - On managing socket's error queue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <68ff91a70ff77f85c655b4de4d450b2172ef802a.camel@yandex.ru>
Date: Tue, 20 Jan 2026 19:25:54 +0300
From: Dmitry Antipov <dmantipov@...dex.ru>
To: netdev@...r.kernel.org
Subject: On managing socket's error queue

Is there a common design pattern to manage 'sk_error_queue' of 'struct sock'?
I've found that some socket destructors (say, 'iucv_sock_destruct()') do
'skb_queue_purge(&sk->sk_error_queue)' but (most of the?) others do not,
and it would be very helpful to know why it is so.

This question comes from https://syzkaller.appspot.com/bug?extid=7ff4013eabad1407b70a
where the trivial patch (hopefully) fixes a memory leak.

Dmitry