All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Tu, Xiaobing" <xiaobing.tu@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Zhang, Yanmin" <yanmin.zhang@intel.com>,
	"Du, Alek" <alek.du@intel.com>, "Zuo, Jiao" <jiao.zuo@intel.com>
Subject: Re: [PATCH] tty: hold lock across tty buffer finding and buffer filling
Date: Thu, 15 Mar 2012 13:26:33 -0700	[thread overview]
Message-ID: <20120315202633.GA23975@kroah.com> (raw)
In-Reply-To: <EE928378561BF1449699C96571234A740FCC580F@SHSMSX102.ccr.corp.intel.com>

On Thu, Mar 15, 2012 at 02:06:43AM +0000, Tu, Xiaobing wrote:
> From: Xiaobing Tu <xiaobing.tu@intel.com>
> 
> tty_buffer_request_room is well protected, but while after it returns,
>  it releases the port->lock. tty->buf.tail might be modified
> by either irq handler or other threads. The patch adds more protection
> by holding the lock across tty buffer finding and buffer filling.
> 
> Signed-off-by: Alek Du <alek.du@intel.com>
> Signed-off-by: Xiaobing Tu <xiaobing.tu@intel.com>
> ---
>  drivers/tty/tty_buffer.c |   85 +++++++++++++++++++++++++++++++++++-----------
>  1 files changed, 65 insertions(+), 20 deletions(-)
>  mode change 100644 => 100755 drivers/tty/tty_buffer.c
> 
> diff --git a/drivers/tty/tty_buffer.c b/drivers/tty/tty_buffer.c
> old mode 100644
> new mode 100755

What?  Why would you change the mode of the file to be executable?

Also, your patch introduces a bunch of trailing whitespace, please run
it through scripts/checkpatch.pl and fix those issues before resending
it.

thanks,

greg k-h

      parent reply	other threads:[~2012-03-15 20:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  2:06 [PATCH] tty: hold lock across tty buffer finding and buffer filling Tu, Xiaobing
2012-03-15 10:08 ` Alan Cox
2012-03-15 10:14   ` Du, Alek
2012-03-15 15:40     ` Alan Cox
2012-03-16  9:43     ` Jiri Slaby
2012-03-16  9:49       ` Du, Alek
2012-03-16  9:57         ` Jiri Slaby
2012-03-16 10:01           ` Du, Alek
2012-03-16 10:04             ` Jiri Slaby
2012-03-16 10:08               ` Du, Alek
2012-03-16 10:22                 ` Jiri Slaby
2012-03-16 11:33                   ` Du, Alek
2012-03-16 12:03                     ` Jiri Slaby
2012-03-16 13:50                       ` Du, Alek
2012-03-16 20:53                         ` Jiri Slaby
2012-03-17  1:05                           ` Alek Du
2012-03-16 23:07                       ` Alan Cox
2012-03-15 20:26 ` gregkh [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=20120315202633.GA23975@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alek.du@intel.com \
    --cc=jiao.zuo@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiaobing.tu@intel.com \
    --cc=yanmin.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.