linux-kernel - Re: 2.9.29.2: ide-tape: panic when probing device at boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A0626A2.4060202@kernel.org>
Date:	Sun, 10 May 2009 09:58:10 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
CC:	Jonathan Woithe <jwoithe@...sics.adelaide.edu.au>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	Borislav Petkov <petkovbb@...il.com>
Subject: Re: 2.9.29.2: ide-tape: panic when probing device at boot

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/