All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Jan Kara <jack@suse.cz>, Al Viro <viro@zeniv.linux.org.uk>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	syzkaller <syzkaller@googlegroups.com>,
	Kostya Serebryany <kcc@google.com>,
	Alexander Potapenko <glider@google.com>,
	Sasha Levin <sasha.levin@oracle.com>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: another uninterruptable hang in sendfile
Date: Mon, 23 Nov 2015 12:56:24 +0100	[thread overview]
Message-ID: <20151123115624.GG23418@quack.suse.cz> (raw)
In-Reply-To: <CACT4Y+aaQ=_+RYDTtNZ25AeGqVu5Djph5YyEtbawjMpKWOypFA@mail.gmail.com>

On Fri 20-11-15 17:16:06, Dmitry Vyukov wrote:
> Hello,
> 
> On commit 8005c49d9aea74d382f474ce11afbbc7d7130bec (Nov 15).
> 
> The program is:
> 
> // autogenerated by syzkaller (http://github.com/google/syzkaller)
> #define _GNU_SOURCE
> #include <unistd.h>
> #include <sys/syscall.h>
> #include <sys/eventfd.h>
> #include <sys/sendfile.h>
> #include <fcntl.h>
> 
> #define SYS_memfd_create 319
> 
> int main()
> {
>         int r1 = eventfd(0, 0);
>         int r2 = syscall(SYS_memfd_create, "", 0);
>         unsigned long n = 1<<30;
>         fallocate(r2, 0, 0, n);
>         sendfile(r1, r2, 0, n);
>         return 0;
> }
> 
> It can be executed under non-privileged user and creates an unkillable
> process. It probably will terminate eventually, but it can take
> days/weeks. Note that "mm: make sendfile(2) killable"
> 296291cdd1629c308114504b850dc343eabc2782 is merged, so it is something
> different. Though, probably similar.

Thanks for the report. Yes, the nature of the problem is similar but here
we don't hit standard filesystem write path where a signal test is. I'll
send a fix which fixes the issue for me shortly.

BTW, this test actually doesn't hang for me but rather burns CPU all the
time and thus causes also softlockups / RCU stalls. I'll send a fix for
that as well.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2015-11-23 11:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 16:16 another uninterruptable hang in sendfile Dmitry Vyukov
2015-11-23 11:56 ` Jan Kara [this message]

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=20151123115624.GG23418@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=dvyukov@google.com \
    --cc=edumazet@google.com \
    --cc=glider@google.com \
    --cc=kcc@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sasha.levin@oracle.com \
    --cc=syzkaller@googlegroups.com \
    --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.