linux-kernel - [solution exits] no PCMCIA in 4.0-rc3

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]

Date:	Tue, 10 Mar 2015 21:31:58 +0100
From:	Pavel Machek <pavel@....cz>
To:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	linux-pcmcia@...ts.infradead.org, axboe@...nel.dk
Subject: [solution exits] no PCMCIA in 4.0-rc3

On Mon 2015-03-02 11:57:25, One Thousand Gnomes wrote:
> 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

If I do that, it breaks compile. If I do that, and delete "config
PCCARD_PCI", it fixes PCMCIA. Thanks!

> 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.

Yeah the trace was from 3.18. 4.0 is ok with this regard.

									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/