DragonFly BSD
DragonFly bugs List (threaded) for 2004-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: ifconfig wepkey problem

From: Rob Schulhof <rrs@xxxxxxx>
Date: Tue, 23 Mar 2004 00:00:53 -0800 (PST)


  I'm having the same problem with SIOCS80211 ioctl's to wi.  I tracked it
down to the commit on ../kern/uipc_mgs.c and ../sys/socketopts.h on
March19th, "Make ALWAYS_MSG the default".  When I back out those changes,
then the ioctl calls succeed.

 It's odd because the with ALWAYS_MSG, the arguments  to the in_control
call are identical, but when in_control calls wi_ioctl, the stack seems to
get corrupted.

Partial trace...

With messaging:

wi_ioctl(cb64c8b8, 801c69ea, dcf95b74, b0, 0)
. ..

Without messaging:

wi_ioctl(cb64c8b8, 801c69ea, dcf95b74, dcf95aec, 1)
. ..

Hope that helps...

On Mon, 22 Mar 2004, Matthew Dillon wrote:

> From: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
> Subject: Re: ifconfig wepkey problem
> Date: Mon, 22 Mar 2004 21:45:12 -0800 (PST)
> To: bugs@xxxxxxxxxxxxxxxxxxxxxxx
> :Somewhere from  Mar 16 to Mar 20, "ifconfig wi0 wepkey ..." has broken, at
> :least here on my machine.
> :It seems to be a kernel problem, as booting an old kernel still works - even
> :with new ifconfig.
> :Some printfs showed, that copyin at sys/dev/netif/if_wi.c:1926 is returning
> :EFAULT for some reason.
> :Any ideas?
> :
> :Thanks,
> :Johannes
>     I don't have a setup that can easily test this, but the very first thing
>     you should do is make sure that your world and your kernel are both up
>     to date.
> 					-Matt
> 					Matthew Dillon
> 					<dillon@xxxxxxxxxxxxx>

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]