linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bryan Wu" <cooloney@kernel.org>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Bryan Wu <bryan.wu@analog.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Input/Touchscreen Driver: add support AD7877touchscreen driver
Date: Mon, 12 May 2008 14:33:50 +0800	[thread overview]
Message-ID: <386072610805112333w7bc935eo4ad0aae47b1c3975@mail.gmail.com> (raw)
In-Reply-To: <8A42379416420646B9BFAC9682273B6D56269C@limkexm3.ad.analog.com>

On Wed, Apr 9, 2008 at 1:13 AM, Hennerich, Michael
<Michael.Hennerich@analog.com> wrote:
>
>
>>-----Original Message-----
>>From: Dmitry Torokhov [mailto:dmitry.torokhov@gmail.com]
>>Sent: Montag, 7. April 2008 22:16
>>To: Bryan Wu
>>Cc: linux-input@vger.kernel.org; linux-kernel@vger.kernel.org; Michael
>>Hennerich
>>Subject: Re: [PATCH 1/1] Input/Touchscreen Driver: add support
>>AD7877touchscreen driver
>>
>>Hi Bryan, Michael,
>>
>>On Thu, Feb 14, 2008 at 05:17:28PM +0800, Bryan Wu wrote:
>>> From: Michael Hennerich <michael.hennerich@analog.com>
>>>
>>> [try #3] Changlog (Add feedback from Dmitry Torokhov):
>>>  - Change handling of spi_sync / spi_async return value handling
>>>  - Remove depreciated dev->power.power_state
>>>  - Fix error return path in ad7877_probe
>>>  - delete pending kernel timer
>>>  - Some minor cleanup (indention, use dev_err etc.)
>>
>>Sorry for the long silence... I have a couple of comments at the moment
>>but I am sure i will have more ;)
>>
>>> +
>>> +    status = spi_sync(spi, &req->msg);
>>> +
>>> +    if (status == 0)
>>> +            status = req->msg.status;
>>> +
>>> +    kfree(req);
>>> +    return status ? status : req->sample;
>>
>>Use after free here.
>
> Yeah this is definitely broken.
>
>>
>>> +
>>> +    ts->irq_disabled = 1;
>>> +    disable_irq(spi->irq);
>>
>>I am a bit uneasy here... do we need to wait for an async spi
> completion
>>here before proceeding? Overall I have some concerns about the
>>irq/spi/removal/sysfs iteractions, I will need some more time to look
>>through the driver.
>
>
> I think you are right - let me come up with a patch.
>
> Thanks and best regards,
> Michael
>
>>

Hi Dmitry,

Sorry for no updates, I forget to send out that patch, although
Michael fixed the driver as your review.

So need I send out one updated patch including Michael's fixing or
just send out his incremental patch?

Thanks
-Bryan

  reply	other threads:[~2008-05-12  6:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  9:17 [PATCH 1/1] Input/Touchscreen Driver: add support AD7877 touchscreen driver Bryan Wu
2008-04-07 20:16 ` Dmitry Torokhov
2008-04-08 17:13   ` [PATCH 1/1] Input/Touchscreen Driver: add support AD7877touchscreen driver Hennerich, Michael
2008-05-12  6:33     ` Bryan Wu [this message]
2008-05-12 12:40       ` Dmitry Torokhov

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=386072610805112333w7bc935eo4ad0aae47b1c3975@mail.gmail.com \
    --to=cooloney@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=bryan.wu@analog.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).