From: Andrew Morton <akpm@osdl.org>
To: Jens Axboe <axboe@suse.de>
Cc: solt2@dns.toxicfilms.tv, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup
Date: Tue, 8 Feb 2005 01:44:33 -0800 [thread overview]
Message-ID: <20050208014433.42320fc4.akpm@osdl.org> (raw)
In-Reply-To: <20050208093713.GC15985@suse.de>
Jens Axboe <axboe@suse.de> wrote:
>
> > ->axboe!
>
> :-)
>
> The thing wants a rewrite. Ideally the serializing point would be a
> special request. The patch is still better than nothing right now, it's
> really easy to hang the device with hdparm in -linus since it's
> impossible to guess when it is safe to issue tuning actions from user
> space.
I'm not sure which is worse, really. I've never hung an interface with
hdparm, nor seen any reports of it. Making I/O errors deadly rather hurts.
Will it happen on all I/O errors, or was this a special case?
next prev parent reply other threads:[~2005-02-08 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 7:15 2.6.11-rc3-mm1 bad scheduling while atomic + lockup Maciej Soltysiak
2005-02-07 20:19 ` Hans Reiser
2005-02-07 20:59 ` Re[2]: " Maciej Soltysiak
2005-02-08 9:00 ` Andrew Morton
2005-02-08 9:37 ` Jens Axboe
2005-02-08 9:44 ` Andrew Morton [this message]
2005-02-08 9:46 ` Jens Axboe
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=20050208014433.42320fc4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=solt2@dns.toxicfilms.tv \
/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