[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120427193413.GM6871@ZenIV.linux.org.uk>
Date: Fri, 27 Apr 2012 20:34:13 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Oleg Nesterov <oleg@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
Roland McGrath <roland@...k.frob.com>,
Greg Ungerer <gerg@...inux.org>
Subject: Re: [RFC] TIF_NOTIFY_RESUME, arch/*/*/*signal*.c and all such
On Fri, Apr 27, 2012 at 09:14:53PM +0200, Geert Uytterhoeven wrote:
> On Fri, Apr 27, 2012 at 20:45, Al Viro <viro@...iv.linux.org.uk> wrote:
> >> The only comment I have,
> >> 38671a3e831ed7327affb24d715f98bb99c80e56 m68k: add TIF_NOTIFY_RESUME and handle it
> >> forgets to unexport do_signal().
> >
> > Meh... ??The thing is, there are _two_ of them. ??signal_mm.c and signal_no.c
> > badly need merging, with common stuff moved to signal.c. ??I really hate
>
> Greg recently posted a patch to merge them:
> http://www.spinics.net/lists/linux-m68k/msg04995.html
Nice... BTW, could you comment on
m68k: don't open-code block_sigmask()
m68k: use set_current_blocked in sigreturn/rt_sigreturn
m68k-nommu: do_signal() is only called when returning to user mode
m68k: add TIF_NOTIFY_RESUME and handle it.
in signal.git tree? The last one is really interesting...
Just pick the current tree - one that was there yesterday had a dumb typo
in thread_info.h part, so it wouldn't even compile (TIF_NOTIFE_RESUME
defined instead of TIF_NOTIFY_RESUME ;-/)
--
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/
Powered by blists - more mailing lists