All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: gregkh@linuxfoundation.org,
	Anupama K Patil <anupamakpatil123@gmail.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	bkkarthik <bkkarthik@pesu.pes.edu>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	kernelnewbies@kernelnewbies.org, skhan@linuxfoundation.org
Subject: Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
Date: Wed, 28 Apr 2021 15:21:55 +0300	[thread overview]
Message-ID: <YIlTY8p4kpkORPfl@unreal> (raw)
In-Reply-To: <59a5d631-6658-2034-06c4-467520b5b9f7@perex.cz>

On Wed, Apr 28, 2021 at 02:04:49PM +0200, Jaroslav Kysela wrote:
> Dne 26. 04. 21 v 19:50 bkkarthik napsal(a):
> > On 21/04/26 08:04AM, Leon Romanovsky wrote:
> >> On Sun, Apr 25, 2021 at 01:13:01AM +0530, Anupama K Patil wrote:
> >>> isapnp_proc_init() does not look at the return value from
> >>> isapnp_proc_attach_device(). Check for this return value in
> >>> isapnp_proc_detach_device().
> >>>
> >>> Cleanup in isapnp_proc_detach_device and
> >>> isapnp_proc_detach_bus() for cleanup.
> >>>
> >>> Changed sprintf() to the kernel-space function scnprintf() as it returns
> >>> the actual number of bytes written.
> >>>
> >>> Removed unnecessary variables de, e of type 'struct proc_dir_entry' to
> >>> save memory.
> >>
> >> What exactly do you fix for such an old code?
> > 
> > I was not aware that this code is so old. This fix was made after checkpatch reported assignment inside an if-statement.
> > Please ignore this patch if th change is not necessary as the code is probably not being used anywhere :)
> > 
> > Maybe the code has to be marked as obsolete in the MAINTAINERS file to prevent patches being sent?
> > 
> >>
> >>>
> >>> Suggested-by: Shuah Khan <skhan@linuxfoundation.org>
> >>> Co-developed-by: B K Karthik <bkkarthik@pesu.pes.edu>
> >>> Signed-off-by: B K Karthik <bkkarthik@pesu.pes.edu>
> >>> Signed-off-by: Anupama K Patil <anupamakpatil123@gmail.com>
> >>> ---
> >>>  drivers/pnp/isapnp/proc.c | 40 +++++++++++++++++++++++++++++----------
> >>>  1 file changed, 30 insertions(+), 10 deletions(-)
> >>>
> >>> diff --git a/drivers/pnp/isapnp/proc.c b/drivers/pnp/isapnp/proc.c
> >>> index 785a796430fa..46ebc24175b7 100644
> >>> --- a/drivers/pnp/isapnp/proc.c
> >>> +++ b/drivers/pnp/isapnp/proc.c
> >>> @@ -54,34 +54,54 @@ static const struct proc_ops isapnp_proc_bus_proc_ops = {
> >>>  	.proc_read	= isapnp_proc_bus_read,
> >>>  };
> >>>  
> >>> +static int isapnp_proc_detach_device(struct pnp_dev *dev)
> >>> +{
> >>> +	proc_remove(dev->procent);
> >>> +	dev->procent = NULL;
> >>> +	return 0;
> >>> +}
> >>> +
> >>> +static int isapnp_proc_detach_bus(struct pnp_card *bus)
> >>> +{
> >>> +	proc_remove(bus->procdir);
> >>> +	return 0;
> >>> +}
> >>
> >> Please don't add one line functions that are called only once and have
> >> return value that no one care about it.
> > 
> > These were only intended for a clean-up job, the idea of this function came from how PCI handles procfs.
> > Maybe those should be changed?
> 
> Which code you refer? I see:
> 
>        for_each_pci_dev(dev)
>                 pci_proc_attach_device(dev);

He talks about isapnp_proc_detach_*() functions.

> 
> 
> The error codes are ignored, too. It does not harm, if proc entries are not
> created (in this case - the system is unstable anyway). We should concentrate
> only to the wrong pointers usage.
> 
> 						Jaroslav
> 
> -- 
> Jaroslav Kysela <perex@perex.cz>
> Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

WARNING: multiple messages have this Message-ID (diff)
From: Leon Romanovsky <leon@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: bkkarthik <bkkarthik@pesu.pes.edu>,
	Anupama K Patil <anupamakpatil123@gmail.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	skhan@linuxfoundation.org, gregkh@linuxfoundation.org,
	kernelnewbies@kernelnewbies.org
Subject: Re: [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices
Date: Wed, 28 Apr 2021 15:21:55 +0300	[thread overview]
Message-ID: <YIlTY8p4kpkORPfl@unreal> (raw)
In-Reply-To: <59a5d631-6658-2034-06c4-467520b5b9f7@perex.cz>

On Wed, Apr 28, 2021 at 02:04:49PM +0200, Jaroslav Kysela wrote:
> Dne 26. 04. 21 v 19:50 bkkarthik napsal(a):
> > On 21/04/26 08:04AM, Leon Romanovsky wrote:
> >> On Sun, Apr 25, 2021 at 01:13:01AM +0530, Anupama K Patil wrote:
> >>> isapnp_proc_init() does not look at the return value from
> >>> isapnp_proc_attach_device(). Check for this return value in
> >>> isapnp_proc_detach_device().
> >>>
> >>> Cleanup in isapnp_proc_detach_device and
> >>> isapnp_proc_detach_bus() for cleanup.
> >>>
> >>> Changed sprintf() to the kernel-space function scnprintf() as it returns
> >>> the actual number of bytes written.
> >>>
> >>> Removed unnecessary variables de, e of type 'struct proc_dir_entry' to
> >>> save memory.
> >>
> >> What exactly do you fix for such an old code?
> > 
> > I was not aware that this code is so old. This fix was made after checkpatch reported assignment inside an if-statement.
> > Please ignore this patch if th change is not necessary as the code is probably not being used anywhere :)
> > 
> > Maybe the code has to be marked as obsolete in the MAINTAINERS file to prevent patches being sent?
> > 
> >>
> >>>
> >>> Suggested-by: Shuah Khan <skhan@linuxfoundation.org>
> >>> Co-developed-by: B K Karthik <bkkarthik@pesu.pes.edu>
> >>> Signed-off-by: B K Karthik <bkkarthik@pesu.pes.edu>
> >>> Signed-off-by: Anupama K Patil <anupamakpatil123@gmail.com>
> >>> ---
> >>>  drivers/pnp/isapnp/proc.c | 40 +++++++++++++++++++++++++++++----------
> >>>  1 file changed, 30 insertions(+), 10 deletions(-)
> >>>
> >>> diff --git a/drivers/pnp/isapnp/proc.c b/drivers/pnp/isapnp/proc.c
> >>> index 785a796430fa..46ebc24175b7 100644
> >>> --- a/drivers/pnp/isapnp/proc.c
> >>> +++ b/drivers/pnp/isapnp/proc.c
> >>> @@ -54,34 +54,54 @@ static const struct proc_ops isapnp_proc_bus_proc_ops = {
> >>>  	.proc_read	= isapnp_proc_bus_read,
> >>>  };
> >>>  
> >>> +static int isapnp_proc_detach_device(struct pnp_dev *dev)
> >>> +{
> >>> +	proc_remove(dev->procent);
> >>> +	dev->procent = NULL;
> >>> +	return 0;
> >>> +}
> >>> +
> >>> +static int isapnp_proc_detach_bus(struct pnp_card *bus)
> >>> +{
> >>> +	proc_remove(bus->procdir);
> >>> +	return 0;
> >>> +}
> >>
> >> Please don't add one line functions that are called only once and have
> >> return value that no one care about it.
> > 
> > These were only intended for a clean-up job, the idea of this function came from how PCI handles procfs.
> > Maybe those should be changed?
> 
> Which code you refer? I see:
> 
>        for_each_pci_dev(dev)
>                 pci_proc_attach_device(dev);

He talks about isapnp_proc_detach_*() functions.

> 
> 
> The error codes are ignored, too. It does not harm, if proc entries are not
> created (in this case - the system is unstable anyway). We should concentrate
> only to the wrong pointers usage.
> 
> 						Jaroslav
> 
> -- 
> Jaroslav Kysela <perex@perex.cz>
> Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

  reply	other threads:[~2021-04-28 12:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24 19:43 [PATCH] drivers: pnp: proc.c: Handle errors while attaching devices Anupama K Patil
2021-04-24 19:43 ` Anupama K Patil
2021-04-24 20:37 ` Valdis Klētnieks
2021-04-24 20:37   ` Valdis Klētnieks
2021-04-25  1:06 ` Barnabás Pőcze
2021-04-25  1:06   ` Barnabás Pőcze
2021-04-26  5:04 ` Leon Romanovsky
2021-04-26  5:04   ` Leon Romanovsky
2021-04-26 17:50   ` bkkarthik
2021-04-26 17:50     ` bkkarthik
2021-04-27  4:26     ` Leon Romanovsky
2021-04-27  4:26       ` Leon Romanovsky
2021-04-29  4:31       ` Valdis Klētnieks
2021-04-29  4:31         ` Valdis Klētnieks
2021-04-29  7:05         ` Leon Romanovsky
2021-04-29  7:05           ` Leon Romanovsky
2021-04-28 12:04     ` Jaroslav Kysela
2021-04-28 12:04       ` Jaroslav Kysela
2021-04-28 12:21       ` Leon Romanovsky [this message]
2021-04-28 12:21         ` Leon Romanovsky
2021-04-28 12:26         ` bkkarthik
2021-04-28 12:26           ` bkkarthik
2021-04-28 12:30         ` Jaroslav Kysela
2021-04-28 12:30           ` Jaroslav Kysela
2021-04-28 12:37           ` bkkarthik
2021-04-28 12:37             ` bkkarthik

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=YIlTY8p4kpkORPfl@unreal \
    --to=leon@kernel.org \
    --cc=anupamakpatil123@gmail.com \
    --cc=bkkarthik@pesu.pes.edu \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=rafael.j.wysocki@intel.com \
    --cc=skhan@linuxfoundation.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 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.