Possibility to use tags #262

Closed
graysky2 opened this Issue Apr 4, 2013 · 6 comments

Comments

Projects
None yet
4 participants

graysky2 commented Apr 4, 2013

Have you guys considered the possibility of tagging your releases? This would avoid the need for distro packagers to do a git clone --depth 1 git://github.com/raspberrypi/linux.git to bring down the source for compilation.

Collaborator

popcornmix commented Apr 5, 2013

Can you be more explicit about what you would like?
Are you suggesting every commit to linux repo is tagged? Or just the points where the firmware repo is rebuilt? Or just the points where an sdcard release?
What would like the tag to consist of?

graysky2 commented Apr 5, 2013

I do not think every push should tagged at all... just points at which a distro would likely do a pkgrel or version bump. Only when new key changes are made I guess.

In terms of the content of the tag, nothing fancy. For example, I tend to use the following scheme in my stuff:
git tag v5.23 -m 'v5.32 && git push --tags'

You can use whatever kind of naming system you want, the key is that the tag is there so now I can point a package to a tarball github auto generates.

Example: https://github.com/graysky2/profile-sync-daemon/tags

richo commented Apr 5, 2013

Bonus points if you can sign the tags with a PGP key with some trust behind
it.

On Fri, Apr 5, 2013 at 10:37 PM, graysky notifications@github.com wrote:

I do not think every push should tagged at all... just points at which a
distro would likely do a pkgrel or version bump. Only when new key changes
are made I guess.

In terms of the content of the tag, nothing fancy. For example, I tend to
use the following scheme in my stuff:
git tag v5.23 -m 'v5.32 && git push --tags'

You can use whatever kind of naming system you want, the key is that the
tag is there so now I can point a package to a tarball github auto
generates.

Example: https://github.com/graysky2/profile-sync-daemon/tags


Reply to this email directly or view it on GitHubhttps://github.com/raspberrypi/linux/issues/262#issuecomment-15951108
.

@graysky2 graysky2 referenced this issue in archlinuxarm/PKGBUILDs Apr 9, 2013

Closed

Updates to PKGBUILD for your consideration #456

graysky2 commented Apr 9, 2013

@richo - The tag is really harmless so no need for any kind of signing. The security lies in the access to the source itself which is well protected with pub/priv keys.

popcornmix pushed a commit that referenced this issue May 1, 2013

cpuset: fix RCU lockdep splat
5d21cc2 ("cpuset: replace
cgroup_mutex locking with cpuset internal locking") incorrectly
converted proc_cpuset_show() from cgroup_lock() to cpuset_mutex.
proc_cpuset_show() is accessing cgroup hierarchy proper to determine
cgroup path which can't be protected by cpuset_mutex.  This triggered
the following RCU warning.

 ===============================
 [ INFO: suspicious RCU usage. ]
 3.8.0-rc3-next-20130114-sasha-00016-ga107525-dirty #262 Tainted: G        W
 -------------------------------
 include/linux/cgroup.h:534 suspicious rcu_dereference_check() usage!

 other info that might help us debug this:

 rcu_scheduler_active = 1, debug_locks = 1
 2 locks held by trinity/7514:
  #0:  (&p->lock){+.+.+.}, at: [<ffffffff812b06aa>] seq_read+0x3a/0x3e0
  #1:  (cpuset_mutex){+.+...}, at: [<ffffffff811abae4>] proc_cpuset_show+0x84/0x190

 stack backtrace:
 Pid: 7514, comm: trinity Tainted: G        W
+3.8.0-rc3-next-20130114-sasha-00016-ga107525-dirty #262
 Call Trace:
  [<ffffffff81182cab>] lockdep_rcu_suspicious+0x10b/0x120
  [<ffffffff811abb71>] proc_cpuset_show+0x111/0x190
  [<ffffffff812b0827>] seq_read+0x1b7/0x3e0
  [<ffffffff812b0670>] ? seq_lseek+0x110/0x110
  [<ffffffff8128b4fb>] do_loop_readv_writev+0x4b/0x90
  [<ffffffff8128b776>] do_readv_writev+0xf6/0x1d0
  [<ffffffff8128b8ee>] vfs_readv+0x3e/0x60
  [<ffffffff8128b960>] sys_readv+0x50/0xd0
  [<ffffffff83d33d18>] tracesys+0xe1/0xe6

The operation can be performed under RCU read lock.  Replace
cpuset_mutex locking with RCU read locking.

tj: Rewrote patch description.

Reported-by: Sasha Levin <sasha.levin@oracle.com>
Signed-off-by: Li Zefan <lizefan@huawei.com>
Signed-off-by: Tejun Heo <tj@kernel.org>

Ruffio commented Aug 29, 2016

@popcornmix this issue/feature request should be closed due to inactivity

Collaborator

popcornmix commented Aug 29, 2016

Tags are now added when we update kernel is raspbian. See: https://github.com/raspberrypi/linux/tags

@popcornmix popcornmix closed this Aug 29, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment