linux-kernel - Re: BUG in 2.6.22-rc2-mm1: Parts of Alsa sound architecture broken

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]

Message-Id: <1180471146.9509.115.camel@localhost>
Date:	Tue, 29 May 2007 17:39:06 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	Takashi Iwai <tiwai@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Jaroslav Kysela <perex@...e.cz>
Subject: Re: BUG in 2.6.22-rc2-mm1: Parts of Alsa sound architecture broken

Em Ter, 2007-05-29 às 22:18 +0200, Jan Engelhardt escreveu:
> On May 29 2007 18:41, Takashi Iwai wrote:
> >
> >Well, I find the change of CONFIG_SND to menuconfig is fine, too.
> >But CONFIG_SND_PCI_DRIVERS and others don't make much sense to me.
> >How is it useful at all?
> 
> Hah, I just tell you some of my own experience.
> In summer 2003, I bought the last new machine, and it got these
> shiny new ports they like to call USB. :)
> I did not have much use for it, but I left it on - you never know
> what standard next is the big win of the decade. And actually,
> it did not took long (well, summer 2005) to get my first USB device.
> Still, I am hell as sure I do not have USB-based sound devices
> anytime soon, so it would be cool to deactivate the whole usbsound
> menu at once. I think I said that in the patch description, did not I?

For me, this seems to be a good idea. Makes clear to users what is
inside each menu, improving their notion on what should be deactivated.

> >Anyway, I'd like to confirm that this really works before merging to
> >the ALSA tree.  As Mauro suspected, kconfig seems not working as
> >expected...
> 
> Unfortunately, there are sometimes non-visible options in menus (the
> Networking>QoS menu for example) that, when converted to menuconfig-if-endif,
> also get lost when the menuconfig object is deactivated. In case of QoS, this
> can break compilation. For most subsystems however, it works alright because
> the particular subsystem referencing CONFIG_INVISIBLE_THING is deactivated
> anyway and does not get compiled.
> Such strange menus (like QoS) have not been menuconfigized so far, it's just
> too hard to keep the bits together. As far as other subsystems are concerned,
> please give it some testing.

Hmm... probably, this is what happened with V4L: there are several
invisible items there for selecting some core items.

In the case of V4L, the problem is that, when the menu item is
activated, sometimes, kconfig doesn't properly honor module/static link
heritage.

 
Cheers,
Mauro

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