Skip to content
Snippets Groups Projects
Select Git revision
  • d0e810eeb3d326978f248b8f0233a2f30f58c72d
  • vme-testing default
  • ci-test
  • master
  • remoteproc
  • am625-sk-ov5640
  • pcal6534-upstreaming
  • lps22df-upstreaming
  • msc-upstreaming
  • imx8mp
  • iio/noa1305
  • vme-next
  • vme-next-4.14-rc4
  • v4.14-rc4
  • v4.14-rc3
  • v4.14-rc2
  • v4.14-rc1
  • v4.13
  • vme-next-4.13-rc7
  • v4.13-rc7
  • v4.13-rc6
  • v4.13-rc5
  • v4.13-rc4
  • v4.13-rc3
  • v4.13-rc2
  • v4.13-rc1
  • v4.12
  • v4.12-rc7
  • v4.12-rc6
  • v4.12-rc5
  • v4.12-rc4
  • v4.12-rc3
32 results

machine_kexec.c

Blame
    • Heiko Carstens's avatar
      d0e810ee
      s390/noexec: execute kexec datamover without DAT · d0e810ee
      Heiko Carstens authored
      
      Rebooting into a new kernel with kexec fails (system dies) if tried on
      a machine that has no-execute support. Reason for this is that the so
      called datamover code gets executed with DAT on (MMU is active) and
      the page that contains the datamover is marked as non-executable.
      Therefore when branching into the datamover an unexpected program
      check happens and afterwards the machine is dead.
      
      This can be simply avoided by disabling DAT, which also disables any
      no-execute checks, just before the datamover gets executed.
      
      In fact the first thing done by the datamover is to disable DAT. The
      code in the datamover that disables DAT can be removed as well.
      
      Thanks to Michael Holzheu and Gerald Schaefer for tracking this down.
      
      Reviewed-by: default avatarMichael Holzheu <holzheu@linux.vnet.ibm.com>
      Reviewed-by: default avatarPhilipp Rudo <prudo@linux.vnet.ibm.com>
      Cc: Gerald Schaefer <gerald.schaefer@de.ibm.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Fixes: 57d7f939 ("s390: add no-execute support")
      Cc: <stable@vger.kernel.org> # v4.11+
      Signed-off-by: default avatarHeiko Carstens <heiko.carstens@de.ibm.com>
      d0e810ee
      History
      s390/noexec: execute kexec datamover without DAT
      Heiko Carstens authored
      
      Rebooting into a new kernel with kexec fails (system dies) if tried on
      a machine that has no-execute support. Reason for this is that the so
      called datamover code gets executed with DAT on (MMU is active) and
      the page that contains the datamover is marked as non-executable.
      Therefore when branching into the datamover an unexpected program
      check happens and afterwards the machine is dead.
      
      This can be simply avoided by disabling DAT, which also disables any
      no-execute checks, just before the datamover gets executed.
      
      In fact the first thing done by the datamover is to disable DAT. The
      code in the datamover that disables DAT can be removed as well.
      
      Thanks to Michael Holzheu and Gerald Schaefer for tracking this down.
      
      Reviewed-by: default avatarMichael Holzheu <holzheu@linux.vnet.ibm.com>
      Reviewed-by: default avatarPhilipp Rudo <prudo@linux.vnet.ibm.com>
      Cc: Gerald Schaefer <gerald.schaefer@de.ibm.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Fixes: 57d7f939 ("s390: add no-execute support")
      Cc: <stable@vger.kernel.org> # v4.11+
      Signed-off-by: default avatarHeiko Carstens <heiko.carstens@de.ibm.com>
    socket.h 2.02 KiB
    #ifndef _UAPI_ASM_SOCKET_H
    #define _UAPI_ASM_SOCKET_H
    
    #include <asm/sockios.h>
    
    /* For setsockopt(2) */
    #define SOL_SOCKET	0xffff
    
    #define SO_DEBUG	0x0001
    #define SO_REUSEADDR	0x0004
    #define SO_KEEPALIVE	0x0008
    #define SO_DONTROUTE	0x0010
    #define SO_BROADCAST	0x0020
    #define SO_LINGER	0x0080
    #define SO_OOBINLINE	0x0100
    #define SO_REUSEPORT	0x0200
    #define SO_SNDBUF	0x1001
    #define SO_RCVBUF	0x1002
    #define SO_SNDBUFFORCE	0x100a
    #define SO_RCVBUFFORCE	0x100b
    #define SO_SNDLOWAT	0x1003
    #define SO_RCVLOWAT	0x1004
    #define SO_SNDTIMEO	0x1005
    #define SO_RCVTIMEO	0x1006
    #define SO_ERROR	0x1007
    #define SO_TYPE		0x1008
    #define SO_PROTOCOL	0x1028
    #define SO_DOMAIN	0x1029
    #define SO_PEERNAME	0x2000
    
    #define SO_NO_CHECK	0x400b
    #define SO_PRIORITY	0x400c
    #define SO_BSDCOMPAT	0x400e
    #define SO_PASSCRED	0x4010
    #define SO_PEERCRED	0x4011
    #define SO_TIMESTAMP	0x4012
    #define SCM_TIMESTAMP	SO_TIMESTAMP
    #define SO_TIMESTAMPNS	0x4013
    #define SCM_TIMESTAMPNS	SO_TIMESTAMPNS
    
    /* Security levels - as per NRL IPv6 - don't actually do anything */
    #define SO_SECURITY_AUTHENTICATION		0x4016
    #define SO_SECURITY_ENCRYPTION_TRANSPORT	0x4017
    #define SO_SECURITY_ENCRYPTION_NETWORK		0x4018
    
    #define SO_BINDTODEVICE	0x4019
    
    /* Socket filtering */
    #define SO_ATTACH_FILTER        0x401a
    #define SO_DETACH_FILTER        0x401b
    #define SO_GET_FILTER		SO_ATTACH_FILTER
    
    #define SO_ACCEPTCONN		0x401c
    
    #define SO_PEERSEC		0x401d
    #define SO_PASSSEC		0x401e
    
    #define SO_MARK			0x401f
    
    #define SO_TIMESTAMPING		0x4020
    #define SCM_TIMESTAMPING	SO_TIMESTAMPING
    
    #define SO_RXQ_OVFL             0x4021
    
    #define SO_WIFI_STATUS		0x4022
    #define SCM_WIFI_STATUS		SO_WIFI_STATUS
    #define SO_PEEK_OFF		0x4023
    
    /* Instruct lower device to use last 4-bytes of skb data as FCS */
    #define SO_NOFCS		0x4024
    
    #define SO_LOCK_FILTER		0x4025
    
    #define SO_SELECT_ERR_QUEUE	0x4026
    
    #define SO_BUSY_POLL		0x4027
    
    #define SO_MAX_PACING_RATE	0x4028
    
    #define SO_BPF_EXTENSIONS	0x4029
    
    #define SO_INCOMING_CPU		0x402A
    
    #define SO_ATTACH_BPF		0x402B
    #define SO_DETACH_BPF		SO_DETACH_FILTER
    
    #endif /* _UAPI_ASM_SOCKET_H */