From: syzbot <syzbot+ccffdf05833ebdaeae70@syzkaller.appspotmail.com>
To: rajojha047@gmail.com
Cc: rajojha047@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mmc?] KASAN: slab-use-after-free Write in ms_read_bytes
Date: Thu, 24 Sep 2026 12:21:29 -0700 [thread overview]
Message-ID: <6ab57839.80e1c6cc.1e8e5f.0016.GAE@google.com> (raw)
In-Reply-To: <CALq3yPV0NNZAO4pARgPe3_f-m2oFJH1FEKx-JsX7gc0s80jBQg@mail.gmail.com>
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
This crash does not have a reproducer. I cannot test it.
> master
>
> diff --git a/drivers/memstick/core/memstick.c b/drivers/memstick/core/memstick.c
> index 7f3f47db4c98..1a2b3c4d5e6f 100644
> --- a/drivers/memstick/core/memstick.c
> +++ b/drivers/memstick/core/memstick.c
> @@ -378,9 +378,7 @@ int memstick_set_rw_addr(struct memstick_dev *card)
> {
> card->next_request = h_memstick_set_rw_addr;
> memstick_new_req(card->host);
> - if (!wait_for_completion_timeout(&card->mrq_complete,
> - msecs_to_jiffies(500)))
> - card->current_mrq.error = -ETIMEDOUT;
> + wait_for_completion(&card->mrq_complete);
>
> return card->current_mrq.error;
> }
> @@ -413,9 +411,7 @@ static struct memstick_dev
> *memstick_alloc_card(struct memstick_host *host)
> goto err_out;
>
> card->next_request = h_memstick_read_dev_id;
> memstick_new_req(host);
> - if (!wait_for_completion_timeout(&card->mrq_complete,
> - msecs_to_jiffies(500)))
> - card->current_mrq.error = -ETIMEDOUT;
> + wait_for_completion(&card->mrq_complete);
>
> if (card->current_mrq.error)
> goto err_out;
next parent reply other threads:[~2026-09-24 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALq3yPV0NNZAO4pARgPe3_f-m2oFJH1FEKx-JsX7gc0s80jBQg@mail.gmail.com>
2026-09-24 19:21 ` syzbot [this message]
2026-09-23 0:33 syzbot
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=6ab57839.80e1c6cc.1e8e5f.0016.GAE@google.com \
--to=syzbot+ccffdf05833ebdaeae70@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rajojha047@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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
all inboxes | Powered by JetHome®