[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100729010607.GB13088@nowhere>
Date: Thu, 29 Jul 2010 03:06:08 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Jason Wessel <jason.wessel@...driver.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, kgdb-bugreport@...ts.sourceforge.net
Subject: Re: [GIT PULL] kgdb regression fixes for 2.6.35-rc5
On Wed, Jul 28, 2010 at 07:14:42PM -0500, Jason Wessel wrote:
> On 07/28/2010 04:26 PM, Linus Torvalds wrote:
> > On Wed, Jul 28, 2010 at 2:17 PM, Frederic Weisbecker <fweisbec@...il.com> wrote:
> >> I'm sorry I spot it a bit late.
> >> There is a little issue in this patch, irqs won't
> >> be restored:
> >>
> >> @@ -588,9 +588,10 @@ int kgdb_ll_trap(int cmd, const char *str,
> >> if (!kgdb_io_module_registered)
> >> return NOTIFY_DONE;
> >>
> >> + local_irq_save(flags);
> >> return __kgdb_notify(&args, cmd);
> >> + local_irq_restore(flags);
> >> }
> >
> > Yeah, that's obviously crap. I also wonder why __kgdb_notify messes up
> > the flags to begin with.
> >
>
> This should not be needed as the irqs should already be off while in the overflow handler.
Interrupts are not disabled in the debug exception handler.
I'm not sure what would be the state of dr6 if a nested debug exception
would happen while do_debug() is interrupted.
Perhaps the previous dr6 value is dropped. Intel manuals don't seem to say anything
about that.
Anyway that's a separate issue. The current patch fixes a regression and
it looks good.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists