mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [patch] procfs: returns ENOENT on opening the being-removed proc entry
@ 2011-06-24  1:48 "FJCL) 荻野 大輔"
  2011-06-27  1:19 ` KAMEZAWA Hiroyuki
  0 siblings, 1 reply; 3+ messages in thread
From: "FJCL) 荻野 大輔" @ 2011-06-24  1:48 UTC (permalink / raw)
  To: linux-kernel; +Cc: linux-pci, adobriyan

From: Daisuke Ohino <ogino.daisuke@jp.fujitsu.com>

opening the proc entry may return EINVAL if the entry is being removed, for
example open("/proc/bus/pci/XX/YY") during the corresponding device is being
hot-removed. The return value is inappropriate and should return ENOENT.

This return value comes from proc_reg_open().

fs/proc/inode.c:
-----------------------------------------------------------
static int proc_reg_open(struct inode *inode, struct file *file)
{
(snip)
        if (!pde->proc_fops) {
                spin_unlock(&pde->pde_unload_lock);
                kfree(pdeo);
                return -EINVAL;
        }
(snip)
-----------------------------------------------------------

pde->proc_fops is NULL iff the proc entry is being removed. It
is set by remove_proc_entry().

-----------------------------------------------------------
void remove_proc_entry(const char *name, struct proc_dir_entry*parent)
{
(snip)
        /*
         * Stop accepting new callers into module. If you're
         * dynamically allocating ->proc_fops, save a pointer somewhere.
         */
        de->proc_fops = NULL;
(snip)
-----------------------------------------------------------

But POSIX says:

-----------------------------------------------------------
[EINVAL]
    The implementation does not support synchronized I/O for this file.
-----------------------------------------------------------

Since removing proc entry is apparently not related to synchronized I/O,
this function should return ENOENT in this case.

Signed-off-by: Daisuke Ogino <ogino.daisuke@jp.fujitsu.com>
---
 fs/proc/inode.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/proc/inode.c b/fs/proc/inode.c
index 74b48cf..7ed72d6 100644
--- a/fs/proc/inode.c
+++ b/fs/proc/inode.c
@@ -319,7 +319,7 @@ static int proc_reg_open(struct inode *inode, struct file *file)
 	if (!pde->proc_fops) {
 		spin_unlock(&pde->pde_unload_lock);
 		kfree(pdeo);
-		return -EINVAL;
+		return -ENOENT;
 	}
 	pde->pde_users++;
 	open = pde->proc_fops->open;
--

Since I don't subscribe LKML, please Cc me if you have any comment.

Thanks,
Daisuke



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [patch] procfs: returns ENOENT on opening the being-removed proc entry
  2011-06-24  1:48 [patch] procfs: returns ENOENT on opening the being-removed proc entry "FJCL) 荻野 大輔"
@ 2011-06-27  1:19 ` KAMEZAWA Hiroyuki
  2011-06-30 10:44   ` Daisuke Ogino
  0 siblings, 1 reply; 3+ messages in thread
From: KAMEZAWA Hiroyuki @ 2011-06-27  1:19 UTC (permalink / raw)
  To: "FJCL) 荻野 大輔"
  Cc: linux-kernel, linux-pci, adobriyan, linux-fsdevel

On Fri, 24 Jun 2011 10:48:08 +0900
"FJCL) 荻野 大輔" <ogino.daisuke@jp.fujitsu.com> wrote:

> From: Daisuke Ohino <ogino.daisuke@jp.fujitsu.com>
> 
> opening the proc entry may return EINVAL if the entry is being removed, for
> example open("/proc/bus/pci/XX/YY") during the corresponding device is being
> hot-removed. The return value is inappropriate and should return ENOENT.
> 
> This return value comes from proc_reg_open().
> 
> fs/proc/inode.c:
> -----------------------------------------------------------
> static int proc_reg_open(struct inode *inode, struct file *file)
> {
> (snip)
>         if (!pde->proc_fops) {
>                 spin_unlock(&pde->pde_unload_lock);
>                 kfree(pdeo);
>                 return -EINVAL;
>         }
> (snip)
> -----------------------------------------------------------
> 
> pde->proc_fops is NULL iff the proc entry is being removed. It
> is set by remove_proc_entry().
> 
> -----------------------------------------------------------
> void remove_proc_entry(const char *name, struct proc_dir_entry*parent)
> {
> (snip)
>         /*
>          * Stop accepting new callers into module. If you're
>          * dynamically allocating ->proc_fops, save a pointer somewhere.
>          */
>         de->proc_fops = NULL;
> (snip)
> -----------------------------------------------------------
> 
> But POSIX says:
> 
> -----------------------------------------------------------
> [EINVAL]
>     The implementation does not support synchronized I/O for this file.
> -----------------------------------------------------------
> 
> Since removing proc entry is apparently not related to synchronized I/O,
> this function should return ENOENT in this case.
> 
> Signed-off-by: Daisuke Ogino <ogino.daisuke@jp.fujitsu.com>

It makes sense to me. 

Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>

Add fsdevel to CC.

> ---
>  fs/proc/inode.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/proc/inode.c b/fs/proc/inode.c
> index 74b48cf..7ed72d6 100644
> --- a/fs/proc/inode.c
> +++ b/fs/proc/inode.c
> @@ -319,7 +319,7 @@ static int proc_reg_open(struct inode *inode, struct file *file)
>  	if (!pde->proc_fops) {
>  		spin_unlock(&pde->pde_unload_lock);
>  		kfree(pdeo);
> -		return -EINVAL;
> +		return -ENOENT;
>  	}
>  	pde->pde_users++;
>  	open = pde->proc_fops->open;
> --
> 
> Since I don't subscribe LKML, please Cc me if you have any comment.
> 
> Thanks,
> Daisuke
> 
> 
> --
> 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/
> 


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [patch] procfs: returns ENOENT on opening the being-removed proc entry
  2011-06-27  1:19 ` KAMEZAWA Hiroyuki
@ 2011-06-30 10:44   ` Daisuke Ogino
  0 siblings, 0 replies; 3+ messages in thread
From: Daisuke Ogino @ 2011-06-30 10:44 UTC (permalink / raw)
  To: linux-kernel; +Cc: linux-pci, linux-fsdevel, jbarnes, hch, akpm, adobriyan

Hello.

Though I posted the following patch a week ago, 
there is no objection, and Kame-san reviewed it.

I hope merge it by someone if possible.
(I don't find maintainer's name for procfs.)

---
I changed the return value to ENOENT.
This return value is then returned when opening the proc entry 
that have been removed.
For example, open("/proc/bus/pci/XX/YY") during the corresponding 
device is being hot-removed.

Signed-off-by: Daisuke Ogino <ogino.daisuke@jp.fujitsu.com>
---
 fs/proc/inode.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/proc/inode.c b/fs/proc/inode.c
index 74b48cf..7ed72d6 100644
--- a/fs/proc/inode.c
+++ b/fs/proc/inode.c
@@ -319,7 +319,7 @@ static int proc_reg_open(struct inode *inode, struct file *file)
 	if (!pde->proc_fops) {
 		spin_unlock(&pde->pde_unload_lock);
 		kfree(pdeo);
-		return -EINVAL;
+		return -ENOENT;
 	}
 	pde->pde_users++;
 	open = pde->proc_fops->open;
--

Thanks.
-- 
Daisuke Ogino



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-06-30 10:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-06-24  1:48 [patch] procfs: returns ENOENT on opening the being-removed proc entry "FJCL) 荻野 大輔"
2011-06-27  1:19 ` KAMEZAWA Hiroyuki
2011-06-30 10:44   ` Daisuke Ogino

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®