From: Al Viro <viro@zeniv.linux.org.uk>
To: dccp@vger.kernel.org
Subject: Re: get rid of the address_space override in setsockopt v2
Date: Mon, 27 Jul 2020 13:48:14 +0000 [thread overview]
Message-ID: <20200727134814.GD794331@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200720124737.118617-1-hch@lst.de>
On Mon, Jul 27, 2020 at 09:51:45AM +0000, David Laight wrote:
> I'm sure there is code that processes options in chunks.
> This probably means it is possible to put a chunk boundary
> at the end of userspace and continue processing the very start
> of kernel memory.
>
> At best this faults on the kernel copy code and crashes the system.
Really? Care to provide some details, or is it another of your "I can't
be possibly arsed to check what I'm saying, but it stands for reason
that..." specials?
next prev parent reply other threads:[~2020-07-27 13:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 12:47 get rid of the address_space override in setsockopt Christoph Hellwig
2020-07-20 16:38 ` Eric Biggers
2020-07-20 17:43 ` Christoph Hellwig
2020-07-20 20:47 ` Alexei Starovoitov
2020-07-21 9:38 ` David Laight
2020-07-21 10:26 ` David Laight
2020-07-22 7:56 ` Christoph Hellwig
2020-07-22 8:06 ` 'Christoph Hellwig'
2020-07-22 8:07 ` 'Christoph Hellwig'
2020-07-22 8:21 ` David Laight
2020-07-22 17:09 ` Alexei Starovoitov
2020-07-23 6:08 ` get rid of the address_space override in setsockopt v2 Christoph Hellwig
2020-07-24 22:43 ` David Miller
2020-07-26 7:03 ` Christoph Hellwig
2020-07-26 7:08 ` Andreas Schwab
2020-07-26 7:46 ` David Miller
2020-07-27 9:51 ` David Laight
2020-07-27 13:48 ` Al Viro [this message]
2020-07-27 14:09 ` David Laight
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200727134814.GD794331@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox