From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: kernel test robot <fengguang.wu@intel.com>
Cc: LKP <lkp@01.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
wfg@linux.intel.com
Subject: Re: [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153!
Date: Mon, 15 Feb 2016 17:20:01 +0530 [thread overview]
Message-ID: <20160215115001.GA22934@sudip-pc> (raw)
In-Reply-To: <56c18a5d.4mR6FT1TNJ7yeYPN%fengguang.wu@intel.com>
On Mon, Feb 15, 2016 at 04:20:45PM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-testing
>
> commit e7223f18603374d235d8bb0398532323e5f318b9
> Author: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> AuthorDate: Fri Feb 12 18:33:45 2016 +0530
> Commit: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> CommitDate: Sun Feb 14 17:43:50 2016 -0800
>
> ppdev: use new parport device model
>
> Modify ppdev driver to use the new parallel port device model.
>
> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Can you please send the .config file so that i can reproduce in my local
system and test?
Ying Huang also sent a similar report after posting the patches. I tried
his .config and your scripts to reproduce this but was not able to.
Anyway, this error is not related to this patch, this patch has just
uncovered this error in parport. And will only happen if ppdev tries to
register with parport before parport bus is registered.
Can you please check if the below patch solves the problem:
diff --git a/drivers/parport/share.c b/drivers/parport/share.c
index 3308427..176b2b6 100644
--- a/drivers/parport/share.c
+++ b/drivers/parport/share.c
@@ -273,6 +273,9 @@ int __parport_register_driver(struct parport_driver *drv, struct module *owner,
/* using device model */
int ret;
+ if (!parport_bus_type.p)
+ return -EAGAIN;
+
/* initialize common driver fields */
drv->driver.name = drv->name;
drv->driver.bus = &parport_bus_type;
--
regards
sudip
next prev parent reply other threads:[~2016-02-15 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 8:20 [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153! kernel test robot
2016-02-15 11:50 ` Sudip Mukherjee [this message]
2016-03-02 21:24 ` Ross Zwisler
2016-03-03 5:51 ` Sudip Mukherjee
2016-03-03 15:36 ` Ross Zwisler
2016-03-24 14:41 ` Petr Mladek
2016-03-25 16:12 ` Linus Torvalds
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=20160215115001.GA22934@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=wfg@linux.intel.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