| To: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Wrong UIDs reported in /proc/net/tcp |
| From: | "Chad N. Tindel" <chad@xxxxxxxxxx> |
| Date: | Fri, 19 Nov 2004 16:01:56 -0500 |
| Cc: | netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx |
| In-reply-to: | <20041118210307.GA9557@xxxxxxxxxxxxxxxxxxx> |
| References: | <20041109205358.GA64015@xxxxxxxxxxxxxx> <E1CRdBr-0001P2-00@xxxxxxxxxxxxxxxxxxxxxxxx> <20041118190257.GA7084@xxxxxxxxxxxxxx> <20041118210307.GA9557@xxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
> > OK, so just out of sheer morbid curiousity, I added an ioctl which will > > accept 4 parameters (the address/port pairs), and will return the user id > > associated with that socket. I also changed pidentd to call this ioctl > > instead of looking at /proc/net/tcp. This should theoretically get rid > > of all race conditions. > > Please show us the code of your ioctl. Hi- I found the problem... it was a bug in my pidentd changes where I wasn't properly handling an ioctl failure. So, using an ioctl to do a direct hash table lookup makes the userid mismatches go away. We've been running tests for 12 hours without any failures. > Have you tried netlink yet? Does it exhibit the same problem? Only so many test systems to go around. ;-) Will start these tests tonight and report back. Chad |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] MII bus API for PHY devices, Andy Fleming |
|---|---|
| Next by Date: | Re: [PATCH] MII bus API for PHY devices, Andy Fleming |
| Previous by Thread: | Re: Wrong UIDs reported in /proc/net/tcp, Herbert Xu |
| Next by Thread: | Re: Wrong UIDs reported in /proc/net/tcp, Henrik Nordstrom |
| Indexes: | [Date] [Thread] [Top] [All Lists] |