From: Oleg Nesterov <oleg@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lingzhu Xiang <lxiang@redhat.com>,
Roman Rakus <rrakus@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] tty: set_termios/set_termiox should not return -EINTR
Date: Wed, 30 Jan 2013 12:51:53 +0100 [thread overview]
Message-ID: <20130130115153.GA7012@redhat.com> (raw)
In-Reply-To: <20130130114645.GA6622@redhat.com>
On 01/30, Oleg Nesterov wrote:
>
> On 01/29, Jiri Slaby wrote:
> >
> > On 01/29/2013 08:49 PM, Oleg Nesterov wrote:
> > >
> > > Perhaps /bin/bash is buggy too, I do not know. Probably Roman and
> > > Lingzhu can tell more.
> >
> > But I really want to hear more details here (the commit log deserves
> > that). E.g. why it started causing problems right now.
>
> I have no idea, I only saw the test-case yesterday.
But if you ask how this affects /bin/bash, I can quote the description
from Lingzhu,
sigchld.sh (reproducer):
#!/bin/bash
( while :; do kill -CHLD $$ 2>&- || break; done ) &
while :; do
read -p 1 -t 0.3 -d ' '
read -p 2
done
Double free happens in read_builtin, here
FREE (tofree);
-> xfree (orig_input_string);
return (retval);
result:
sigchld.sh: line 4: read: error setting terminal attributes: Interrupted system call
1
*** glibc detected *** ./bash-4.1.2-14.el6/bin/bash: double free or corruption (out): 0x00000000020f45b0 ***
======= Backtrace: =========
(...)
Oleg.
next prev parent reply other threads:[~2013-01-30 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 19:07 [PATCH 0/1] tty: set_termios/set_termiox should not return -EINTR Oleg Nesterov
2013-01-29 19:07 ` [PATCH 1/1] " Oleg Nesterov
2013-01-29 19:35 ` Jiri Slaby
2013-01-29 19:49 ` Oleg Nesterov
2013-01-29 22:01 ` Jiri Slaby
2013-01-30 11:46 ` Oleg Nesterov
2013-01-30 11:51 ` Oleg Nesterov [this message]
2013-01-30 13:01 ` Roman Rakus
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=20130130115153.GA7012@redhat.com \
--to=oleg@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lxiang@redhat.com \
--cc=rrakus@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