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: <20081014.163359.110730186.davem@davemloft.net>
Date:	Tue, 14 Oct 2008 16:33:59 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	afleming@...il.com
Cc:	afleming@...escale.com, netdev@...r.kernel.org
Subject: Re: [PATCH] Change S390 anti-dependency to CONFIG_GENERIC_HARDIRQS
 dependency

From: "Andy Fleming" <afleming@...il.com>
Date: Tue, 14 Oct 2008 18:21:44 -0500

> Argh.  From what I could see, we have request_irq, free_irq,
> disable_irq, enable_irq, and disable_irq_nosync.  For the PHYLIB, it
> shouldn't be difficult to modify things so that it doesn't compile in
> interrupt support if the system doesn't support them.  Shouldn't, that
> is, if there's some config option that tells me whether those
> functions exist.

I think this whole situation with s390 is rediculious.

If s390 is weird and lacks these fundamental things, that's fine.
What isn't fine is how we're handling this.

No code should care or even be aware of this.

S390 should simply provide a set of dummy DMA and interrupt interface
stubs that always fail and return an error value.

Then we can get rid of this S390 Kconfig stuff which has been spewed
all over the place.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ