All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>
Cc: ZhaoLong Wang <wangzhaolong1@huawei.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
	dpervushin <dpervushin@embeddedalley.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	chengzhihao1 <chengzhihao1@huawei.com>,
	yi zhang <yi.zhang@huawei.com>, yangerkun <yangerkun@huawei.com>
Subject: Re: [PATCH v3] mtd: Fix gluebi NULL pointer dereference caused by ftl notifier
Date: Sun, 29 Oct 2023 14:50:33 +0100	[thread overview]
Message-ID: <20231029145033.0ad2682a@xps-13> (raw)
In-Reply-To: <174426702.13324.1698438610904.JavaMail.zimbra@nod.at>

Hi Richard,

richard@nod.at wrote on Fri, 27 Oct 2023 22:30:10 +0200 (CEST):

> ----- Ursprüngliche Mail -----
> > Von: "Miquel Raynal" <miquel.raynal@bootlin.com>  
> >> Detailed reproduction information available at the link[1],
> >> 
> >> The solution for the gluebi module is to run jffs2 on the UBI
> >> volume without considering working with ftl or mtdblock.[2].  
> > 
> > I am sorry but ftl, gluebi, mtdblock, jffs2 and ubi in the same report
> > seem a little bit fuzzy. Are you sure about this sentence?  
> 
> ZhaoLong Wang found an interesting bug while stacking various MTD components.
> I suggested to just deny mtdblock on top of gluebi to avoid the whole
> problem class instead of adding more duct tape.

Ack. I'll queue this once the log fixed and your official Ack-by
received for mtd/next after -rc1 is out.

Thanks,
Miquèl

> 
> Thanks,
> //richard
> 
> The issue reminds me of one of my favorite Monty Python sketches, https://www.youtube.com/watch?v=LFrdqQZ8FFc
> ;-)

:-)

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

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>
Cc: ZhaoLong Wang <wangzhaolong1@huawei.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
	dpervushin <dpervushin@embeddedalley.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	chengzhihao1 <chengzhihao1@huawei.com>,
	yi zhang <yi.zhang@huawei.com>, yangerkun <yangerkun@huawei.com>
Subject: Re: [PATCH v3] mtd: Fix gluebi NULL pointer dereference caused by ftl notifier
Date: Sun, 29 Oct 2023 14:50:33 +0100	[thread overview]
Message-ID: <20231029145033.0ad2682a@xps-13> (raw)
In-Reply-To: <174426702.13324.1698438610904.JavaMail.zimbra@nod.at>

Hi Richard,

richard@nod.at wrote on Fri, 27 Oct 2023 22:30:10 +0200 (CEST):

> ----- Ursprüngliche Mail -----
> > Von: "Miquel Raynal" <miquel.raynal@bootlin.com>  
> >> Detailed reproduction information available at the link[1],
> >> 
> >> The solution for the gluebi module is to run jffs2 on the UBI
> >> volume without considering working with ftl or mtdblock.[2].  
> > 
> > I am sorry but ftl, gluebi, mtdblock, jffs2 and ubi in the same report
> > seem a little bit fuzzy. Are you sure about this sentence?  
> 
> ZhaoLong Wang found an interesting bug while stacking various MTD components.
> I suggested to just deny mtdblock on top of gluebi to avoid the whole
> problem class instead of adding more duct tape.

Ack. I'll queue this once the log fixed and your official Ack-by
received for mtd/next after -rc1 is out.

Thanks,
Miquèl

> 
> Thanks,
> //richard
> 
> The issue reminds me of one of my favorite Monty Python sketches, https://www.youtube.com/watch?v=LFrdqQZ8FFc
> ;-)

:-)

  reply	other threads:[~2023-10-29 13:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  1:20 [PATCH v3] mtd: Fix gluebi NULL pointer dereference caused by ftl notifier ZhaoLong Wang
2023-10-27  1:20 ` ZhaoLong Wang
2023-10-27  3:23 ` Zhihao Cheng
2023-10-27  3:23   ` Zhihao Cheng
2023-10-27 17:40 ` Miquel Raynal
2023-10-27 17:40   ` Miquel Raynal
2023-10-27 20:30   ` Richard Weinberger
2023-10-27 20:30     ` Richard Weinberger
2023-10-29 13:50     ` Miquel Raynal [this message]
2023-10-29 13:50       ` Miquel Raynal
2023-10-29 15:39       ` Richard Weinberger
2023-10-29 15:39         ` Richard Weinberger
2023-12-19 14:36         ` ZhaoLong Wang
2023-12-19 14:36           ` ZhaoLong Wang
2023-12-19 14:44           ` Miquel Raynal
2023-12-19 14:44             ` Miquel Raynal
2023-12-20  2:15             ` ZhaoLong Wang
2023-12-20  2:15               ` ZhaoLong Wang

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=20231029145033.0ad2682a@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=chengzhihao1@huawei.com \
    --cc=dpervushin@embeddedalley.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    --cc=wangzhaolong1@huawei.com \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.