public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Jiri Kosina <jkosina@suse.cz>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	WANG Cong <xiyou.wangcong@gmail.com>, Tejun Heo <tj@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] base firmware: Fix BUG from sysfs attributes change in commit a2db6842873c8e5a70652f278d469128cb52db70
Date: Sun, 14 Mar 2010 11:30:48 -0700	[thread overview]
Message-ID: <m11vfmzrfr.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <20100314181131.GC28359@suse.de> (Greg KH's message of "Sun\, 14 Mar 2010 11\:11\:31 -0700")

Greg KH <gregkh@suse.de> writes:

> On Sat, Mar 13, 2010 at 09:46:46PM -0800, Linus Torvalds wrote:
>> 
>> 
>> On Sat, 13 Mar 2010, Eric W. Biederman wrote:
>> > 
>> > It also only affects those fairly rare lockdep users as well, and the only
>> > affect is to throw a nasty warning message.  Isn't lockdep all about throwing
>> > nasty warning messages?
>> 
>> Hmm. The report has that "BUG: " message in it (and in the subject line), 
>> but you're right - it ends up being just a warning, not actually a real 
>> BUG() (which is a machine killer).
>> 
>> So yeah - it's not as bad as I thought. Sorry.
>
> It's a messy warning, I have patches that should fix the remaining ones
> that I will send to you tomorrow.

Greg if you have it that is great.  I started looking through the emails
I received and it looks like you weren't copied on all of them.  At this
point I will double check after you send out your changes to Linus.  That
we have everything I have seen reported.

Eric

  reply	other threads:[~2010-03-14 18:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-13 19:36 [PATCH] base firmware: Fix BUG from sysfs attributes change in commit a2db6842873c8e5a70652f278d469128cb52db70 Larry Finger
2010-03-13 22:32 ` Linus Torvalds
2010-03-13 22:39   ` Jiri Kosina
2010-03-13 22:57     ` Linus Torvalds
2010-03-14  3:57       ` Eric W. Biederman
2010-03-14  5:46         ` Linus Torvalds
2010-03-14  6:59           ` Ingo Molnar
2010-03-14 17:20             ` Linus Torvalds
2010-03-14 18:11           ` Greg KH
2010-03-14 18:30             ` Eric W. Biederman [this message]
2010-03-14 18:38               ` Greg KH
2010-03-14 10:49         ` Wolfram Sang
2010-03-14 18:04           ` Linus Torvalds
2010-03-14 18:07             ` Linus Torvalds
2010-03-14 19:08             ` Eric W. Biederman
2010-03-15  0:48               ` Wolfram Sang
2010-03-15  0:20             ` Wolfram Sang
2010-03-15  0:29             ` [PATCH] init dynamic bin_attribute structures Wolfram Sang
2010-03-15 10:00               ` Jiri Kosina
2010-03-15 10:12                 ` [rtc-linux] " Wolfram Sang
2010-03-15 18:47                 ` Linus Torvalds
2010-03-13 22:55   ` [PATCH] base firmware: Fix BUG from sysfs attributes change in commit a2db6842873c8e5a70652f278d469128cb52db70 Larry Finger

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=m11vfmzrfr.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gregkh@suse.de \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xiyou.wangcong@gmail.com \
    /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