AW: [syzbot] [fs?] possible deadlock in ovl_create_object (2)
From: Richard Weinberger
Date: Sun Sep 20 2026 - 17:09:47 EST
Am Sat, Sep 19, 2026, 16:44 schrieb Chris Roy <iam@xxxxxxxxxxx>:
> On Sat, Sep 19, 2026, Richard Weinberger wrote:
> > While we're here, maybe it's time to add a decent configfs interface to
> > this driver instead of configuring through module parameters.
> > That way also multiple instances are possible.
> >
> > IMHO testing is the only use case. I use it regularly.
>
> I would love to look at this if you think it's worth the added
> complexity. A couple of design questions before I start
> on anything:
>
> - Does configfs coexist with the existing block2mtd= module param
> (for early-boot/cmdline compatibility), or replace it outright?
Keeping the module parameters is not a hard requirement but would be nice.
Ideally, the module parameters prove an initial configfs setting.
> - For multiple instances, would a configfs group per device (backing
> path, erase size, label) match what you had in mind?
>
Yes. See how nvmet uses configfs. A similar, but simpler, approach
will do it for block2mtd too.
> Can sketch an RFC-style doc once I have a sense of the above.
Sounds good.
Thanks,
//richard