From: Jens Axboe <axboe@kernel.dk>
To: linux-kernel-mentees@lists.linuxfoundation.org
Cc: hch@infradead.org,
syzbot+a8e049cd3abd342936b6@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org, willy@infradead.org,
linux-block@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] loop: Check for overflow while configuring loop
Date: Tue, 23 Aug 2022 10:16:46 -0600 [thread overview]
Message-ID: <166127140632.124225.483036207879834754.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220823160810.181275-1-code@siddh.me>
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
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: linux-kernel-mentees@lists.linuxfoundation.org
Cc: stable@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, willy@infradead.org,
syzbot+a8e049cd3abd342936b6@syzkaller.appspotmail.com,
hch@infradead.org
Subject: Re: [PATCH v2] loop: Check for overflow while configuring loop
Date: Tue, 23 Aug 2022 10:16:46 -0600 [thread overview]
Message-ID: <166127140632.124225.483036207879834754.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220823160810.181275-1-code@siddh.me>
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
next prev parent reply other threads:[~2022-08-23 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 16:08 [PATCH v2] loop: Check for overflow while configuring loop Siddh Raman Pant via Linux-kernel-mentees
2022-08-23 16:08 ` Siddh Raman Pant
2022-08-23 16:15 ` Christoph Hellwig
2022-08-23 16:15 ` Christoph Hellwig
2022-08-23 16:16 ` Jens Axboe [this message]
2022-08-23 16:16 ` Jens Axboe
2022-08-24 8:12 ` Siddh Raman Pant via Linux-kernel-mentees
2022-08-24 8:12 ` Siddh Raman Pant
2022-08-24 12:53 ` Jens Axboe
2022-08-24 12:53 ` Jens Axboe
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=166127140632.124225.483036207879834754.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+a8e049cd3abd342936b6@syzkaller.appspotmail.com \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.