Re: [PATCH] uml: fix hostfs mknod()

2015-12-16 Thread Vegard Nossum
On 12/16/2015 11:17 PM, Richard Weinberger wrote: Am 16.12.2015 um 21:59 schrieb Vegard Nossum: An inverted return value check in hostfs_mknod() caused the function to return success after handling it as an error (and cleaning up). [...] Applied! :-) BTW: How did you create this patch? I

Re: [PATCH] uml: fix hostfs mknod()

2015-12-16 Thread Richard Weinberger
Am 16.12.2015 um 21:59 schrieb Vegard Nossum: > An inverted return value check in hostfs_mknod() caused the function > to return success after handling it as an error (and cleaning up). > > It resulted in the following segfault when trying to bind() a named > unix socket: > > Pid: 198, comm:

[PATCH] uml: fix hostfs mknod()

2015-12-16 Thread Vegard Nossum
An inverted return value check in hostfs_mknod() caused the function to return success after handling it as an error (and cleaning up). It resulted in the following segfault when trying to bind() a named unix socket: Pid: 198, comm: a.out Not tainted 4.4.0-rc4 RIP: 0033:[<61077df6>]

[PATCH] uml: fix hostfs mknod()

2015-12-16 Thread Vegard Nossum
An inverted return value check in hostfs_mknod() caused the function to return success after handling it as an error (and cleaning up). It resulted in the following segfault when trying to bind() a named unix socket: Pid: 198, comm: a.out Not tainted 4.4.0-rc4 RIP: 0033:[<61077df6>]

Re: [PATCH] uml: fix hostfs mknod()

2015-12-16 Thread Vegard Nossum
On 12/16/2015 11:17 PM, Richard Weinberger wrote: Am 16.12.2015 um 21:59 schrieb Vegard Nossum: An inverted return value check in hostfs_mknod() caused the function to return success after handling it as an error (and cleaning up). [...] Applied! :-) BTW: How did you create this patch? I

Re: [PATCH] uml: fix hostfs mknod()

2015-12-16 Thread Richard Weinberger
Am 16.12.2015 um 21:59 schrieb Vegard Nossum: > An inverted return value check in hostfs_mknod() caused the function > to return success after handling it as an error (and cleaning up). > > It resulted in the following segfault when trying to bind() a named > unix socket: > > Pid: 198, comm: