Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #66275

Bug#948041: impossible to update libbpf without updating the kernel

Path csiph.com!news.dns-netz.com!news.freedyn.net!weretis.net!feeder7.news.weretis.net!news.albasani.net!tahina.priv.at!bofh.it!news.nic.it!robomod
From Ben Hutchings <ben@decadent.org.uk>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#948041: impossible to update libbpf without updating the kernel
Date Fri, 31 Jan 2020 17:20:02 +0100
Message-ID <zuHbs-2FO-11@gated-at.bofh.it> (permalink)
References <zkzId-1as-5@gated-at.bofh.it> <zkBh0-1Xc-1@gated-at.bofh.it> <zkBK1-2m1-1@gated-at.bofh.it> <zkyM9-AC-3@gated-at.bofh.it> <znzsl-4FB-3@gated-at.bofh.it> <znHpT-1bb-1@gated-at.bofh.it> <znHpT-1bb-1@gated-at.bofh.it> <zkyM9-AC-3@gated-at.bofh.it> <zoKc2-7vg-5@gated-at.bofh.it> <zoKc2-7vg-3@gated-at.bofh.it> <zkyM9-AC-3@gated-at.bofh.it> <zoQr7-2zK-3@gated-at.bofh.it> <zkyM9-AC-3@gated-at.bofh.it> <zoQr7-2zK-3@gated-at.bofh.it>
X-Original-To Sudip Mukherjee <sudipm.mukherjee@gmail.com>, 948041@bugs.debian.org, Jonathan Nieder <jrnieder@gmail.com>
X-Mailbox-Line From debian-bugs-dist-request@lists.debian.org Fri Jan 31 16:15:09 2020
Old-Return-Path <debbugs@buxtehude.debian.org>
X-Spam-Flag NO
X-Spam-Score 0.25
Reply-To Ben Hutchings <ben@decadent.org.uk>, 948041@bugs.debian.org
Resent-To debian-bugs-dist@lists.debian.org
Resent-Cc Debian Kernel Team <debian-kernel@lists.debian.org>
X-Debian-Pr-Message followup 948041
X-Debian-Pr-Package libbpf-dev
X-Debian-Pr-Source linux
X-Spam-Bayes score:0.0000 Tokens: new, 10; hammy, 150; neutral, 159; spammy, 0. spammytokens: hammytokens:0.000-+--H*ct:application, 0.000-+--H*ct:protocol, 0.000-+--H*ct:micalg, 0.000-+--H*ct:signed, 0.000-+--H*ct:pgp-signature
Content-Type multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-foYIbfyhY1DJeHhyMcQf"
User-Agent Evolution 3.34.1-2+b1
MIME-Version 1.0
X-Sa-Exim-Connect-IP 94.197.121.42
X-Sa-Exim-Mail-From ben@decadent.org.uk
X-Sa-Exim-Scanned No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false
X-Debian-Message from BTS
X-Mailing-List <debian-bugs-dist@lists.debian.org> archive/latest/1582648
List-ID <debian-bugs-dist.lists.debian.org>
List-URL <https://lists.debian.org/debian-bugs-dist/>
Approved robomod@news.nic.it
Lines 94
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Cc Julia Kartseva <hex@fb.com>, "waldi@debian.org" <waldi@debian.org>, "md@Linux.IT" <md@Linux.IT>
X-Original-Date Fri, 31 Jan 2020 17:11:25 +0100
X-Original-Message-ID <5eacdfec7d635aea6bb15dc1bea32c6d339cf340.camel@decadent.org.uk>
X-Original-References <20200103175936.GD490987@bongo.bofh.it> <20200103194944.hvhiczvbe52xphe4@shell.thinkmo.de> <CADVatmMsSG0TG1nq7VFNAnNUZOsWc8=B17d=yno=_vnnZ4JDOw@mail.gmail.com> <20200103171255.sqhtr3rpaep5gdmr@debian> <20200112002820.zebojotzoeeaukc2@debian> <20200112085155.yeumrrrp2wtiarlk@shell.thinkmo.de> <20200112085155.yeumrrrp2wtiarlk@shell.thinkmo.de> <20200103171255.sqhtr3rpaep5gdmr@debian> <0bd726ba-be20-ba91-0a52-60c38b28ff3b@fb.com> <20200115061205.GC218782@google.com> <20200103171255.sqhtr3rpaep5gdmr@debian> <20200115125016.ht6xrxpprmpjwfdx@debian> <20200103171255.sqhtr3rpaep5gdmr@debian> <20200115125016.ht6xrxpprmpjwfdx@debian>
Xref csiph.com linux.debian.bugs.dist:993988 linux.debian.kernel:66275

Cross-posted to 2 groups.

Show key headers only | View raw


[Multipart message — attachments visible in raw view] - view raw

On Wed, 2020-01-15 at 12:50 +0000, Sudip Mukherjee wrote:
> Hi Jonathan,
> 
> On Wed, Jan 15, 2020 at 06:12:05AM +0000, Jonathan Nieder wrote:
> > retitle 948041 libbpf-dev: please build from https://github.com/libbpf/libbpf
> > reassign 948041 libbpf-dev
> > merge 942903 948041
> > quit
> > 
> > Hi,
> > 
> > Julia Kartseva wrote:
> > > On Sun, 12 Jan 2020 09:51:55 +0100 Bastian Blank <waldi@debian.org> wrote:
> > > > Why should we?  If the upstream developers decide to maintain it
> > > > independently, aka don't use the kernel repo as true source, or better,
> > > > remove the source from it, then we have something to do.
> > 
> > I agree --- if upstream development were happening in
> > https://github.com/libbpf/libbpf then this would be a no-brainer.  It
> > appears to instead be a mirror of the source that's in the kernel
> > repo, though.
> 
> That will be difficult as all of them are dependent on the ftrace hooks
> that are in the kernel.
> 
> > > Why should we switch from kernel sources to GH is a frequently asked
> > > question so the reason was explained in libbpf README [1].
> > 
> > If I'm reading that correctly, the intent appears to be that it would
> > allow faster libbpf upgrades.
> 
> Yes, one of my intent. Faster and independent.

This is a potential benefit, but probably only in the run-up to a
release when we might fix the kernel version early.

[...]
> > Is there some underlying need that we could address more directly?
> > I think I'm missing some piece of the motivation here.
> 
> Going back to the history of why I started this bug report. I was added
> in a discussion about libtraceevent and Steven (upstream developer of
> libtraceevent) was asking how can he make changes to the library without
> releasing a new version and that the distros should not pick up as that
> will still be premature and not tested enough.
[...]

However, this ability to release libbpf *less* often also seems
important, and I think this point has been missed.

I have some concern about whether this might prevent us building
bpftool in future (if it depends on recent changes in libbpf) but
that's hypothetical at this point.

So on balance I support moving libbpf out to a separate source package.

Ben.

-- 
Ben Hutchings
73.46% of all statistics are made up.


Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#948041: impossible to update libbpf without updating the kernel Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-01-03 18:20 +0100
  Bug#948041: impossible to update libbpf without updating the kernel Marco d'Itri <md@Linux.IT> - 2020-01-03 19:20 +0100
    Bug#948041: impossible to update libbpf without updating the kernel Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-01-03 19:50 +0100
    Bug#948041: impossible to update libbpf without updating the kernel Bastian Blank <bblank@thinkmo.de> - 2020-01-03 21:00 +0100
      Bug#948041: impossible to update libbpf without updating the kernel Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-01-03 21:30 +0100
        Bug#948041: impossible to update libbpf without updating the kernel Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-01-12 01:40 +0100
          Bug#948041: impossible to update libbpf without updating the kernel Bastian Blank <waldi@debian.org> - 2020-01-12 10:10 +0100
  Bug#948041: impossible to update libbpf without updating the kernel Jonathan Nieder <jrnieder@gmail.com> - 2020-01-15 07:20 +0100
    Bug#948041: impossible to update libbpf without updating the kernel Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-01-15 14:00 +0100
      Bug#948041: impossible to update libbpf without updating the kernel Bastian Blank <bblank@thinkmo.de> - 2020-01-18 16:50 +0100
        Bug#948041: impossible to update libbpf without updating the kernel Andrii Nakryiko <andrii.nakryiko@gmail.com> - 2020-01-20 07:50 +0100
      Bug#948041: impossible to update libbpf without updating the kernel Ben Hutchings <ben@decadent.org.uk> - 2020-01-31 17:20 +0100
        Bug#948041: impossible to update libbpf without updating the kernel Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-01-31 17:40 +0100
          Bug#948041: impossible to update libbpf without updating the kernel Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-02-05 22:10 +0100
  Bug#948041: marked as done (libbpf-dev: please build from  https://github.com/libbpf/libbpf) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-04-12 00:10 +0200

csiph-web