linux-kernel - Re: [PATCH 0/1][3.13.y-ckt] tty: fix stall caused by missing memory barrier in drivers/tty/n

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 11 Dec 2015 11:00:52 -0800
From:	Kamal Mostafa <kamal@...onical.com>
To:	Joseph Salisbury <joseph.salisbury@...onical.com>
Cc:	kamal.mostafa@...onical.com, tatsu@...jp.nec.com,
	gregkh@...uxfoundation.org, jslaby@...e.com,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 0/1][3.13.y-ckt] tty: fix stall caused by missing memory
 barrier in drivers/tty/n_tty.c

On Tue, 2015-12-08 at 17:11 -0500, Joseph Salisbury wrote:
> Hello,
> 
> Please consider including upstream commit e81107d4c6bd098878af9796b24edc8d4a9524fd
> in the next v3.13.y-ckt release.  This commit was included mainline as of v4.3-rc5.
> It has been tested and confirmed to resolve http://bugs.launchpad.net/bugs/1512815 .
> 
> commit e81107d4c6bd098878af9796b24edc8d4a9524fd
> Author: Kosuke Tatsukawa <tatsu@...jp.nec.com>
> Date:   Fri Oct 2 08:27:05 2015 +0000
> 
>     tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c
> 
> Commit e81107d4 does not apply cleanly to v3.13.y-ckt, so I performed a backport, which is
> in email 1/1.

Thanks very much Joseph.  Queued for 3.13-stable.

 -Kamal


> 
> Sincerely,
> 
> Joseph Salisbury
> 
> 
> 
> 
> Kosuke Tatsukawa (1):
>   tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c
> 
>  drivers/tty/n_tty.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/