public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Shannon Sterz <s.sterz@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-storage] dismanagement: account for leading white space in serial number
Date: Sun, 6 Apr 2025 21:19:51 +0200	[thread overview]
Message-ID: <e5361beb-42ff-4cf2-ae45-225b6387ac6a@proxmox.com> (raw)
In-Reply-To: <20250312083819.15379-1-s.sterz@proxmox.com>

did a s/dismanagement/disk management/ for the subject on applying this.

Am 12.03.25 um 09:38 schrieb Shannon Sterz:
> some manufacturer seem to report leading white space in the
> `ID_SERIAL_SHORT` field. the regex failed here, as it just didn't
> match the whitespace at all.
> 
> reported on the forum:
> https://forum.proxmox.com/threads/nvme-drive-serial-unknown.163480/#post-754953
> 
> Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
> ---
> 
> not sure this is the ideal fix, but i tried to stay on the more
> conservative side here. alternatively the regex could be:
> 
> ^E: ID_SERIAL_SHORT=(.+)$
> 
> but then the whitespace would be considered as part of the serial, not
> sure this is intended or could have negative side effects.

As serials are often printed on labels it would be really error
prone to include spaces in them.

> 
>  src/PVE/Diskmanage.pm | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
>

applied, thanks! What about spaces at the end though, are they already
parsed out and thus allowed?


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-04-06 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  8:38 [pve-devel] " Shannon Sterz
2025-04-06 19:19 ` Thomas Lamprecht [this message]
2025-04-07  8:00   ` [pve-devel] applied: " Fiona Ebner
2025-04-07 10:51     ` Thomas Lamprecht

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=e5361beb-42ff-4cf2-ae45-225b6387ac6a@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.sterz@proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal