From: Tejun Heo <tj@kernel.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Borislav Petkov <petkovbb@gmail.com>
Subject: Re: 2.9.29.2: ide-tape: panic when probing device at boot
Date: Sun, 10 May 2009 09:58:10 +0900 [thread overview]
Message-ID: <4A0626A2.4060202@kernel.org> (raw)
In-Reply-To: <200905091757.49697.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> [ cc:ing linux-ide and knowledgeable people ]
>
> Borislav/Tejun:
>
> Is the 2.6.29 problem the same thing that was fixed recently?
>
> Should I just push commit 1e75540ec5202cae63cd238c86bd880e3d496546
> ("ide-tape: remove back-to-back REQUEST_SENSE detection") to Linus
> or there is more needed to bring ide-tape to the world of living?
The oops will probably fixed the above commit. I don't have much idea
about the DMA problem on 2.6.24 tho. But even with the above commit
fixed, I doubt it would work. The buffer allocation code is broken
and reliably triggered OOM on my test machine. While trying to locate
the bug, I realized the complex code didn't do much good to begin with
and just stripped it down, so I didn't actually tracked down the
actual bug && the patch to simplify buffer management is way too large
for 2.6.29, so unless someone is willing to hunt down the bug just for
2.6.29, we're kind of stuck. :-(
Thanks.
--
tejun
prev parent reply other threads:[~2009-05-10 0:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 7:00 2.9.29.2: ide-tape: panic when probing device at boot Jonathan Woithe
2009-05-09 15:57 ` Bartlomiej Zolnierkiewicz
2009-05-09 16:18 ` Borislav Petkov
2009-05-10 0:59 ` Tejun Heo
2010-01-04 1:15 ` Jonathan Woithe
2010-01-04 5:47 ` Borislav Petkov
2010-01-05 5:38 ` Jonathan Woithe
2010-03-12 1:31 ` Jonathan Woithe
2010-01-04 5:52 ` Robert Hancock
2009-05-18 5:32 ` Jonathan Woithe
2009-05-18 6:30 ` Borislav Petkov
2009-05-18 13:18 ` Borislav Petkov
2009-05-10 0:58 ` Tejun Heo [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=4A0626A2.4060202@kernel.org \
--to=tj@kernel.org \
--cc=bzolnier@gmail.com \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@gmail.com \
/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