All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <mani@kernel.org>
To: Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: Sricharan Ramabadhran <sricharan@codeaurora.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	pragalla@codeaurora.org, ~postmarketos/upstreaming@lists.sr.ht,
	martin.botka@somainline.org,
	angelogioacchino.delregno@somainline.org,
	marijn.suijten@somainline.org, jamipkettunen@somainline.org,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd@lists.infradead.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mdalam@codeaurora.org,
	bbhatt@codeaurora.org, hemantk@codeaurora.org
Subject: Re: [PATCH] mtd: nand: raw: qcom_nandc: Don't clear_bam_transaction on READID
Date: Fri, 8 Apr 2022 18:59:41 +0530	[thread overview]
Message-ID: <20220408132941.GA12635@thinkpad> (raw)
In-Reply-To: <b428593e-a4db-984b-df7f-7cd14795d5e2@somainline.org>

Hi,

On Fri, Mar 11, 2022 at 10:22:51PM +0100, Konrad Dybcio wrote:
> 
>

[...]
 
> I have 3 logs for you:
> 
> [1] is KASAN=y, with this patch
> [2] is KASAN=y, WITHOUT this patch (should die, but doesn't - does KASAN prevent it from doing something stupid?)
> [3] is KASAN=n, WITHOUT this patch (dies as expected)
> 

We reproduced the same issue on SDX65-MTP board and your hack worked :)
Since this board is available inside Qcom, now Sadre and Sricharan should be
able to investigate it properly.

Thanks,
Mani

> Looks like there's a lot happening..
> 
> 
> Konrad
> > 
> > Regards,
> >   Sricharan
> > 
> > 
> 
> [1] https://paste.debian.net/1233873/
> [2] https://paste.debian.net/1233874/
> [3] https://paste.debian.net/1233878/

WARNING: multiple messages have this Message-ID (diff)
From: Manivannan Sadhasivam <mani@kernel.org>
To: Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: Sricharan Ramabadhran <sricharan@codeaurora.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	pragalla@codeaurora.org, ~postmarketos/upstreaming@lists.sr.ht,
	martin.botka@somainline.org,
	angelogioacchino.delregno@somainline.org,
	marijn.suijten@somainline.org, jamipkettunen@somainline.org,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd@lists.infradead.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mdalam@codeaurora.org,
	bbhatt@codeaurora.org, hemantk@codeaurora.org
Subject: Re: [PATCH] mtd: nand: raw: qcom_nandc: Don't clear_bam_transaction on READID
Date: Fri, 8 Apr 2022 18:59:41 +0530	[thread overview]
Message-ID: <20220408132941.GA12635@thinkpad> (raw)
In-Reply-To: <b428593e-a4db-984b-df7f-7cd14795d5e2@somainline.org>

Hi,

On Fri, Mar 11, 2022 at 10:22:51PM +0100, Konrad Dybcio wrote:
> 
>

[...]
 
> I have 3 logs for you:
> 
> [1] is KASAN=y, with this patch
> [2] is KASAN=y, WITHOUT this patch (should die, but doesn't - does KASAN prevent it from doing something stupid?)
> [3] is KASAN=n, WITHOUT this patch (dies as expected)
> 

We reproduced the same issue on SDX65-MTP board and your hack worked :)
Since this board is available inside Qcom, now Sadre and Sricharan should be
able to investigate it properly.

Thanks,
Mani

> Looks like there's a lot happening..
> 
> 
> Konrad
> > 
> > Regards,
> >   Sricharan
> > 
> > 
> 
> [1] https://paste.debian.net/1233873/
> [2] https://paste.debian.net/1233874/
> [3] https://paste.debian.net/1233878/

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

  reply	other threads:[~2022-04-08 13:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 18:44 [PATCH] mtd: nand: raw: qcom_nandc: Don't clear_bam_transaction on READID Konrad Dybcio
2022-01-13 18:44 ` Konrad Dybcio
2022-01-13 18:45 ` Konrad Dybcio
2022-01-13 18:45   ` Konrad Dybcio
2022-01-14  7:27 ` Miquel Raynal
2022-01-14  7:27   ` Miquel Raynal
2022-01-26 10:16   ` Miquel Raynal
2022-01-26 10:16     ` Miquel Raynal
2022-01-26 10:33     ` Manivannan Sadhasivam
2022-01-26 10:33       ` Manivannan Sadhasivam
2022-01-26 10:42       ` Miquel Raynal
2022-01-26 10:42         ` Miquel Raynal
2022-01-26 11:36         ` Manivannan Sadhasivam
2022-01-26 11:36           ` Manivannan Sadhasivam
2022-01-28  4:25         ` Sricharan Ramabadhran
2022-01-28  4:25           ` Sricharan Ramabadhran
2022-01-28 17:50           ` Sricharan Ramabadhran
2022-01-28 17:50             ` Sricharan Ramabadhran
2022-01-31  9:52             ` Miquel Raynal
2022-01-31  9:52               ` Miquel Raynal
2022-01-31 10:09             ` Konrad Dybcio
2022-01-31 10:09               ` Konrad Dybcio
2022-01-31 14:13               ` Sricharan Ramabadhran
2022-01-31 14:13                 ` Sricharan Ramabadhran
2022-01-31 19:54                 ` Konrad Dybcio
2022-01-31 19:54                   ` Konrad Dybcio
2022-02-01 13:52                   ` Miquel Raynal
2022-02-01 13:52                     ` Miquel Raynal
2022-02-01 15:51                     ` Konrad Dybcio
2022-02-01 15:51                       ` Konrad Dybcio
2022-02-02  7:24                       ` Sricharan Ramabadhran
2022-02-02  7:24                         ` Sricharan Ramabadhran
2022-02-04 17:17                         ` Sricharan Ramabadhran
2022-02-04 17:17                           ` Sricharan Ramabadhran
2022-02-08 16:45                           ` Konrad Dybcio
2022-02-08 16:45                             ` Konrad Dybcio
2022-02-24  7:33                             ` Sricharan Ramabadhran
2022-02-24  7:33                               ` Sricharan Ramabadhran
2022-03-11 21:22                               ` Konrad Dybcio
2022-03-11 21:22                                 ` Konrad Dybcio
2022-04-08 13:29                                 ` Manivannan Sadhasivam [this message]
2022-04-08 13:29                                   ` Manivannan Sadhasivam

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=20220408132941.GA12635@thinkpad \
    --to=mani@kernel.org \
    --cc=angelogioacchino.delregno@somainline.org \
    --cc=bbhatt@codeaurora.org \
    --cc=hemantk@codeaurora.org \
    --cc=jamipkettunen@somainline.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marijn.suijten@somainline.org \
    --cc=martin.botka@somainline.org \
    --cc=mdalam@codeaurora.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=pragalla@codeaurora.org \
    --cc=richard@nod.at \
    --cc=sricharan@codeaurora.org \
    --cc=vigneshr@ti.com \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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.