Got it. Thanks again Al.
On Sat, Nov 28, 2020 at 7:28 PM Al Viro wrote:
>
> On Sat, Nov 28, 2020 at 06:19:31PM -0800, Walt Drummond wrote:
> > Thanks Al. I want to understand the nuance, so please bear with me as I
> > reason this out. The cast in stone nature of this is due to both the need
On Sat, Nov 28, 2020 at 06:19:31PM -0800, Walt Drummond wrote:
> Thanks Al. I want to understand the nuance, so please bear with me as I
> reason this out. The cast in stone nature of this is due to both the need
> to keep userspace and kernel space in sync (ie, you'd have to coordinate
> libc
(Sorry, resending as Gmail decided to ignore "Plaintext mode")
Thanks Al. I want to understand the nuance, so please bear with me as
I reason this out. The cast in stone nature of this is due to both
the need to keep userspace and kernel space in sync (ie, you'd have to
coordinate libc and
On Thu, Nov 19, 2020 at 02:11:33PM -0800, Walt Drummond wrote:
> The macro unsafe_put_sigmask() only handles the first 64 bits of the
> sigmask_t, which works today. However, if the definition of the
> sigset_t structure ever changed,
... existing userland would get fucked over, since sigset_t
The macro unsafe_put_sigmask() only handles the first 64 bits of the
sigmask_t, which works today. However, if the definition of the
sigset_t structure ever changed, this would fail to setup/restore the
signal stack properly and likely corrupt the sigset. This patch
updates unsafe_put_sigmask()
5 matches
Mail list logo
