From: Tyler Montbriand <tsm@accesscomm.ca>
To: jgarzik@pobox.com
Cc: linux-ide@vger.kernel.org
Subject: sata_sil on amd64
Date: Sat, 22 Jan 2005 19:19:35 -0600 [thread overview]
Message-ID: <200501221919.35710.tsm@accesscomm.ca> (raw)
I have been stuck using kernel 2.6.4 for the last year or so for various
reasons, and now I'm in a vicious catch-22. If I don't upgrade, I can't use
NPTL, therefore my system will continue to be susceptible to the
sigqueue-overflow flaw in linuxthreads. But if I do upgrade, problems in
>0.53 sata_sil implementations halt my system in a matter of minutes with
dmesg entries about imaginary bad blocks.
0.53 probably has it's own flaws, but it's been rock-solid running a single
drive on my computer for a year. How feasible would it be to forward-port
this version to a newer kernel, say 2.6.10? If I fix the header problems
could it work, or is .10 too structurally different from .4?
next reply other threads:[~2005-01-23 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 1:19 Tyler Montbriand [this message]
2005-01-23 16:29 ` sata_sil on amd64 Bartlomiej Zolnierkiewicz
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=200501221919.35710.tsm@accesscomm.ca \
--to=tsm@accesscomm.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).