linux-kernel - Re: TIF_NOTIFY

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]

Date:	Thu, 19 Nov 2009 17:21:31 +0100
From:	Mikael Pettersson <mikpe@...uu.se>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	linux-m68k <linux-m68k@...r.kernel.org>,
	uClinux development list <uclinux-dev@...inux.org>,
	linux-kernel@...r.kernel.org
Subject: Re: TIF_NOTIFY_RESUME on m68k?

Geert Uytterhoeven writes:
 > Has anyone already looked into TIF_NOTIFY_RESUME support for m68k?

You need to change your entry.S code where it now does single-bit tests
for TIF_SIGPENDING with lsl/jmi do_signal_return, to instead test a 2-bit
(or larger, it that gives better code) flag field for zero/non-zero.
TIF_SIGPENDING and TIF_NOTIFY_RESUME should be alone in that field.
In the non-zero case you should call a new do_notify_resume() written in C,
which will then test TIF_SIGPENDING and TIF_NOTIFY_RESUME just like many
other archs do.

BTW, m68k also lacks TIF_RESTORE_SIGMASK support. You could probably use
the one I added to ARM very recently as a model.

Do current 2.6.3x m68k kernels boot on aranym? Last time I tried aranym
it could only boot som ancient hacked 2.4 kernel, for 2.6 kernels I got
disk detection errors due to what looked like byteswapping issues.
--
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/