DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH v2] v7a: run: randomise the SSH forwarding port
Date: Mon, 26 Apr 2021 11:03:12 +0200	[thread overview]
Message-ID: <20210426090312.ma4wpwcaszzlnvmi@pengutronix.de> (raw)
In-Reply-To: <20210426090216.fxkcrcubnptadyyg@pengutronix.de>

On Mon, Apr 26, 2021 at 11:02:16AM +0200, Robert Schwebel wrote:
> On Mon, Apr 26, 2021 at 10:35:56AM +0200, Roland Hieber wrote:
> > When multiple ./configs/platform-v7a/run scripts are run at the same
> > time, the first qemu process will open port 4445, and following runs
> > will fail. To prevent that, first look at the environment variable
> > QEMU_SSH_PORT to determine the port to be used (so that users can set
> > this in their shell to keep the port static), or fall back to a port
> > between 1025 and 65025 using the shell's PID as a seed, which should
> > have a good chance of being unused. Also print the port forwarding
> > before starting qemu, so we don't have to bother with "ps -Af|grep
> > qemu".
> > 
> > Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> > 
> > ---
> > v2:
> >   * use PPID instead of RANDOM to make the port reproducable in the same
> >     shell session (Michael Olbrich)
> > ---
> >  configs/platform-v7a/run | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> Could you rebase the patch against next?

The subject could need some care as well, as it isn't "randomize" any
more with the PPID change.

rsc
-- 
Pengutronix e.K.                           | Dipl.-Ing. Robert Schwebel  |
Steuerwalder Str. 21                       | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |

_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de


  reply	other threads:[~2021-04-26  9:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26  6:05 [DistroKit] [PATCH 1/5] v7a: image-vexpress: convert hex numbers to human-readable sizes Roland Hieber
2021-04-26  6:05 ` [DistroKit] [PATCH 2/5] v7a: images: remove redundant size specifications Roland Hieber
2021-04-26  6:35   ` Robert Schwebel
2021-04-26  6:05 ` [DistroKit] [PATCH 3/5] v7a: barebox: clean up defaultenvs Roland Hieber
2021-04-26  6:36   ` Robert Schwebel
2021-04-26  6:05 ` [DistroKit] [PATCH 4/5] v7a: run: remove telnet port forwarding Roland Hieber
2021-04-26  6:36   ` Robert Schwebel
2021-04-26  6:05 ` [DistroKit] [PATCH 5/5] v7a: run: randomise the SSH forwarding port Roland Hieber
2021-04-26  6:33   ` Michael Olbrich
2021-04-26  8:30     ` Roland Hieber
2021-04-26  8:35       ` [DistroKit] [PATCH v2] " Roland Hieber
2021-04-26  9:02         ` Robert Schwebel
2021-04-26  9:03           ` Robert Schwebel [this message]
2021-04-26 10:07   ` [DistroKit] [PATCH v3] v7a: run: make the SSH forwarding port multiprocess-compatible Roland Hieber
2021-04-26 10:09     ` Robert Schwebel
2021-04-26  6:35 ` [DistroKit] [PATCH 1/5] v7a: image-vexpress: convert hex numbers to human-readable sizes Robert Schwebel

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=20210426090312.ma4wpwcaszzlnvmi@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    --cc=rhi@pengutronix.de \
    /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