From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Alex Bligh <alex@alex.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Local DoS through write heavy I/O on CFQ & Deadline
Date: Thu, 11 Oct 2012 14:46:34 +0100 [thread overview]
Message-ID: <20121011144634.7017e270@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <0B138F62-16BF-4295-9AD9-64C0BB39FCE2@alex.org.uk>
> We have reproduced this on multiple hardware environments, using 3.2
> (/proc/version_signature gives "Ubuntu 3.2.0-29.46-generic 3.2.24").
> Anecdotally we believe the situation has worsened since 3.0.
I've certainly seen this on 3.0 and 3.2, but do you still see it on
3.5/6 ?
next prev parent reply other threads:[~2012-10-11 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 12:23 Local DoS through write heavy I/O on CFQ & Deadline Alex Bligh
2012-10-11 13:46 ` Alan Cox [this message]
2012-10-12 12:57 ` Alex Bligh
2012-10-12 13:30 ` Michal Hocko
2012-10-12 14:48 ` Alex Bligh
2012-10-12 14:58 ` Michal Hocko
2012-10-12 16:29 ` Alex Bligh
2012-10-13 13:53 ` Hillf Danton
2012-10-13 19:33 ` Alex Bligh
2012-10-14 2:43 ` Hillf Danton
2012-10-15 8:17 ` Michal Hocko
2012-10-18 21:28 ` Jan Kara
2012-10-18 22:13 ` Chris Friesen
2012-10-18 22:24 ` Jan Kara
2012-10-14 21:17 ` Dave Chinner
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=20121011144634.7017e270@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alex@alex.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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