linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zheng, Lv" <lv.zheng@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	"Brown, Len" <len.brown@intel.com>, Lv Zheng <zetalog@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux ACPI <linux-acpi@vger.kernel.org>
Subject: RE: [RFC PATCH] ACPICA: Tables: Fix regression introduced by a too early mechanism enabling
Date: Wed, 26 Apr 2017 05:15:07 +0000	[thread overview]
Message-ID: <1AE640813FDE7649BE1B193DEA596E886CE98BCA@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAPcyv4gtYzkeUL-Ou8bap5Sye=1Tq2PmuhZM04nFPwdjmCwCgg@mail.gmail.com>

Hi,

> From: Dan Williams [mailto:dan.j.williams@intel.com]
> Subject: Re: [RFC PATCH] ACPICA: Tables: Fix regression introduced by a too early mechanism enabling
> 
> On Tue, Apr 25, 2017 at 6:49 PM, Lv Zheng <lv.zheng@intel.com> wrote:
> > In the Linux kernel side, acpi_get_table() hasn't been fully balanced by
> > acpi_put_table() invocations. So it is not a good timing to report errors.
> > The strict balanced validation count check should only be enabled after
> > confirming that all kernel side invocations are safe.
> 
> We've been living with this bug for 7 years, let's just go fix all
> acpi_get_table() invocations to make sure they have a corresponding
> acpi_put_table().

We knew that, you should have already seen a series internally or
externally from me achieving this.
It's done several years ago. But it takes long time to make the
ACPICA part upstreamed.

Now my plan is:
1. introduce the APIs but allow old usage models in order not to
   change old ACPICA behavior and its users.
2. fix all users
3. disallow old usage models.
It's just my mistake to leak the final stage approach to the ACPICA
upstream from my local repo.
Now we can try to jump to the final step, but as far as I know,
not only Linux, ACPICA itself also contains several broken cases.

Bottom line of Linux kernel is we shouldn't break any running system.
So IMO, we will need this commit during this special period.

I didn't say the final step is wrong or is not required.
We can do both in parallel.

So could you please help to confirm if it's working.
And I would like to suggest linux to take this first step fix along
with other final step fixes during this period.

Thanks and best regards
Lv

> 
> >
> > Thus this patch removes the fatal error but leaves the error report to
> > indicate the leak so that developers can notice the required engineering
> > change. Reported by Dan Williams, fixed by Lv Zheng.
> >
> > Reported-by: Dan Williams <dan.j.williams@intel.com>
> > Signed-off-by: Lv Zheng <lv.zheng@intel.com>
> > ---
> >  drivers/acpi/acpica/tbutils.c | 1 -
> >  1 file changed, 1 deletion(-)
> >
> > diff --git a/drivers/acpi/acpica/tbutils.c b/drivers/acpi/acpica/tbutils.c
> > index 5a968a7..9e7d95cf 100644
> > --- a/drivers/acpi/acpica/tbutils.c
> > +++ b/drivers/acpi/acpica/tbutils.c
> > @@ -422,7 +422,6 @@ acpi_tb_get_table(struct acpi_table_desc *table_desc,
> >                             "Table %p, Validation count is zero after increment\n",
> >                             table_desc));
> >                 table_desc->validation_count--;
> > -               return_ACPI_STATUS(AE_LIMIT);
> 
> If you want to leave the error report turn it into a WARN_ON_ONCE() so
> it doesn't keep triggering, but I'd rather we just focus on the
> missing acpi_put_table() calls.

  reply	other threads:[~2017-04-26  5:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26  1:49 [RFC PATCH] ACPICA: Tables: Fix regression introduced by a too early mechanism enabling Lv Zheng
2017-04-26  5:00 ` Dan Williams
2017-04-26  5:15   ` Zheng, Lv [this message]
2017-04-26 14:13     ` Dan Williams
2017-04-26 15:34       ` Dan Williams

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=1AE640813FDE7649BE1B193DEA596E886CE98BCA@SHSMSX101.ccr.corp.intel.com \
    --to=lv.zheng@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=zetalog@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).