All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxim Patlasov <mpatlasov@parallels.com>
To: Konstantin Khlebnikov <koct9i@gmail.com>,
	Roman Gushchin <klamm@yandex-team.ru>
Cc: <fuse-devel@lists.sourceforge.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [fuse-devel] [PATCH] fuse: break infinite loop in fuse_fill_write_pages()
Date: Fri, 2 Oct 2015 12:27:45 -0700	[thread overview]
Message-ID: <560EDAB1.5090605@parallels.com> (raw)
In-Reply-To: <CALYGNiPt+6GB5DfvuPWHY1yJQFFsE3UWGdvhotzGeif2zdBrGA@mail.gmail.com>

On 10/02/2015 04:21 AM, Konstantin Khlebnikov wrote:
> Bump. Add more peopple in CC.
>
> On Mon, Sep 21, 2015 at 1:02 PM, Roman Gushchin <klamm@yandex-team.ru> wrote:
>> I got a report about unkillable task eating CPU. Thge further
>> investigation shows, that the problem is in the fuse_fill_write_pages()
>> function. If iov's first segment has zero length, we get an infinite
>> loop, because we never reach iov_iter_advance() call.

iov_iter_copy_from_user_atomic() eventually calls iterate_iovec(). The 
latter silently consumes zero-length iov. So I don't think "iov's first 
segment has zero length" can cause infinite loop.

Thanks,
Maxim

>>
>> Fix this by calling iov_iter_advance() before repeating an attempt to
>> copy data from userspace.
>>
>> A similar problem is described in 124d3b7041f ("fix writev regression:
>> pan hanging unkillable and un-straceable").
>>
>> Signed-off-by: Roman Gushchin <klamm@yandex-team.ru>
>> Cc: Miklos Szeredi <miklos@szeredi.hu>
>> ---
>>   fs/fuse/file.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
>> index f523f2f..195476a 100644
>> --- a/fs/fuse/file.c
>> +++ b/fs/fuse/file.c
>> @@ -1049,6 +1049,7 @@ static ssize_t fuse_fill_write_pages(struct fuse_req *req,
>>                  tmp = iov_iter_copy_from_user_atomic(page, ii, offset, bytes);
>>                  flush_dcache_page(page);
>>
>> +               iov_iter_advance(ii, tmp);
>>                  if (!tmp) {
>>                          unlock_page(page);
>>                          page_cache_release(page);
>> @@ -1061,7 +1062,6 @@ static ssize_t fuse_fill_write_pages(struct fuse_req *req,
>>                  req->page_descs[req->num_pages].length = tmp;
>>                  req->num_pages++;
>>
>> -               iov_iter_advance(ii, tmp);
>>                  count += tmp;
>>                  pos += tmp;
>>                  offset += tmp;
>> --
>> 2.4.3
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
> ------------------------------------------------------------------------------
> _______________________________________________
> fuse-devel mailing list
> fuse-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fuse-devel


  reply	other threads:[~2015-10-02 19:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 10:02 [PATCH] fuse: break infinite loop in fuse_fill_write_pages() Roman Gushchin
2015-10-02 11:21 ` Konstantin Khlebnikov
2015-10-02 19:27   ` Maxim Patlasov [this message]
2015-10-02 22:04     ` [fuse-devel] " Andrew Morton
2015-10-03  1:58       ` Konstantin Khlebnikov
2015-10-05 18:37         ` Maxim Patlasov
2015-10-12 13:33           ` [PATCH v2] " Roman Gushchin
2015-11-10 14:41             ` Miklos Szeredi

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=560EDAB1.5090605@parallels.com \
    --to=mpatlasov@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=klamm@yandex-team.ru \
    --cc=koct9i@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=viro@zeniv.linux.org.uk \
    /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.