linux-kernel - Re: avr32: handle

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: <CAF8ieYV_3skMFo4Mc59hX1g1tFEjg8Fjnag36ZQwU9w=CPkLLQ@mail.gmail.com>
Date:	Mon, 15 Aug 2011 22:55:45 -0700
From:	Håvard Skinnemoen <hskinnemoen@...il.com>
To:	Matt Fleming <matt@...sole-pimps.org>
Cc:	Hans-Christian Egtvedt <egtvedt@...fundet.no>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: avr32: handle_signal() bug?

Hi,

Sorry for taking so long to test this.

On Mon, Aug 8, 2011 at 3:25 AM, Matt Fleming <matt@...sole-pimps.org> wrote:
> On Sun, 2011-08-07 at 10:20 -0700, Håvard Skinnemoen wrote:
>> Looks good to me. I'm not sure how to test it though...I can try to
>> build a kernel, run it on my board and see if it explodes, but I
>> suspect this bug is a lot more subtle than that.
>
> I suspect the best test would be one that makes use of SA_NODEFER.
> Something like this,

Thanks for the test. Unfortunately, the result is the same regardless
of whether I apply the patches or not. In both cases:

/root # ./nodefer
SIGUSR2: not blocked
SIGTERM: not blocked

On my desktop, it behaves as expected:

$ ./nodefer-pc
SIGUSR2: blocked
SIGTERM: blocked

Your patch doesn't appear to do any harm though, and it looks correct
to me. Perhaps there's another bug lurking somewhere as well. Some
preliminary debugging makes me suspicious about libc, but I can't tell
for sure yet.

Havard
--
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/