Re: [Linux-cachefs] 3.0.3 64-bit Crash running fscache/cachefilesd

[Mark Moseley]

On Thu, Oct 20, 2011 at 4:05 PM, David Howells <dhowells@xxxxxxxxxx> wrote:
> Mark Moseley <moseleymark@xxxxxxxxx> wrote:
>
>> Nope, it wasn't. I had to reboot it back into the previous kernel for
>> the weekend. I got a couple of oops though in the past 12 hours. I
>> unfortunately hadn't fired up that dump again though (I have now and
>> will send a new dump when I get another crash)
>
> Okay.  I'm away next week at a pair of conferences, but I'll try and have a
> look.
>
>> [67666.389761] kernel BUG at fs/fscache/operation.c:426!
>
> Can you have a look what's on line 426 for you, please?  It's a blank line in
> my kernel.  I think I've managed to rearrange my patches to muck the ordering
> up.

Here's line 426 with some context:


418         _debug("PUT OP");
419
420         if (op->state != FSCACHE_OP_ST_COMPLETE &&
421             op->state != FSCACHE_OP_ST_CANCELLED)
422                 printk("FS-Cache: Asserting on %s operation\n",
423                        fscache_op_names[op->name]);
424
425         ASSERTIFCMP(op->state != FSCACHE_OP_ST_COMPLETE,
426                     op->state, ==, FSCACHE_OP_ST_CANCELLED);
427         op->state = FSCACHE_OP_ST_DEAD;
428
429         fscache_stat(&fscache_n_op_release);
430
431         if (op->release) {
432                 op->release(op);
433                 op->release = NULL;
434         }
435
436         object = op->object;
437
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/