From: Armin Schindler <armin@melware.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] isdn divas: fix proc creation
Date: Thu, 5 Jun 2008 12:25:06 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.0.99.0806051221380.30590@k10.melware.de> (raw)
In-Reply-To: <20080530233445.GB7358@martell.zuzino.mipt.ru>
On Sat, 31 May 2008, Alexey Dobriyan wrote:
> 1. creating proc entry and not saving pointer to PDE and checking it
> is not going to work.
I don't know where you found this. I have look even in older versions, but
the pointer divas_proc_entry is set by proc_create(). The patch to
divasproc.c is wrong, it exists from the beginning of the driver.
(2.6.25.4 doesn't contain the bug you describe).
> 2. if proc entry wasn't created, no reason to remove it on error path.
Agreed here. The reason for doing remove_divas_proc() anyway, was to
make sure all possible settings done in !create_divas_proc() are
reverted. But since nothing else is done here, it is okay to remove it.
Armin
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
>
> drivers/isdn/hardware/eicon/divasmain.c | 1 -
> drivers/isdn/hardware/eicon/divasproc.c | 4 ++--
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
> --- a/drivers/isdn/hardware/eicon/divasmain.c
> +++ b/drivers/isdn/hardware/eicon/divasmain.c
> @@ -806,7 +806,6 @@ static int DIVA_INIT_FUNCTION divas_init(void)
>
> if (!create_divas_proc()) {
> #ifdef MODULE
> - remove_divas_proc();
> divas_unregister_chrdev();
> divasfunc_exit();
> #endif
> --- a/drivers/isdn/hardware/eicon/divasproc.c
> +++ b/drivers/isdn/hardware/eicon/divasproc.c
> @@ -125,8 +125,8 @@ static const struct file_operations divas_fops = {
>
> int create_divas_proc(void)
> {
> - proc_create(divas_proc_name, S_IFREG | S_IRUGO, proc_net_eicon,
> - &divas_fops);
> + divas_proc_entry = proc_create(divas_proc_name, S_IFREG | S_IRUGO,
> + proc_net_eicon, &divas_fops);
> if (!divas_proc_entry)
> return (0);
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2008-06-05 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 23:34 Alexey Dobriyan
2008-06-05 10:25 ` Armin Schindler [this message]
2008-06-06 6:17 ` Alexey Dobriyan
2008-06-06 6:44 ` Armin Schindler
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=alpine.DEB.0.99.0806051221380.30590@k10.melware.de \
--to=armin@melware.de \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.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
all inboxes | Powered by JetHome®