On Tue, Aug 09, 2011 at 10:29:43AM -0600, Kevin Van Maren wrote:
That code is unchanged in 1.8.6.
The two relevant patches for 1.8 are the following:
http://review.whamcloud.com/#change,457
http://review.whamcloud.com/#change,506
Both patches are included in 1.8.6-wc1 and waiting for landing
chas williams - CONTRACTOR wrote:
On Mon, 08 Aug 2011 12:03:25 -0400
chas williams - CONTRACTOR c...@cmf.nrl.navy.mil wrote:
later mdc_exit_request() finds this mcw by iterating the list.
seeing as mcw was allocated on the stack, i dont think you can do this.
mcw might have been reused
On Tue, 09 Aug 2011 10:29:43 -0600
Kevin Van Maren kevin.van.ma...@oracle.com wrote:
chas williams - CONTRACTOR wrote:
nevermind. i see this has been fixed in later releases apparently (i
was looking at 1.8.5). if l_wait_event() returns early (like
from being interrupted)
On 2011-08-08, at 10:03 AM, chas williams - CONTRACTOR wrote:
we have seen a few crashes that look like:
[250696.381575] RIP: 0010:[a0a1f9e4] [a0a1f9e4]
mdc_exit_request+0x74/0xb0 [mdc]
...
[250696.381575] Call Trace:
[250696.381575] [a0a25042]
On Mon, 08 Aug 2011 12:03:25 -0400
chas williams - CONTRACTOR c...@cmf.nrl.navy.mil wrote:
later mdc_exit_request() finds this mcw by iterating the list.
seeing as mcw was allocated on the stack, i dont think you can do this.
mcw might have been reused by the time mdc_exit_request() gets
