From: Greg KH <gregkh@linuxfoundation.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: peter@hurleysoftware.com, jslaby@suse.com,
linux-kernel@vger.kernel.org, jslaby@suse.cz,
andreyknvl@google.com, kcc@google.com, glider@google.com,
paulmck@linux.vnet.ibm.com, hboehm@google.com
Subject: Re: [PATCH] tty: fix data race in tty_buffer_flush
Date: Tue, 8 Sep 2015 15:11:23 -0700 [thread overview]
Message-ID: <20150908221123.GA22446@kroah.com> (raw)
In-Reply-To: <1441716506-110551-1-git-send-email-dvyukov@google.com>
On Tue, Sep 08, 2015 at 02:48:26PM +0200, Dmitry Vyukov wrote:
> tty_buffer_flush frees not acquired buffers.
> As the result, for example, read of b->size in tty_buffer_free
> can return garbage value which will lead to a huge buffer
> hanging in the freelist. This is just the benignest
> manifestation of freeing of a not acquired object.
> If the object is passed to kfree, heap can be corrupted.
>
> Acquire visibility over the buffer before freeing it.
>
> The data race was found with KernelThreadSanitizer (KTSAN).
>
> Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
> ---
> drivers/tty/tty_buffer.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
What changed from the last version? Why should I take this one and not
the other? What order do these go in?
Please please please version your patches, and number them in a series
so that I know what to apply, and in what order, and what changed
between versions. Please read Documentation/SubmittingPatches for all
the details about this.
I've now dropped all of your patches from my queue, please resend them
all properly.
thanks,
greg k-h
next prev parent reply other threads:[~2015-09-08 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 12:26 Dmitry Vyukov
2015-09-08 12:48 ` Dmitry Vyukov
2015-09-08 22:11 ` Greg KH [this message]
2015-09-16 1:38 ` Peter Hurley
2015-09-16 18:20 ` Dmitry Vyukov
2015-09-17 10:28 ` Dmitry Vyukov
2015-09-17 10:59 ` Dmitry Vyukov
2015-09-17 12:51 ` Greg Kroah-Hartman
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=20150908221123.GA22446@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hboehm@google.com \
--cc=jslaby@suse.com \
--cc=jslaby@suse.cz \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peter@hurleysoftware.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
Powered by JetHome