public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Chenyuan Yang <cy54@illinois.edu>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
	 Miquel Raynal <miquel.raynal@bootlin.com>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 syzkaller <syzkaller@googlegroups.com>,
	 Zijie Zhao <zijie4@illinois.edu>,
	 Lingming Zhang <lingming@illinois.edu>
Subject: Re: [Linux Kernel Bug] WARNING: zero-size vmalloc in ubi_read_volume_table
Date: Wed, 24 Jan 2024 10:30:03 +0100 (CET)	[thread overview]
Message-ID: <1166579150.272394.1706088603335.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <A65BC97A-20AA-4B9E-B7A1-6151B9E7CDC2@illinois.edu>

Chenyuan,

----- Ursprüngliche Mail -----
> Von: "Chenyuan Yang" <cy54@illinois.edu>
> mtd0
> Name:                           mtdram test device
> Type:                           ram
> Eraseblock size:                4096 bytes, 4.0 KiB

You're working with an extremely small MTD and the fuzzer set the VID
offset to a large value. As a consequence, the LEB size was smaller than
a single volume table record and the calculation of the volume table returned
zero.
Fix sent.

Thanks,
//richard

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2024-01-24  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH7PR11MB57682489034B17034C021B04A06B2@PH7PR11MB5768.namprd11.prod.outlook.com>
2024-01-23 15:30 ` [Linux Kernel Bug] WARNING: zero-size vmalloc in ubi_read_volume_table Yang, Chenyuan
2024-01-23 16:15   ` Richard Weinberger
2024-01-23 16:39     ` Yang, Chenyuan
     [not found]       ` <1365676233.271004.1706041442841.JavaMail.zimbra@nod.at>
2024-01-23 22:44         ` Yang, Chenyuan
2024-01-24  9:30           ` Richard Weinberger [this message]

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=1166579150.272394.1706088603335.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=cy54@illinois.edu \
    --cc=lingming@illinois.edu \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=syzkaller@googlegroups.com \
    --cc=vigneshr@ti.com \
    --cc=zijie4@illinois.edu \
    /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