From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnd Bergmann <arnd@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Doug Anderson <dianders@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SoC Team <soc@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM: SoC fixes for v5.10, part 3
Date: Mon, 30 Nov 2020 19:06:34 +0000 [thread overview]
Message-ID: <20201130190634.GA1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAHk-=wgZhkMu5UFgmD2Yt96S_nrhMzTTXfqOwgBe4nsg0R_M6Q@mail.gmail.com>
On Mon, Nov 30, 2020 at 10:15:29AM -0800, Linus Torvalds wrote:
> On Mon, Nov 30, 2020 at 10:05 AM Russell King - ARM Linux admin
> <linux@armlinux.org.uk> wrote:
> >
> > If you think that /dev/sda for example is always the machine's internal
> > HDD, that is wrong.
>
> Yes. See the whole part about
>
> "Note that it really is only the internal devices that matter. Once you
> start plugging in an external USB hug and random devices, ordering
> clearly won't be reliable.
>
> So this is not a "everything must be ordered". But people who think
> that that then means "everythinbg can be random" are wrong"
>
> in my email.
>
> And the key word here is:
>
> > I have a HP Pavilion laptop with its internal HDD with a Windows
> > installation. Because I didn't want to destroy that in any way, I
> > bought an external USB3 SATA enclosure and SSD, and installed Debian
> > Stable on there.
>
> .. but it will still generally be stable with the same hardware
> configuration, and not fluctuate randomly from boot to boot when the
> hardware is the same.
>
> Is it a guarantee? No. External plugged in hardware can change things.
> In fact, when you have things like Thunderbolt involved, since it just
> looks like PCI, even the PCI probing order won't be the same with or
> without the plugged-in device.
>
> But again: avoid randomness. The difference between non-random and
> random is that one is predictable and one is not.
>
> Predictability is good. It's not necessariyl always achievable, but
> it's very much something we should strive for VERY HARD.
>
> Predictability and reproducibility help debugging enormously. It means
> that things like "git bisect" work a lot better. It makes user reports
> much more understandable when two users with identical hardware see
> identical issues.
>
> Seriously. Anybody who argues against reproducibility is so far out to
> lunch that it's not even funny.
>
> You seem to argue on a complete technicality.
Yes, I fully agree - but the problem is that how people read your
"avoid randomness".
Randomness as in "doesn't change if I change kernel configuration"
or "doesn't change order on reboot to a similar kernel".
People who have complained about mmc in the past have done so from
the point of view of "I changed something, now my mmc block devices
are different".
It is my understanding that mmc behaves in the same way as exactly
what I see on my HP laptop. The device numbering is stable provided
the hardware (and indeed software) configuration is stable.
If I decide to rebuild the Debian kernel for my HP laptop, and build
in the drivers necessary for all its hardware, the internal HDD will
switch to being /dev/sda instead of /dev/sdb as it is now... which
doesn't seem to be any different from complaints like "I've changed
some code in the kernel now my MMC devices have changed order."
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-30 19:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 20:51 [GIT PULL] ARM: SoC fixes for v5.10, part 3 Arnd Bergmann
2020-11-27 22:56 ` Linus Torvalds
2020-11-30 17:04 ` Doug Anderson
2020-11-30 17:44 ` Linus Torvalds
2020-11-30 18:05 ` Russell King - ARM Linux admin
2020-11-30 18:15 ` Linus Torvalds
2020-11-30 19:06 ` Russell King - ARM Linux admin [this message]
2020-11-30 18:11 ` Doug Anderson
2020-11-30 18:22 ` Linus Torvalds
2020-11-30 22:54 ` Russell King - ARM Linux admin
2020-12-01 11:39 ` Ulf Hansson
2020-12-01 14:00 ` Arnd Bergmann
2020-12-07 20:19 ` Geert Uytterhoeven
2020-12-07 21:55 ` Arnd Bergmann
2020-12-07 22:15 ` Doug Anderson
2020-12-08 7:31 ` Geert Uytterhoeven
2020-12-14 20:22 ` Ulf Hansson
2020-12-15 8:19 ` Geert Uytterhoeven
2020-12-15 9:53 ` Ulf Hansson
2020-11-30 17:27 ` Dmitry Torokhov
2020-12-05 20:48 ` Pavel Machek
2020-11-27 23:29 ` pr-tracker-bot
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=20201130190634.GA1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).