From: Greg KH <gregkh@linuxfoundation.org>
To: Phi Nguyen <phind.uet@gmail.com>
Cc: jirislaby@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
syzbot+97388eb9d31b997fe1d0@syzkaller.appspotmail.com
Subject: Re: [PATCH] tty: Fix data race between tiocsti() and flush_to_ldisc()
Date: Wed, 18 Aug 2021 16:03:49 +0200 [thread overview]
Message-ID: <YR0TRf+283ujBxbv@kroah.com> (raw)
In-Reply-To: <7323d825-f596-223b-a063-7539a6a57107@gmail.com>
On Sat, Aug 14, 2021 at 02:35:53AM +0800, Phi Nguyen wrote:
> On 8/13/2021 3:33 PM, Greg KH wrote:
> > >
> > > Signed-off-by: Nguyen Dinh Phi <phind.uet@gmail.com>
> > > Reported-by: syzbot+97388eb9d31b997fe1d0@syzkaller.appspotmail.com
> > > ---
> > > drivers/tty/tty_io.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
> > > index e8532006e960..746fe13a2054 100644
> > > --- a/drivers/tty/tty_io.c
> > > +++ b/drivers/tty/tty_io.c
> > > @@ -2307,8 +2307,10 @@ static int tiocsti(struct tty_struct *tty, char __user *p)
> > > ld = tty_ldisc_ref_wait(tty);
> > > if (!ld)
> > > return -EIO;
> > > + tty_buffer_lock_exclusive(tty->port);
> > > if (ld->ops->receive_buf)
> > > ld->ops->receive_buf(tty, &ch, &mbz, 1);
> > > + tty_buffer_unlock_exclusive(tty->port);
> >
> > Did this fix the syzbot reported issue?
> >
> > thanks,
> >
> > greg k-h
> > Yes, this fixed the syzbot reported issue.
>
> The lock is grabbed in flush_to_ldisc() and paste_selection().
> Actually, I follow the document in tty_buffer.c, where it say the callers to
> receive_buff() other than flush_to_ldisc() need to exclude the kworker from
> concurrent use of the line discipline.
>
> And function tiocsti() has the following comment:
> /* FIXME: may race normal receive processing */
> that why I add lock in this function.
As you are fixing this FIXME, please remove it in this patch, otherwise
we will not know it is resolved :)
Can you add that to the change and submit a new version?
Also, this should go to stable kernels, right? Any idea how far back?
thanks,
greg k-h
next prev parent reply other threads:[~2021-08-18 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 19:05 [PATCH] tty: Fix data race between tiocsti() and flush_to_ldisc() Nguyen Dinh Phi
2021-08-13 7:33 ` Greg KH
2021-08-13 18:35 ` Phi Nguyen
2021-08-18 14:03 ` Greg KH [this message]
2021-08-22 16:09 ` Phi Nguyen
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=YR0TRf+283ujBxbv@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phind.uet@gmail.com \
--cc=syzbot+97388eb9d31b997fe1d0@syzkaller.appspotmail.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