Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

Hi Al. On Mon, Aug 28, 2017 at 05:41:49AM +0100, Al Viro wrote: > On Sun, Aug 06, 2017 at 07:22:03PM +0100, Al Viro wrote: > > > assuming I'll have any sanity left by that time). > > ... and that hope had turned out to be far too optimistic. Ohh, looking forward to what impact this will have

Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

Hi Al. On Mon, Aug 28, 2017 at 05:41:49AM +0100, Al Viro wrote: > On Sun, Aug 06, 2017 at 07:22:03PM +0100, Al Viro wrote: > > > assuming I'll have any sanity left by that time). > > ... and that hope had turned out to be far too optimistic. Ohh, looking forward to what impact this will have

Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

On Sun, Aug 06, 2017 at 07:22:03PM +0100, Al Viro wrote: > I would pick it through my tree, but the local network is half-disasembled > for move (containers arrive tomorrow, flight to Boston on 9th, stuff should > arrive there by the weekend, so I hope to be back to normal by the 14th > or so,

Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

On Sun, Aug 06, 2017 at 07:22:03PM +0100, Al Viro wrote: > I would pick it through my tree, but the local network is half-disasembled > for move (containers arrive tomorrow, flight to Boston on 9th, stuff should > arrive there by the weekend, so I hope to be back to normal by the 14th > or so,

Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

On Sun, Aug 06, 2017 at 07:22:03PM +0100, Al Viro wrote: > On Sat, Aug 05, 2017 at 11:00:50PM +0300, Dmitry V. Levin wrote: > > The latest change of compat_sys_sigpending has broken it in two ways. > > > > First, it tries to write 4 bytes more than userspace expects: > > sizeof(old_sigset_t) ==

Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

On Sun, Aug 06, 2017 at 07:22:03PM +0100, Al Viro wrote: > On Sat, Aug 05, 2017 at 11:00:50PM +0300, Dmitry V. Levin wrote: > > The latest change of compat_sys_sigpending has broken it in two ways. > > > > First, it tries to write 4 bytes more than userspace expects: > > sizeof(old_sigset_t) ==

Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

On Sun, Aug 6, 2017 at 11:22 AM, Al Viro wrote: > Anyway, all of that can be done later; for now let's go with your patch. > ACKed-by: Al Viro > > I would pick it through my tree, but the local network is half-disasembled > for move (containers

Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

On Sun, Aug 6, 2017 at 11:22 AM, Al Viro wrote: > Anyway, all of that can be done later; for now let's go with your patch. > ACKed-by: Al Viro > > I would pick it through my tree, but the local network is half-disasembled > for move (containers arrive tomorrow, flight to Boston on 9th, stuff

Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

On Sat, Aug 05, 2017 at 11:00:50PM +0300, Dmitry V. Levin wrote: > The latest change of compat_sys_sigpending has broken it in two ways. > > First, it tries to write 4 bytes more than userspace expects: > sizeof(old_sigset_t) == sizeof(long) == 8 instead of > sizeof(compat_old_sigset_t) ==

Re: [PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

On Sat, Aug 05, 2017 at 11:00:50PM +0300, Dmitry V. Levin wrote: > The latest change of compat_sys_sigpending has broken it in two ways. > > First, it tries to write 4 bytes more than userspace expects: > sizeof(old_sigset_t) == sizeof(long) == 8 instead of > sizeof(compat_old_sigset_t) ==

[PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

The latest change of compat_sys_sigpending has broken it in two ways. First, it tries to write 4 bytes more than userspace expects: sizeof(old_sigset_t) == sizeof(long) == 8 instead of sizeof(compat_old_sigset_t) == sizeof(u32) == 4. Second, on big endian architectures these bytes are being

[PATCH] Fix compat_sys_sigpending breakage introduced by v4.13-rc1~6^2~12

The latest change of compat_sys_sigpending has broken it in two ways. First, it tries to write 4 bytes more than userspace expects: sizeof(old_sigset_t) == sizeof(long) == 8 instead of sizeof(compat_old_sigset_t) == sizeof(u32) == 4. Second, on big endian architectures these bytes are being