From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Willy Tarreau <willy@meta-x.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: panel: fix stackdump
Date: Tue, 12 May 2015 17:20:23 +0530 [thread overview]
Message-ID: <20150512115023.GA13738@sudip-PC> (raw)
In-Reply-To: <20150512112712.GP14154@mwanda>
On Tue, May 12, 2015 at 02:27:13PM +0300, Dan Carpenter wrote:
> On Tue, May 12, 2015 at 04:45:44PM +0530, Sudip Mukherjee wrote:
> > if we load the module, unload and then again try to load the module, we
> > will get a stackdump. In the module_exit function we are unregistering
> > the device and releasing the parport. So when we reach the detach
> > function parport is already null and the unregister_reboot_notifier()
> > is never called. When we again try to load the module it again tries
> > register_reboot_notifier() and gives us a stackdump as its earlier
> > registration is still not removed. It was caused by the commit
> > <bb046fef9668baf1c4744a3c7aba05e15e44c9ac>.
>
> The right format is:
>
> commit bb046fef9668 ('staging: panel: register reboot')
>
> It is in case human beings reading your description don't remember which
> patch bb046fef9668 was.
>
> > Fix this by moving all the unregistering and releasing in the detach
> > function, which should be the ideal case as the detach will be called if
> > we try to unregister the driver or if the parport is removed.
> >
>
> We also have the Fixes: tag.
>
> Fixes: bb046fef9668 ('staging: panel: register reboot')
ok, thanks.
I will send the v3 with the commit in correct format.
regards
sudip
>
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
>
> regards,
> dan carpenter
>
prev parent reply other threads:[~2015-05-12 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 11:15 [PATCH v2] staging: panel: fix stackdump Sudip Mukherjee
2015-05-12 11:27 ` Dan Carpenter
2015-05-12 11:50 ` Sudip Mukherjee [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=20150512115023.GA13738@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@meta-x.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