From: Greg KH <gregkh@suse.de>
To: Anton Blanchard <anton@samba.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devmem: Handle class_create() failure
Date: Fri, 2 Apr 2010 09:53:24 -0700 [thread overview]
Message-ID: <20100402165324.GD32081@suse.de> (raw)
In-Reply-To: <20100402072920.GH5594@kryten>
On Fri, Apr 02, 2010 at 06:29:20PM +1100, Anton Blanchard wrote:
>
> I hit this when we had a bug in IDR for a few days. Basically sysfs would
> fail to create new inodes since it uses an IDR and therefore class_create would
> fail.
>
> While we are unlikely to see this fail we may as well handle it instead of
> oopsing.
Is this something that we need for .34? How were you getting this to
fail in the first place?
thanks,
greg k-h
next prev parent reply other threads:[~2010-04-02 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 7:29 [PATCH] devmem: Handle class_create() failure Anton Blanchard
2010-04-02 7:36 ` Wu Fengguang
2010-04-02 16:53 ` Greg KH [this message]
2010-04-03 2:03 ` Anton Blanchard
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=20100402165324.GD32081@suse.de \
--to=gregkh@suse.de \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=fengguang.wu@intel.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
/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