ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Vladimir D. Seleznev" <vseleznv@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] hash collision in rpm
Date: Wed, 5 May 2021 17:11:05 +0300
Message-ID: <YJKneWALLbH3iqIT@portlab> (raw)
In-Reply-To: <CA+qzen=zsq3au7q_6r4bpigQUeMFFy66jR3x6wo3N=cYNZaODQ@mail.gmail.com>

On Wed, May 05, 2021 at 08:40:27AM +0300, Alexey Tourbin wrote:
> [skip]
> 
> So the expected number of collisions for short versions is smaller,
> but we have two of them. By the linearity of expectation, the birthday
> collision rate is the same. (This generally shows that it is pointless
> to split a long set-version into a few shorter ones, under any classes
> of equivalence on symbols such as ELF ABI tags. Counterintuitively,
> you can't fight birthday collisions by partitioning, unless you also
> increase the output length. So doing separate set-versions for
> libfoo.so.0(FOO_1.0) and libfoo.so.0(FOO_1.1) is not necessarily a
> good idea, we can just as well hash sym@FOO_1.0 and sym@FOO_1.1 and
> package them into a single version.)

Unfortunately, the symbol resolution is very flexible (some treat it as
an advantage), so the dynamic linker can resolve sym@FOO_1.0 as sym and
vice versa. That makes almost no point to hash symbols with their
versions.

-- 
   WBR,
   Vladimir D. Seleznev


      parent reply	other threads:[~2021-05-05 14:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01  9:04 ` [devel] rust-1:1.50.0-alt1: Sisyphus/x86_64 test rebuild failed Alexey Gladkov
2021-05-04 10:32   ` [devel] hash collision in rpm Anton Farygin
2021-05-04 10:45     ` Alexey Gladkov
2021-05-04 12:50       ` Alexey Tourbin
2021-05-05  5:40         ` Alexey Tourbin
2021-05-05 13:10           ` Dmitry V. Levin
2021-05-05 14:11           ` Vladimir D. Seleznev [this message]

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=YJKneWALLbH3iqIT@portlab \
    --to=vseleznv@altlinux.org \
    --cc=devel@lists.altlinux.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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git