Bug 543968 - Connecting to tcpmux service causes SIGSEGV in xinetd
Summary: Connecting to tcpmux service causes SIGSEGV in xinetd
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xinetd
Version: 12
Hardware: i686
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Jan Zeleny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 801507
TreeView+ depends on / blocked
 
Reported: 2009-12-03 15:44 UTC by Vsevolod Volkov
Modified: 2012-03-08 17:32 UTC (History)
1 user (show)

Fixed In Version: 2.3.14-29.fc12
Clone Of:
: 801507 (view as bug list)
Environment:
Last Closed: 2010-01-22 22:30:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vsevolod Volkov 2009-12-03 15:44:32 UTC
Description of problem:
Connecting to tcpmux service causes SIGSEGV in xinetd.


Version-Release number of selected component (if applicable):
2:2.3.14-28.fc12


How reproducible:
Enable tcpmux service. Create any service with type 'TCPMUX UNLISTED' and without port entry. Restart xinetd. Connect to port 1 at the host.

Steps to Reproduce:
1. Enable tcpmux service in /etc/xinetd.d/tcpmux-server.
2. Create service in /etc/xinetd.d/uptime:
   service uptime
   {
	type		= TCPMUX UNLISTED
	socket_type	= stream
	protocol	= tcp
	wait		= no
	user		= nobody
	server		= /usr/bin/uptime
	disable		= no
   }
3. Restart xinetd.
4. Connect to port 1:
   telnet localhost 1

Actual results:
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

Expected results:
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
uptime
 14:55:54 up 1 day, 27 min,  7 users,  load average: 0.56, 0.81, 0.86
Connection closed by foreign host.

Additional info:
/var/log/messages contains the following lines:
Dec  3 14:55:04 hostname xinetd[30173]: START: tcpmux-server pid=7476 from=...
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {general_handler} (7476) Unexpected signal: 11 (Segmentation fault)
Dec  3 14:55:04 hostname xinetd[7476]: 7476 {bad_signal} Received 10 signals in 1 seconds. Exiting...
Dec  3 14:55:04 hostname xinetd[30173]: EXIT: tcpmux-server status=1 pid=7476 duration=0(sec)

Comment 1 Fedora Update System 2010-01-21 09:57:29 UTC
xinetd-2.3.14-29.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/xinetd-2.3.14-29.fc12

Comment 2 Fedora Update System 2010-01-22 22:29:59 UTC
xinetd-2.3.14-29.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.