All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
Cc: jirislaby@kernel.org, linux-kernel@vger.kernel.org,
	syzbot+3d2c27c2b7dc2a94814d@syzkaller.appspotmail.com
Subject: Re: [PATCH] tty: fix when iov_iter_count() returns 0 in tty_write()
Date: Wed, 17 Feb 2021 16:13:58 +0100	[thread overview]
Message-ID: <YC0ytokrZPUitjVS@kroah.com> (raw)
In-Reply-To: <20210217144347.2962551-1-snovitoll@gmail.com>

On Wed, Feb 17, 2021 at 08:43:47PM +0600, Sabyrzhan Tasbolatov wrote:
> syzbot found WARNING in iov_iter_revert[1] when iov_iter_count() returns 0,
> therefore INT_MAX is passed to iov_iter_revert() causing > MAX_RW_COUNT
> warning.
> 
> static inline ssize_t do_tty_write()
> {
> ..
> 	size_t count = iov_iter_count(from);
> ..
> 		size_t size = count;
> 		if (ret != size)
> 			iov_iter_revert(from, size-ret);
> 
> [1] WARNING: lib/iov_iter.c:1090
> Call Trace:
>  do_tty_write drivers/tty/tty_io.c:967 [inline]
>  file_tty_write.constprop.0+0x55f/0x8f0 drivers/tty/tty_io.c:1048
>  call_write_iter include/linux/fs.h:1901 [inline]
>  new_sync_write+0x426/0x650 fs/read_write.c:518
>  vfs_write+0x791/0xa30 fs/read_write.c:605
>  ksys_write+0x12d/0x250 fs/read_write.c:658
> 
> Fixes: 494e63ee9c("tty: implement write_iter")

Nit, you need a ' ' before your '(' character here, otherwise the
linux-next scripts will complain.

> Reported-by: syzbot+3d2c27c2b7dc2a94814d@syzkaller.appspotmail.com
> Signed-off-by: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
> ---
>  drivers/tty/tty_io.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
> index 816e709afa56..8d6d579ecc3b 100644
> --- a/drivers/tty/tty_io.c
> +++ b/drivers/tty/tty_io.c
> @@ -905,6 +905,9 @@ static inline ssize_t do_tty_write(
>  	ssize_t ret, written = 0;
>  	unsigned int chunk;
>  
> +	if (!count)
> +		return -EINVAL;

According to the man page for write(2), I think this is the wrong error
value to return, unless that is the value that was returned on kernels
before the commit listed above.

Can you verify this?

thanks,

greg k-h

  reply	other threads:[~2021-02-17 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17 14:43 [PATCH] tty: fix when iov_iter_count() returns 0 in tty_write() Sabyrzhan Tasbolatov
2021-02-17 15:13 ` Greg KH [this message]
2021-02-17 15:15   ` Greg KH
2021-02-17 15:55     ` [PATCH v2] " Sabyrzhan Tasbolatov
2021-02-19  9:17       ` Jiri Slaby

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=YC0ytokrZPUitjVS@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snovitoll@gmail.com \
    --cc=syzbot+3d2c27c2b7dc2a94814d@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 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.