From: "Jörn Engel" <joern@barelysecure.org>
To: Tal Zussman <tz2294@columbia.edu>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
sashiko-bot@kernel.org, Joern Engel <joern@lazybastard.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
sashiko-reviews@lists.linux.dev,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 3/3] mtd: block2mtd: convert _block2mtd_erase() to folios
Date: Thu, 15 Oct 2026 11:34:44 -0700 [thread overview]
Message-ID: <atEcxC2Hp7idmr04@cashel.logfs.org> (raw)
In-Reply-To: <5ec61284-3ae9-4875-bba3-932cbede14b4@columbia.edu>
On Thu, Oct 15, 2026 at 11:19:23AM -0400, Tal Zussman wrote:
>
> It seems like it's a real but very rare pre-existing issue.
You should drop the "but very rare" bit. ;)
When it comes to bugs, being rare and hard to hit doesn't improve
things, it makes them worse. Rare bugs result in crazy bug reports that
you cannot reproduce. Instead of spending a few hours on them, they can
cost you days, weeks or months.
They are also often non-trivial to fix. Instead of taking a bug report
and saying "ah, here is the problem", several times I've had to come up
with new debug code, make it robust enough to ship into production
(because rare bugs only reproduce at scale, which means on production
systems), refine it once or twice and then finally get enough
information to fix the bug.
On the plus side, such debug infrastructure tends to provide enough
clues to fix many bugs, not just one troublemaker.
Jörn
--
The cost of changing business rules is much more expensive for software
than for a secretaty.
-- unknown
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-10-15 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 3:34 [PATCH 0/3] mtd: block2mtd: convert to folios Tal Zussman
2026-10-15 3:34 ` [PATCH 1/3] mtd: block2mtd: convert block2mtd_read() " Tal Zussman
2026-10-15 3:34 ` [PATCH 2/3] mtd: block2mtd: convert _block2mtd_write() " Tal Zussman
2026-10-15 3:34 ` [PATCH 3/3] mtd: block2mtd: convert _block2mtd_erase() " Tal Zussman
2026-10-15 3:45 ` sashiko-bot
2026-10-15 9:14 ` Miquel Raynal
2026-10-15 15:19 ` Tal Zussman
2026-10-15 18:34 ` Jörn Engel [this message]
2026-10-15 18:39 ` [PATCH 0/3] mtd: block2mtd: convert " Jörn Engel
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=atEcxC2Hp7idmr04@cashel.logfs.org \
--to=joern@barelysecure.org \
--cc=joern@lazybastard.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tz2294@columbia.edu \
--cc=vigneshr@ti.com \
--cc=willy@infradead.org \
/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