linux-kernel - Re: 4.0-rc1: Oops on eject of CF card in PCMCIA slot

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 2 Mar 2015 11:57:25 +0000
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Pavel Machek <pavel@....cz>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	linux-pcmcia@...ts.infradead.org, axboe@...nel.dk
Subject: Re: 4.0-rc1: Oops on eject of CF card in PCMCIA slot

On Sat, 28 Feb 2015 00:08:52 +0100
Pavel Machek <pavel@....cz> wrote:

> Hi!
> 
> It seems that pcmcia was unhappy even before, but eject definitely
> oopsed it.
> 
> Any ideas?

Probably a PCMCIA not a block layer change - well I guess could be
either. I fixed a pile of PCMCIA bugs and also reworked the allocator for
pure PCI boxes so it didn't do various bad things.

Can you tweak drivers/pcmcia/Kconfig for config YENTA and make

        select PCCARD_PCI if PCMCIA !=n && !ISA   

instead do

	select PCCARD_NONSTATIC if PCMCIA !=n && !ISA

rebuild and re-test

The tracel looks like a block layer bug, but it would be nice to know if
its one that PCMCIA used it hide, or its in fact potentially something
else.

Do you have any other I/O port based PCMCIA device you can insert/eject
in that machine ?

Alan
--
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/