mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiubo Li <xiubli@redhat.com>
To: Hamish Martin <Hamish.Martin@alliedtelesis.co.nz>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "jannh@google.com" <jannh@google.com>,
	"pkalever@redhat.com" <pkalever@redhat.com>,
	"pkarampu@redhat.com" <pkarampu@redhat.com>,
	"atumball@redhat.com" <atumball@redhat.com>,
	"sabose@redhat.com" <sabose@redhat.com>,
	"mchristi@redhat.com" <mchristi@redhat.com>
Subject: Re: [PATCH v4 0/3] uio: fix potential crash bug
Date: Mon, 16 Jul 2018 10:09:41 +0800	[thread overview]
Message-ID: <095acd45-675d-b9c3-244a-d1b6cdc1e8f0@redhat.com> (raw)
In-Reply-To: <7c0ae0c9-2af6-c7c3-49b0-24302584a24d@alliedtelesis.co.nz>

On 2018/7/13 4:34, Hamish Martin wrote:
> Hi Xiubo,
>
> Tested-by: Hamish Martin <hamish.martin@alliedtelesis.co.nz>
>
> I see these were already merged into Linus' tree but I wanted to let you
> know that I tested v4.18-rc4 (which contains these three patches) and
> the issue which led to my original series is still fixed and this patch
> series of yours has caused no regression in our scenario. This was
> tested on PPC 64 bit system (NXP T2081).
Hi Hamish,

Cool and thanks very much for your testing about this.

BRs
Xiubo


> Thanks for resolving that.
>
> Regards,
> Hamish M.
>
> On 07/07/2018 02:05 PM, xiubli@redhat.com wrote:
>> From: Xiubo Li <xiubli@redhat.com>
>>
>> V2:
>> - resend it with some small fix
>>
>> V3:
>> - switch to use request_threaded_irq
>>
>> V4:
>> - remove useless checking code, Thanks Mike.
>> - Thanks very much for the review from Hamish and Mike.
>>
>>
>> Xiubo Li (3):
>>     uio: use request_threaded_irq instead
>>     uio: change to use the mutex lock instead of the spin lock
>>     uio: fix crash after the device is unregistered
>>
>>    drivers/uio/uio.c          | 139 +++++++++++++++++++++++++++++++++------------
>>    include/linux/uio_driver.h |   2 +-
>>    2 files changed, 104 insertions(+), 37 deletions(-)
>>


      reply	other threads:[~2018-07-16  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-07  2:05 xiubli
2018-07-07  2:05 ` [PATCH v4 1/3] uio: use request_threaded_irq instead xiubli
2018-07-07  2:05 ` [PATCH v4 2/3] uio: change to use the mutex lock instead of the spin lock xiubli
2018-07-07  2:05 ` [PATCH v4 3/3] uio: fix crash after the device is unregistered xiubli
2018-07-12 20:34 ` [PATCH v4 0/3] uio: fix potential crash bug Hamish Martin
2018-07-16  2:09   ` Xiubo Li [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=095acd45-675d-b9c3-244a-d1b6cdc1e8f0@redhat.com \
    --to=xiubli@redhat.com \
    --cc=Hamish.Martin@alliedtelesis.co.nz \
    --cc=atumball@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchristi@redhat.com \
    --cc=pkalever@redhat.com \
    --cc=pkarampu@redhat.com \
    --cc=sabose@redhat.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

all inboxes | Powered by JetHome®