netdev - Re: do a single memdup_user in sctp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200522.161133.75296957266065703.davem@davemloft.net>
Date:   Fri, 22 May 2020 16:11:33 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     hch@....de
Cc:     vyasevich@...il.com, nhorman@...driver.com,
        marcelo.leitner@...il.com, kuba@...nel.org,
        David.Laight@...LAB.COM, linux-sctp@...r.kernel.org,
        netdev@...r.kernel.org
Subject: Re: do a single memdup_user in sctp_setsockopt

From: Christoph Hellwig <hch@....de>
Date: Thu, 21 May 2020 19:46:35 +0200

> based on the review of Davids patch to do something similar I dusted off
> the series I had started a few days ago to move the memdup_user or
> copy_from_user from the inidividual sockopts into sctp_setsockopt,
> which is done with one patch per option, so it might suit Marcelo's
> taste a bit better.  I did not start any work on getsockopt.

I think you and David still need to discuss how to move forward here,
there doesn't seem to be consensus yet.

Thanks.