linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Andrew Liu" <shengping.liu@windriver.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Fix a potential issue in mpc52xx uart driver
Date: Thu, 1 May 2008 12:07:06 -0600	[thread overview]
Message-ID: <fa686aa40805011107p3b3ed242ue79849719961f8db@mail.gmail.com> (raw)
In-Reply-To: <4816CFF9.5030505@windriver.com>

On Tue, Apr 29, 2008 at 1:36 AM, Andrew Liu <shengping.liu@windriver.com> wrote:
> mpc52xx_uart_int and __uart_put_char both try to acquire the
>  port->lock. Therefore the function sequence of:
>
>  mpc52xx_uart_int--> ...-->flush_to_ldisc-->...-->__uart_put_char
>
>  can potentially trigger a deadlock. To avoid this deadlock a fix
>  similar to that found in the 8250.c serial driver is applied. The
>  deadlock is avoided by releasing the lock before pushing a buffer
>  and reacquiring it when completed.
>
>  Signed-off-by: Andrew Liu <shengping.liu@windriver.com>

Your patch is whitespace damaged and does not apply (tabs have been
converted to spaces).  It was trivial so I've applied it manually, but
please be careful when posting future patches.

Thanks,
g.

>
>  diff --git a/drivers/serial/mpc52xx_uart.c b/drivers/serial/mpc52xx_uart.c
>  index d93b357..5f95e53 100644
>  --- a/drivers/serial/mpc52xx_uart.c
>  +++ b/drivers/serial/mpc52xx_uart.c
>  @@ -783,7 +783,9 @@ mpc52xx_uart_int_rx_chars(struct uart_port *port)
>                 }
>         }
>
>  +       spin_unlock(&port->lock);
>         tty_flip_buffer_push(tty);
>  +       spin_lock(&port->lock);
>
>         return psc_ops->raw_rx_rdy(port);
>   }
>



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

      reply	other threads:[~2008-05-01 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29  7:36 [PATCH] Fix a potential issue in mpc52xx uart driver Andrew Liu
2008-05-01 18:07 ` Grant Likely [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=fa686aa40805011107p3b3ed242ue79849719961f8db@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=shengping.liu@windriver.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).