[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <166127140632.124225.483036207879834754.b4-ty@kernel.dk>
Date: Tue, 23 Aug 2022 10:16:46 -0600
From: Jens Axboe <axboe@...nel.dk>
To: linux-kernel-mentees@...ts.linuxfoundation.org
Cc: stable@...r.kernel.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, willy@...radead.org,
syzbot+a8e049cd3abd342936b6@...kaller.appspotmail.com,
hch@...radead.org
Subject: Re: [PATCH v2] loop: Check for overflow while configuring loop
On Tue, 23 Aug 2022 21:38:10 +0530, Siddh Raman Pant via Linux-kernel-mentees wrote:
> The userspace can configure a loop using an ioctl call, wherein
> a configuration of type loop_config is passed (see lo_ioctl()'s
> case on line 1550 of drivers/block/loop.c). This proceeds to call
> loop_configure() which in turn calls loop_set_status_from_info()
> (see line 1050 of loop.c), passing &config->info which is of type
> loop_info64*. This function then sets the appropriate values, like
> the offset.
>
> [...]
Applied, thanks!
[1/1] loop: Check for overflow while configuring loop
commit: f11ebc7347340d291ba032a3872e40d3283fc351
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists