linux-kernel - Re: Can not get output of command line on SH

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] [day] [month] [year] [list]

Date:	Mon, 3 Sep 2012 13:24:43 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@...esas.com>
Cc:	Al Viro <viro@...iv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Can not get output of command line on SH

On Mon, Sep 03, 2012 at 11:56:59AM +0900, Nobuhiro Iwamatsu wrote:
> On Fri, Aug 31, 2012 at 10:10 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
> > Smells like broken TIF_NOTIFY_RESUME hookup on sh...  Arrrgh.  Looks like
> > while it is in the relevant masks *and* checked in do_notify_resume() both
> > on 32bit and 64bit variants since commit ab99c733ae73cce31f2a2434f7099564e5a73d95
> > Author: Paul Mundt <lethal@...ux-sh.org>
> > Date:   Wed Jul 30 19:55:30 2008 +0900
> >
> >     sh: Make syscall tracer use tracehook notifiers, add TIF_NOTIFY_RESUME.
> >
> > they are actually *not* reached without simulataneous SIGPENDING, since the
> > actual glue in the callers had not been updated back then and still checks
> > for _TIF_SIGPENDING alone when deciding whether to hit do_notify_resume()
> > or not.  Looks like the following ought to fix that:
> 
> Thanks for your reply and explanation.
> I confirmed that revise this problem with your patch.
> 
> >
> > Signed-off-by: Al Viro <viro@...iv.linux.org.uk>
> Tested-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@...esas.com>
> 
I'll queue it up, thanks!
--
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/