linux-kernel - Re: [PATCH v4 05/15] h8300: Process and signal

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]

Message-ID: <87wq3a31rf.wl-ysato@users.sourceforge.jp>
Date:	Sun, 22 Feb 2015 15:21:08 +0900
From:	Yoshinori Sato <ysato@...rs.sourceforge.jp>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH v4 05/15] h8300: Process and signal

At Sat, 21 Feb 2015 09:51:23 +0000,
Al Viro wrote:
> 
> On Sat, Feb 21, 2015 at 04:53:49PM +0900, Yoshinori Sato wrote:
> 
> > +static inline void *
> > +get_sigframe(struct k_sigaction *ka, struct pt_regs *regs, size_t frame_size)
> > +{
> > +	unsigned long usp;
> > +
> > +	/* Default to using normal stack.  */
> > +	usp = rdusp();
> > +
> > +	/* This is the X/Open sanctioned signal stack switching.  */
> > +	if (ka->sa.sa_flags & SA_ONSTACK) {
> > +		if (!sas_ss_flags(usp))
> > +			usp = current->sas_ss_sp + current->sas_ss_size;
> > +	}
> 
> Use sigsp(), please.  Pass ksig to that sucker and it'll become
> 	return (void *)((sigsp(rdusp, ksig) - frame_size) & -8UL);

OK.

> 
> > +static void do_signal(struct pt_regs *regs)
> > +	 * We want the common case to go fast, which
> > +	 * is why we may in certain cases get here from
> > +	 * kernel mode. Just return without doing anything
> > +	 * if so.
> > +	 */
> > +	if ((regs->ccr & 0x10))
> > +		return;
> 
> Can we get there in kernel mode, actually?

It case checking for entry.S
Removed.

Thanks.

-- 
Yoshinori Sato
<ysato@...rs.sourceforge.jp>
--
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/