Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1352001

Re: sigaltstack breaks swapcontext()

From One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Newsgroups linux.kernel
Subject Re: sigaltstack breaks swapcontext()
Date 2016-03-07 22:40 +0100
Message-ID <rab2F-8kT-1@gated-at.bofh.it> (permalink)
References (5 earlier) <qOQPf-6LO-1@gated-at.bofh.it> <ra9Dz-7xE-3@gated-at.bofh.it> <raaJl-8cF-35@gated-at.bofh.it> <raaT0-8gx-13@gated-at.bofh.it> <rab2F-8kT-3@gated-at.bofh.it>
Organization Intel Corporation

Show all headers | View raw

> Anyway, maybe Linus or the x86 maintainers have some idea of how AC is
> used.  If there are people who use it for a whole program and if libc
> can survive the experience, then they might expect even signal
> handlers to run with AC set.  But if they're sane and protect just
> critical pieces of code being tested with AC, we could be polite and
> clear AC on signal handler entry.

No idea about AC and signals but the main use I have seen is type
checking, particularly in old 16bit code.

Basically code does add type to address, deference. If the type is wrong
for the address you get an alignment trap.

Alan

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: sigaltstack breaks swapcontext() Stas Sergeev <stsp@list.ru> - 2016-03-07 21:10 +0100
  Re: sigaltstack breaks swapcontext() Andy Lutomirski <luto@amacapital.net> - 2016-03-07 22:20 +0100
    Re: sigaltstack breaks swapcontext() Stas Sergeev <stsp@list.ru> - 2016-03-07 22:30 +0100
      Re: sigaltstack breaks swapcontext() One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> - 2016-03-07 22:40 +0100
      Re: sigaltstack breaks swapcontext() Andy Lutomirski <luto@amacapital.net> - 2016-03-07 22:40 +0100
        Re: sigaltstack breaks swapcontext() Stas Sergeev <stsp@list.ru> - 2016-03-07 22:50 +0100

csiph-web