top(1) loses process user time count when threads end

2011-08-05 Thread Yuri
I have the process that first runs in 3 threads but later two active threads exit. top(1) shows this moment this way (1 sec intervals): 30833 yuri3 760 4729M 4225M nanslp 4 0:32 88.62% app 30833 yuri3 760 4729M 4225M nanslp 6 0:34 90.92% app 30833 yuri

Re: module_register_init fails, but driver is still loaded?

2011-08-05 Thread Andriy Gapon
on 05/08/2011 18:21 Sergey Kandaurov said the following: > On 4 August 2011 20:23, Garrett Cooper wrote: >> Hi hackers, >>I noticed that if anything fails while initializing a driver, the >> driver stays attached to the kernel as a module instead of being >> kicked when all references to the d

Re: module_register_init fails, but driver is still loaded?

2011-08-05 Thread Sergey Kandaurov
On 4 August 2011 20:23, Garrett Cooper wrote: > Hi hackers, >    I noticed that if anything fails while initializing a driver, the > driver stays attached to the kernel as a module instead of being > kicked when all references to the driver go to 0. Is this desired > behavior (it doesn't seem like

Re: cam / ata timeout limited to 2147 due to overflow bug?

2011-08-05 Thread Eygene Ryabinkin
Fri, Aug 05, 2011 at 10:59:43AM +0100, Steven Hartland wrote: > I've tried the patch and it a few cut and paste errors, which I've fixed, Thanks for spotting that! > and confirmed it works as expected, so thanks for that :) > > There's also a load more drivers with the same issue so I've gone th

Re: cam / ata timeout limited to 2147 due to overflow bug?

2011-08-05 Thread Steven Hartland
Fri, Aug 05, 2011 at 12:02:19AM +0100, Steven Hartland wrote: So I suspect that this is what's happening resulting in an extremely small timeout instead of a large one. Now I know that passed in value to the timeout is seconds * 1000 so we should be seeing 2148000 for ccb->ccb_h.timeout now multi

Re: cam / ata timeout limited to 2147 due to overflow bug?

2011-08-05 Thread Eygene Ryabinkin
Steven, good day. Fri, Aug 05, 2011 at 12:02:19AM +0100, Steven Hartland wrote: > So I suspect that this is what's happening resulting in an extremely > small timeout instead of a large one. Now I know that passed in value > to the timeout is seconds * 1000 so we should be seeing 2148000 > for ccb

Re: cam / ata timeout limited to 2147 due to overflow bug?

2011-08-05 Thread Kostik Belousov
On Fri, Aug 05, 2011 at 12:02:19AM +0100, Steven Hartland wrote: > I'm working on adding security methods to camcontrol and have > come up against a strange issue. It seems that the timeout > value for cam, at least on ata (ahci), is limited to less than > 2148 seconds. > > This can be seen by run