Re: [PATCH] [1/2] kernel error reporting (revised)

• Next message: Dynamicfactory.com: "Your website"
• Previous message: Rusty Russell: "Re: [2.4 patch] netfilter Configure.help cleanup"
• In reply to: Jim Keniston: "Re: [PATCH] [1/2] kernel error reporting (revised)"
• Next in thread: Jim Keniston: "Re: [PATCH] [1/2] kernel error reporting (revised)"
• Reply: Jim Keniston: "Re: [PATCH] [1/2] kernel error reporting (revised)"
• Reply: Jim Keniston: "Re: [PATCH] [1/2] kernel error reporting (revised)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, 17 Jul 2003, Jim Keniston wrote:

> 3. Given the above, what should the evlog.c caller do when
> kernel_error_event_iov() returns -EINPROGRESS?
> a. Nothing. Figure the packet will probably get logged.
> b. Just to be safe, report it via printk, the same way we report dropped
> packets.
> We currently do (a). (b) would mean that every event logged from IRQ
> context would be cc-ed to printk.

I don't think this irq detection logic should be added at all here, let
the caller reschedule its logging if running in irq context.

- James

-- 
James Morris
<jmorris@intercode.com.au>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

• Next message: Dynamicfactory.com: "Your website"
• Previous message: Rusty Russell: "Re: [2.4 patch] netfilter Configure.help cleanup"
• In reply to: Jim Keniston: "Re: [PATCH] [1/2] kernel error reporting (revised)"
• Next in thread: Jim Keniston: "Re: [PATCH] [1/2] kernel error reporting (revised)"
• Reply: Jim Keniston: "Re: [PATCH] [1/2] kernel error reporting (revised)"
• Reply: Jim Keniston: "Re: [PATCH] [1/2] kernel error reporting (revised)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:31 EST