linux-kernel - rpc.rwalld is broken in 2.6.33.16

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>] [day] [month] [year] [list]

Date:	Mon, 29 Aug 2011 17:40:01 -0700 (PDT)
From:	Darrell Anderson <humanreadable@...oo.com>
To:	linux-kernel@...r.kernel.org
Subject: rpc.rwalld is broken in 2.6.33.16

Greetings,

I am using Slackware 13.1 and the 2.6.33.x kernel. Recently I compiled and installed the 2.6.33.18 kernel and noticed rpc.rwalld will not start or run. There are no error messages and the exit code when run directly from the command line is zero.

rpc.rwalld runs fine under 2.6.33.15.

Recompiling netkit-rwall against 2.6.33.18 made no difference.

I'll take a wild guess this is where the breakage occurred (2.6.33.16 change log):

commit 273f86df6960cfc9e6402f0eca7d5b77204c5dd8
Author: Trond Myklebust <Trond.Myklebust@...app.com>
Date:   Fri Jun 17 10:14:59 2011 -0400
SUNRPC: Ensure the RPC client only quits on fatal signals
commit 5afa9133cfe67f1bfead6049a9640c9262a7101c upstream.
Fix a couple of instances where we were exiting the RPC client on
arbitrary signals. We should only do so on fatal signals.
Signed-off-by: Trond Myklebust <Trond.Myklebust@...app.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>

I compiled and installed the 2.6.33.16 kernel and confirmed rpc.rwalld fails to run there. So the change occurred from 2.6.33.15 to 2.6.33.16.

I am not a member of this list nor am I a kernel developer.

Please contact me at this email address if I can help further or provide additional information.

Thanks for all your great work and time.

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