netdev - Re: [PATCH 0/2] Clean up owner field in sock_lock

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>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070912.014546.78722298.davem@davemloft.net>
Date:	Wed, 12 Sep 2007 01:45:46 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jheffner@....edu
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 0/2] Clean up owner field in sock_lock_t

From: John Heffner <jheffner@....edu>
Date: Tue, 11 Sep 2007 14:01:31 -0400

> I don't know why the owner field is a (struct sock_iocb *).  I'm assuming
> it's historical.  Can someone check this out?  Did I miss some alternate
> usage?

AIO used it somehow in net/socket.c and I believe there was some
intention to access this sock_iocb deeper in the call chain.

None of that materialized of course :)

> These patches are against net-2.6.24.

Thanks a lot, I'll add these patches.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html