Re: possible BUG while doing gpg --gen-key

From: Andrew Morton
Date: Wed Sep 05 2007 - 12:59:59 EST


> On Wed, 05 Sep 2007 18:49:39 +0200 Udo van den Heuvel <udovdh@xxxxxxxxx> wrote:
> Andrew Morton wrote:
> >> On Sun, 2 Sep 2007 04:55:20 -0700 Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> >>> On Sat, 25 Aug 2007 14:57:17 +0200 Udo van den Heuvel <udovdh@xxxxxxxxx> wrote:
> >>> Udo van den Heuvel wrote:
> >>>> Now it works:
> >>> Stranger even:
> >>>
> >>> With audio-entropyd, rngd active and the netdev-random patch working I
> >>> cannot reproduce the crash. Even after a fresh boot.
> >> It would really help if your oops stack trace wasn't truncated. Can you
> >> see if you can generate a complete one using a recent kernel? Enabling
> >> CONFIG_FRAME_POINTER and disabling CONFIG_4K_STACKS might help in this.
> >>
> >
> > So... what's happening here? Did the trail go cold?
>
> Well, I just rebooted the box for an other problem (see
> http://bugzilla.kernel.org/show_bug.cgi?id=8377 for details)

erp, the bug report from hell #2.

> and did a
> fresh try:
>
> strace gpg --gen-key 2> ~/gpg.txt
>
> Oddly enough the action completes successfully. This is with both
> audio-entropyd and rngd running and netdev-random patch in the kernel.
> The very same thing triggered the bug without problem before trying with
> the mentioned deamons stopped.
> Now even doing rm -rf .gnupg/ does not help in reproducing.
>
> So yes, all is OK, and no, I don't know why.

oh well, thanks. If there's really a bug in there then someone will
reliably hit it one day. Thanks for following up.

-
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/