From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-kernel@vger.kernel.org,
ext4 development <linux-ext4@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Al Viro <viro@ZenIV.linux.org.uk>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] fs: make generic_block_fiemap sig-tolerant PING2...
Date: Thu, 18 Dec 2014 15:12:47 -0800 [thread overview]
Message-ID: <20141218151247.b6ccd73351f40db66818c07e@linux-foundation.org> (raw)
In-Reply-To: <87zjavehsx.fsf@openvz.org>
On Wed, 10 Dec 2014 16:49:18 +0300 Dmitry Monakhov <dmonakhov@openvz.org> wrote:
>
> Hello. Someone please take care of this patch.
>
> W/o that patch unprivileged user may abuse system resources simply by spawning
> wast number of unkilable busyloops (works on ext2/ext3):
>
> truncate --size 1T test
> for ((i=0;i<1024;i++))
> do
> filefrag test > /dev/null &
> done
>
> >> --- a/fs/ioctl.c
> >> +++ b/fs/ioctl.c
> >> @@ -379,6 +379,11 @@ int __generic_block_fiemap(struct inode *inode,
> >> past_eof = true;
> >> }
> >> cond_resched();
> >> + if (fatal_signal_pending(current)) {
> >> + ret = -EINTR;
> >> + break;
> >> + }
> >> +
> >> } while (1);
> >>
Is FIEMAP documented anywhere (manpage)? If so, that will need an
update.
next prev parent reply other threads:[~2014-12-18 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1413552269-32203-1-git-send-email-dmonakhov@openvz.org>
[not found] ` <871toikt7c.fsf@openvz.org>
2014-12-10 13:49 ` [PATCH] fs: make generic_block_fiemap sig-tolerant PING2 Dmitry Monakhov
2014-12-18 23:12 ` Andrew Morton [this message]
2014-12-19 9:13 ` Dmitry Monakhov
2014-12-19 21:33 ` Andrew Morton
2014-12-19 23:38 ` Andreas Dilger
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=20141218151247.b6ccd73351f40db66818c07e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=tytso@mit.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox