linux-kernel - Re: [PATCH V2] mtd: capture device name setting failure when adding mtd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <173893958654.2918383.13397786440999528769.b4-ty@bootlin.com>
Date: Fri, 07 Feb 2025 15:46:26 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Edward Adam Davis <eadavis@...com>
Cc: linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org, 
 richard@....at, syzkaller-bugs@...glegroups.com, vigneshr@...com
Subject: Re: [PATCH V2] mtd: capture device name setting failure when
 adding mtd

On Fri, 07 Feb 2025 20:10:35 +0800, Edward Adam Davis wrote:
> syzbot reported a WARNING in release_mtd_partition. [1]
> 
> The reproducer uses "/proc/thread-self/fail-nth" to trigger the failure
> of memory allocation when executing dev_set_name() in add_mtd_device(),
> which eventually causes device_register() to fail because the device name
> is not set, and finally triggers a warning in put_device().
> 
> [...]

Applied to mtd/next, thanks!

[1/1] mtd: capture device name setting failure when adding mtd
      commit: 3f930a52d7151addefa6d5ba9f7f2c17dc52db1d

Patche(s) should be available on mtd/linux.git and will be
part of the next PR (provided that no robot complains by then).

Kind regards,
Miquèl