From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
gregkh@linuxfoundation.org, dmitry.torokhov@gmail.com,
tiwai@suse.de, arjan@linux.intel.com, teg@jklm.no,
rmilasan@suse.com, werner@suse.com, oleg@redhat.com,
hare@suse.com, bpoirier@suse.de, santosh@chelsio.com,
pmladek@suse.cz, dbueso@suse.com, linux-kernel@vger.kernel.org,
Doug Thompson <dougthompson@xmission.com>,
Borislav Petkov <bp@alien8.de>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH v1 3/5] amd64_edac: enforce synchronous probe
Date: Tue, 30 Sep 2014 09:23:28 +0200 [thread overview]
Message-ID: <20140930072328.GD14081@wotan.suse.de> (raw)
In-Reply-To: <20140928144123.GB5023@mtj.dyndns.org>
On Sun, Sep 28, 2014 at 10:41:23AM -0400, Tejun Heo wrote:
> On Fri, Sep 26, 2014 at 02:57:15PM -0700, Luis R. Rodriguez wrote:
> ...
> > [ 14.414746] [<ffffffff814d2cf9>] ? dump_stack+0x41/0x51
> > [ 14.414790] [<ffffffff81061972>] ? warn_slowpath_common+0x72/0x90
> > [ 14.414834] [<ffffffff810619d7>] ? warn_slowpath_fmt+0x47/0x50
> > [ 14.414880] [<ffffffff814d0ac3>] ? printk+0x4f/0x51
> > [ 14.414921] [<ffffffff811f8593>] ? kernfs_remove_by_name_ns+0x83/0x90
> > [ 14.415000] [<ffffffff8137433d>] ? driver_sysfs_remove+0x1d/0x40
> > [ 14.415046] [<ffffffff81374a15>] ? driver_probe_device+0x1d5/0x250
> > [ 14.415099] [<ffffffff81374b4b>] ? __driver_attach+0x7b/0x80
> > [ 14.415149] [<ffffffff81374ad0>] ? __device_attach+0x40/0x40
> > [ 14.415204] [<ffffffff81372a13>] ? bus_for_each_dev+0x53/0x90
> > [ 14.415254] [<ffffffff81373913>] ? driver_attach_workfn+0x13/0x80
> > [ 14.415298] [<ffffffff81077403>] ? process_one_work+0x143/0x3c0
> > [ 14.415342] [<ffffffff81077a44>] ? worker_thread+0x114/0x480
> > [ 14.415384] [<ffffffff81077930>] ? rescuer_thread+0x2b0/0x2b0
> > [ 14.415427] [<ffffffff8107c261>] ? kthread+0xc1/0xe0
> > [ 14.415468] [<ffffffff8107c1a0>] ? kthread_create_on_node+0x170/0x170
> > [ 14.415511] [<ffffffff814d883c>] ? ret_from_fork+0x7c/0xb0
> > [ 14.415554] [<ffffffff8107c1a0>] ? kthread_create_on_node+0x170/0x170
>
> Do you have CONFIG_FRAME_POINTER turned off?
Yeah..
> Probe failure itself
> aside, the above looks like a bug in really_probe()'s error path. It
> looks like it can try to remove sysfs directory that it hasn't added
> yet.
I see one area where that can happen, will debug a bit more to see if we
are running into that here with async probe.
Luis
next prev parent reply other threads:[~2014-09-30 7:23 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 21:57 [PATCH v1 0/5] driver-core: async probe support Luis R. Rodriguez
2014-09-26 21:57 ` [Cocci] [PATCH v1 1/5] module: add extra argument for parse_params() callback Luis R. Rodriguez
2014-09-26 21:57 ` Luis R. Rodriguez
2014-09-26 21:57 ` [PATCH v1 2/5] driver-core: enable drivers to opt-out of async probe Luis R. Rodriguez
2014-09-28 14:33 ` Tejun Heo
2014-09-29 18:55 ` Luis R. Rodriguez
2014-09-26 21:57 ` [PATCH v1 3/5] amd64_edac: enforce synchronous probe Luis R. Rodriguez
2014-09-28 14:41 ` Tejun Heo
2014-09-30 7:23 ` Luis R. Rodriguez [this message]
2014-10-01 22:39 ` Luis R. Rodriguez
2014-10-02 9:18 ` Borislav Petkov
2014-10-02 19:08 ` Luis R. Rodriguez
2014-09-26 21:57 ` [PATCH v1 4/5] driver-core: generalize freeing driver private member Luis R. Rodriguez
2014-09-26 21:57 ` [PATCH v1 5/5] driver-core: add driver asynchronous probe support Luis R. Rodriguez
2014-09-26 21:57 ` Luis R. Rodriguez
2014-09-28 15:03 ` Tejun Heo
2014-09-28 15:03 ` Tejun Heo
2014-09-28 15:03 ` Tejun Heo
2014-09-29 21:22 ` Luis R. Rodriguez
2014-09-29 21:22 ` Luis R. Rodriguez
2014-09-29 21:22 ` Luis R. Rodriguez
2014-09-29 21:26 ` Tejun Heo
2014-09-29 21:26 ` Tejun Heo
2014-09-29 21:26 ` Tejun Heo
2014-09-30 7:21 ` Luis R. Rodriguez
2014-09-30 7:21 ` Luis R. Rodriguez
2014-09-30 7:21 ` Luis R. Rodriguez
2014-10-02 23:29 ` Luis R. Rodriguez
2014-10-02 23:29 ` Luis R. Rodriguez
2014-10-02 23:29 ` Luis R. Rodriguez
2014-09-29 21:59 ` Greg KH
2014-09-29 21:59 ` Greg KH
2014-09-29 21:59 ` Greg KH
2014-09-29 22:10 ` Luis R. Rodriguez
2014-09-29 22:10 ` Luis R. Rodriguez
2014-09-29 22:10 ` Luis R. Rodriguez
2014-09-29 22:24 ` Greg KH
2014-09-29 22:24 ` Greg KH
2014-09-29 22:24 ` Greg KH
2014-09-28 17:07 ` Tom Gundersen
2014-09-28 17:07 ` Tom Gundersen
2014-09-28 17:07 ` Tom Gundersen
2014-09-30 2:27 ` Luis R. Rodriguez
2014-09-30 2:27 ` Luis R. Rodriguez
2014-09-30 2:27 ` Luis R. Rodriguez
2014-09-30 7:47 ` Luis R. Rodriguez
2014-09-30 7:47 ` Luis R. Rodriguez
2014-09-30 7:47 ` Luis R. Rodriguez
2014-09-30 9:22 ` Tom Gundersen
2014-09-30 9:22 ` Tom Gundersen
2014-09-30 9:22 ` Tom Gundersen
2014-09-30 15:24 ` Luis R. Rodriguez
2014-09-30 15:24 ` Luis R. Rodriguez
2014-09-30 15:24 ` Luis R. Rodriguez
2014-10-02 6:12 ` Tom Gundersen
2014-10-02 6:12 ` Tom Gundersen
2014-10-02 6:12 ` Tom Gundersen
2014-10-02 20:06 ` Luis R. Rodriguez
2014-10-02 20:06 ` Luis R. Rodriguez
2014-10-02 20:06 ` Luis R. Rodriguez
2014-10-03 8:23 ` Tom Gundersen
2014-10-03 8:23 ` Tom Gundersen
2014-10-03 8:23 ` Tom Gundersen
2014-10-03 16:54 ` Luis R. Rodriguez
2014-10-03 16:54 ` Luis R. Rodriguez
2014-10-03 16:54 ` Luis R. Rodriguez
2014-09-28 19:22 ` Dmitry Torokhov
2014-09-28 19:22 ` Dmitry Torokhov
2014-09-28 19:22 ` Dmitry Torokhov
2014-09-30 7:15 ` Luis R. Rodriguez
2014-09-30 7:15 ` Luis R. Rodriguez
2014-09-30 7:15 ` Luis R. Rodriguez
2014-10-02 23:31 ` Luis R. Rodriguez
2014-10-02 23:31 ` Luis R. Rodriguez
2014-10-02 23:31 ` Luis R. Rodriguez
2014-10-03 20:11 ` Luis R. Rodriguez
2014-10-03 20:11 ` Luis R. Rodriguez
2014-10-03 20:11 ` Luis R. Rodriguez
2014-10-03 21:12 ` Luis R. Rodriguez
2014-10-03 21:12 ` Luis R. Rodriguez
2014-10-03 21:12 ` Luis R. Rodriguez
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=20140930072328.GD14081@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=bpoirier@suse.de \
--cc=dbueso@suse.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dougthompson@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mcgrof@do-not-panic.com \
--cc=oleg@redhat.com \
--cc=pmladek@suse.cz \
--cc=rmilasan@suse.com \
--cc=santosh@chelsio.com \
--cc=teg@jklm.no \
--cc=tiwai@suse.de \
--cc=tj@kernel.org \
--cc=werner@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.