[lkml]   [2002]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] IBM Lanstreamer bugfixes
  Sorry, this mail was sent acidentally...  but since its out here...

> 5 & 11) Nope, I had not read Doc/networking/netdevices.txt, so I have a
question. What does being inside rtnl_lock() imply other than the sleep
> issues?
> The calls to cli() and save_flags() were wrong from the beginning.
They were imported by the last maintainer since this driver is a modified
version > of the olympic token ring driver. The current spin_lock() and
spin_unlock() calls protect the srb_queued variable. If we were to set it
to one and then > get interrupted before we actually write() to the srb,
the interrupt function will try to service whatever junk happens to be in
the srb. If going into the
> interrupt function is covered by rtnl_lock(), this would be covered, but
I guess its not (?)....

actually I should be using spin_lock_irqsave() in open() and close()
since the lock is taken inside the interrupt function, no?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:15    [W:0.043 / U:7.400 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site