mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "Guillaume Chazarain" <guichaz@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Laszlo Attila Toth" <panther@balabit.hu>,
	"David Miller" <davem@davemloft.net>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.25-rc2: wpa_supplicant BUGs kernel in rwlock recursion
Date: Sun, 17 Feb 2008 01:17:31 +0100	[thread overview]
Message-ID: <5a4c581d0802161617h284574aar7d4d72e87ecbba49@mail.gmail.com> (raw)
In-Reply-To: <3d8471ca0802161518h3fe87f5encc83e7cc976ccef9@mail.gmail.com>

On Feb 17, 2008 12:18 AM, Guillaume Chazarain <guichaz@gmail.com> wrote:
> On Feb 16, 2008 6:14 PM, Alessandro Suardi <alessandro.suardi@gmail.com> wrote:
> > Feb 16 16:51:49 sandman kernel: BUG: rwlock recursion on CPU#0,
>
> Same thing here, bisected it to:
>
> commit 45b503548210fe6f23e92b856421c2a3f05fd034
> Author: Laszlo Attila Toth <panther <at> balabit.hu>
> Date:   Tue Feb 12 22:42:09 2008 -0800
>
>     [RTNETLINK]: Send a single notification on device state changes.
>
> The revert applies cleanly and fixes the problem.
> Rafael has more details in http://lkml.org/lkml/2008/2/15/542.

Thanks Guillaume,

  I can confirm that the revert of the rtnetlink.c changes does
  indeed fix the problem for me.

Second time in a couple of week I hit the same bugs as Rafael,
 will keep an eye on his new findings ;)

--alessandro

 "We act as though comfort and luxury were the chief requirements
   of life, when all that we need to make us really happy is
   something to be enthusiastic about."

   (Charles Kingsley)

      reply	other threads:[~2008-02-17  0:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 17:14 Alessandro Suardi
2008-02-16 18:27 ` Alessandro Suardi
2008-02-16 23:18 ` Guillaume Chazarain
2008-02-17  0:17   ` Alessandro Suardi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5a4c581d0802161617h284574aar7d4d72e87ecbba49@mail.gmail.com \
    --to=alessandro.suardi@gmail.com \
    --cc=davem@davemloft.net \
    --cc=guichaz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=panther@balabit.hu \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®