netdev
[Top] [All Lists]

Re: [PATCH] minor socket ioctl cleanup for 2.5.30

To: willy@xxxxxxxxxx (Matthew Wilcox)
Subject: Re: [PATCH] minor socket ioctl cleanup for 2.5.30
From: kuznet@xxxxxxxxxxxxx
Date: Thu, 8 Aug 2002 21:13:15 +0400 (MSD)
Cc: davem@xxxxxxxxxx, jmorris@xxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, willy@xxxxxxxxxx
In-reply-to: <20020808170720.N24631@parcelfarce.linux.theplanet.co.uk> from "Matthew Wilcox" at Aug 8, 2 05:07:20 pm
Sender: owner-netdev@xxxxxxxxxxx
Hello!

> > Do we really want to do this?  What if some socket family either
> > doesn't want to support it or wants to handle it differently?
> 
> I rather think we do.  It's analagous to saying "What if some filesystem
> either doesn't want to support it or wants to handle it differently?"
> -- tough!  This is unix and filesystems (socket families) support this.

No, this is not true. This creepy ioctl is specific to TCP
(well, x.25 also uses SIGURG), which use kill*(sk->proc, SIGURG) directly.

Probably, it is better to move sk->proc to TCP private data,
this ioctl to tcp_ioctl(). Or... find a way to get rid of this completely,
not breaking compatibility with a few BSDish applications.

Alexey


<Prev in Thread] Current Thread [Next in Thread>