Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Dylan Yudaken <dylany@fb.com>
To:     <io-uring@vger.kernel.org>
CC:     <axboe@kernel.dk>, <asml.silence@gmail.com>,
        <linux-kernel@vger.kernel.org>, <kernel-team@fb.com>,
        Dylan Yudaken <dylany@fb.com>
Subject: [PATCH 0/4] io_uring: verify that reserved fields are 0
Date:   Tue, 12 Apr 2022 09:30:38 -0700
Message-ID: <20220412163042.2788062-1-dylany@fb.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain
Precedence: bulk

A few reserved fields are not verified to be 0. In preparation for possib=
ly using these fields later we should verify that they are passed as 0.

One extra field I do not have confidence in verifying is up.nr in io_regi=
ster_files_update(). Should this also be checked to be zero?

Patch 1 in this series just moves a validation out of __io_register_rsrc_=
update as it was duplicated
Patch 2-4 add verifications for reserved fields

Dylan Yudaken (4):
  io_uring: move io_uring_rsrc_update2 validation
  io_uring: verify that resv2 is 0 in io_uring_rsrc_update2
  io_uring: verify resv is 0 in ringfd register/unregister
  io_uring: verify pad field is 0 in io_get_ext_arg

 fs/io_uring.c | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)


base-commit: 0f8da75b51ac863b9435368bd50691718cc454b0
--=20
2.30.2