From: Bart Van Assche <bvanassche@acm.org>
To: Dominik Maier <dmnk@google.com>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, dmnk+artist@google.com
Subject: Re: [BUG] loop: missing BLK_OPEN_WRITE check on LOOP_SET_STATUS in lo_compat_ioctl()
Date: Mon, 19 Oct 2026 12:23:27 -0700 [thread overview]
Message-ID: <51568a73-77a8-49cf-8a49-71f15cb6e5e7@acm.org> (raw)
In-Reply-To: <CAE7N4Sq6_M610g6gOUJCkkoBH06Kqbndb7KhGGLk=WCHOqHbtw@mail.gmail.com>
On 10/19/26 3:16 AM, Dominik Maier wrote:
> Fixes: 604f275f9670 ("loop:Check for read-write open mode before
> setting status")
> Assisted-by: ARTIST LLM
I can't find commit ID 604f275f9670 anywhere. Additionally, I can't find
any commit with the subject "loop:Check for read-write open mode before
setting status". Did I perhaps overlook something?
Linux kernel patches must be signed. I don't see a Signed-off-by tag?
Thanks,
Bart.
next prev parent reply other threads:[~2026-10-19 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 10:16 [BUG] loop: missing BLK_OPEN_WRITE check on LOOP_SET_STATUS in lo_compat_ioctl() Dominik Maier
2026-10-19 19:13 ` Jens Axboe
2026-10-19 19:23 ` Bart Van Assche [this message]
2026-10-19 19:26 ` 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=51568a73-77a8-49cf-8a49-71f15cb6e5e7@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=dmnk+artist@google.com \
--cc=dmnk@google.com \
--cc=linux-block@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