public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: "Zheng, Lv" <lv.zheng@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / button: remove pointer to old lid_sysfs on unbind
Date: Fri, 29 Jul 2016 09:53:35 +0200	[thread overview]
Message-ID: <20160729075335.GP19383@mail.corp.redhat.com> (raw)
In-Reply-To: <1AE640813FDE7649BE1B193DEA596E883BC07E6E@SHSMSX101.ccr.corp.intel.com>

On Jul 29 2016 or thereabouts, Zheng, Lv wrote:
> Hi, Benjamin
> 
> > From: linux-acpi-owner@vger.kernel.org [mailto:linux-acpi-
> > owner@vger.kernel.org] On Behalf Of Benjamin Tissoires
> > Subject: [PATCH] ACPI / button: remove pointer to old lid_sysfs on unbind
> > 
> > When we removed the procfs dir on error or if the driver is
> > unbound, the two variables acpi_lid_dir and acpi_button_dir
> > were not reset. On the next rebind, those static variables
> > were not null and we couldn't re-register the device again.
> > 
> > Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> > ---
> >  drivers/acpi/button.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/drivers/acpi/button.c b/drivers/acpi/button.c
> > index 5c3b091..e413599 100644
> > --- a/drivers/acpi/button.c
> > +++ b/drivers/acpi/button.c
> > @@ -188,9 +188,11 @@ done:
> [Lv Zheng] 
> I have a concern here for acpi_button_add_fs().
> It looks like that this function doesn't support 2 lid devices.
> So why do we need /proc/acpi/button/lid/LID0 folder?

History I guess?

- (re)introduced in b34a803 "[ACPI] restore /proc/acpi/button/ (ala 2.6.12)"
  (2005-08-03)
- procfs cleaned up in 912b742 "ACPI button: remove unused procfs I/F"
  (2011-03-23)

And I would believe given that it was introduced prior 2.6.12, it's now
kernel ABI.

> 
> >  remove_dev_dir:
> >  	remove_proc_entry(acpi_device_bid(device),
> >  			  acpi_lid_dir);
> > +	acpi_lid_dir = NULL;
> >  	acpi_device_dir(device) = NULL;
> >  remove_lid_dir:
> >  	remove_proc_entry(ACPI_BUTTON_SUBCLASS_LID,
> > acpi_button_dir);
> [Lv Zheng] 
> Should acpi_lid_dir = NULL be put here?

Right

> 
> > +	acpi_button_dir = NULL;
> >  remove_button_dir:
> >  	remove_proc_entry(ACPI_BUTTON_CLASS, acpi_root_dir);
> [Lv Zheng] 
> Should acpi_button_dir = NULL be put here?
> 

Right

> >  	goto done;
> > @@ -207,8 +209,10 @@ static int acpi_button_remove_fs(struct
> > acpi_device *device)
> >  			  acpi_device_dir(device));
> >  	remove_proc_entry(acpi_device_bid(device),
> >  			  acpi_lid_dir);
> > +	acpi_lid_dir = NULL;
> >  	acpi_device_dir(device) = NULL;
> >  	remove_proc_entry(ACPI_BUTTON_SUBCLASS_LID,
> > acpi_button_dir);
> [Lv Zheng] 
> Should acpi_lid_dir = NULL be put here?
> 
> > +	acpi_button_dir = NULL;
> >  	remove_proc_entry(ACPI_BUTTON_CLASS, acpi_root_dir);
> [Lv Zheng] 
> Should acpi_button_dir = NULL be put here?

Right for these too to, but it won't change the result in the end :)

I'll send a v2 ASAP.

Cheers,
Benjamin

> 
> Thanks and best regards
> Lv
> 
> > 
> >  	return 0;
> > --
> > 2.5.5
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2016-07-29  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 10:19 [PATCH] ACPI / button: remove pointer to old lid_sysfs on unbind Benjamin Tissoires
2016-07-29  4:35 ` Zheng, Lv
2016-07-29  7:53   ` Benjamin Tissoires [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=20160729075335.GP19383@mail.corp.redhat.com \
    --to=benjamin.tissoires@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=rjw@rjwysocki.net \
    /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