Re: sunrpc/clnt.c: BUG kmalloc-256 (Not tainted): Poison overwritten

[Toralf FÃrster]

On 07/15/2013 05:01 AM, Myklebust, Trond wrote:
> On Sun, 2013-07-14 at 10:02 +0200, Toralf FÃrster wrote:
>> This bisected commit produces at a 32 bit user mode linux guest the attached BUG :
>>
>> commit eeee245268c951262b861bc1be4e9dc812352499
>> Author: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
>> Date:   Wed Jul 10 15:33:01 2013 -0400
>>
>>     SUNRPC: Fix a deadlock in rpc_client_register()
>>
>>     Commit 384816051ca9125cd54750e59c780c2a2655fa4f (SUNRPC: fix races on
>>     PipeFS MOUNT notifications) introduces a regression when we call
>>     rpc_setup_pipedir() with RPCSEC_GSS as the auth flavour.
>>
>>     By calling rpcauth_create() while holding the sn->pipefs_sb_lock, we
>>     end up deadlocking in gss_pipes_dentries_create_net().
>>     Fix is to register the client and release the mutex before calling
>>     rpcauth_create().
>>
>>     Reported-by: Weston Andros Adamson <dros@xxxxxxxxxx>
>>     Tested-by: Weston Andros Adamson <dros@xxxxxxxxxx>
>>     Cc: Stanislav Kinsbursky <skinsbursky@xxxxxxxxxxxxx>
>>     Cc: <stable@xxxxxxxxxxxxxxx> # : 3848160: SUNRPC: fix races on PipeFS MOUNT
>>     Cc: <stable@xxxxxxxxxxxxxxx> # : e73f4cc: SUNRPC: split client creation
>>     Signed-off-by: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
>>
>>
>>
>>
>>
>>
>> 2013-07-13T22:09:07.000+02:00 trinity sm-notify[1042]: Version 1.2.6 starting
>> 2013-07-13T22:09:07.000+02:00 trinity sm-notify[1042]: Backgrounding to notify hosts...
>> 2013-07-13T22:09:07.000+02:00 trinity sm-notify[1043]: Running as root.  chown /var/lib/nfs to choose different user
>> 2013-07-13T22:09:10.000+02:00 trinity mount[1047]: mount to NFS server 'n22stab4' failed: No route to host, retrying
>> 2013-07-13T22:09:11.000+02:00 trinity dhcpcd[971]: eth0: sending IPv6 Router Solicitation
>> 2013-07-13T22:09:11.000+02:00 trinity dhcpcd[971]: eth0: no IPv6 Routers available
>> 2013-07-13T22:09:13.000+02:00 trinity mount[1048]: mount to NFS server 'n22stab4' failed: No route to host, retrying
>> 2013-07-13T22:09:13.647+02:00 trinity kernel: =============================================================================
>> 2013-07-13T22:09:13.647+02:00 trinity kernel: BUG kmalloc-256 (Not tainted): Poison overwritten
>> 2013-07-13T22:09:13.647+02:00 trinity kernel: -----------------------------------------------------------------------------

<snip>

>> 2013-07-13T22:09:13.647+02:00 trinity kernel:

> Does the attached patch fix the problem?

Yes.

And it solves another related problem too : a soft lookup of CPU0 during
shutdown of the UML guest

:-)



-- 
MfG/Sincerely
Toralf FÃrster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/