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: <E1Lypk4-0004it-BA@pomaz-ex.szeredi.hu>
Date:	Tue, 28 Apr 2009 18:01:08 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	teheo@...e.de
CC:	linux-kernel@...r.kernel.org, greg@...ah.com, miklos@...redi.hu,
	tiwai@...e.de, fuse-devel@...ts.sourceforge.net
Subject: Re: [ANNOUNCE] OSS Proxy 1.2 using CUSE

>From the README:

| ALSA contains OSS emulation but sadly the emulation is behind
| multiplexing layer (which is in userland) which means that if your
| sound card doesn't support multiple audio streams, only either one of
| ALSA or OSS interface would be usable at any given moment.

This seems to imply (and I was hoping very much) that this won't be a
limitation of a CUSE based OSS Proxy.  But at the moment I'm finding
that while ossp is doing some playback other ALSA apps cannot start
playback and vice versa.

In fact if something else is playing though ALSA and I start a
playback through ossp, then ossp will print some errors, return EIO
and get into a bad state, that it recoveres from only by starting the
playback twice more (after stopping the other playback through ALSA).

ossp-padsp[mszeredi:24123]  ERR: pa_stream_write() failed (Connection terminated)
osspd  ERR: failed to read_fill 16 bytes from fd 7 (Connection reset by peer)
osspd WARN: S[1/24122] communication with slave failed (can't read reply: Connection reset by peer)
E: socket-client.c: socket(): Address family not supported by protocol
E: context.c: waitpid(): No child processes
ossp-padsp[mszeredi:24130]  ERR: failed to connect context, state=5 (Bad state)

Thanks,
Miklos
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ