Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: overseers@sourceware.org
Cc: gdb@sourceware.org
Subject: Re: gdb.git hiccup
Date: Sun, 04 Oct 2009 15:05:00 -0000	[thread overview]
Message-ID: <878wfri4ip.fsf@meyering.net> (raw)
In-Reply-To: <20091004144926.GA5475@ednor.casa.cgf.cx> (Christopher Faylor's 	message of "Sun, 4 Oct 2009 10:49:26 -0400")

Christopher Faylor wrote:

> On Sun, Oct 04, 2009 at 08:51:32AM +0200, Jim Meyering wrote:
>>But when I tried to diagnose it, I discovered that there are unreadable
>>temporary pack files owned by from back in February that prevent a local clone.
>>
>>  sourceware$ cd /git/archer.git/objects; ls -l tmp*
>>  -rw-------  1 rmoseley archer  368640 Feb  9  2009 tmp_pack_hMUtoO
>>  -rw-------  1 rmoseley archer  876544 Feb  9  2009 tmp_pack_jmBcho
>>  -rw-------  1 rmoseley archer 1007616 Feb  9  2009 tmp_pack_zbwx0m
>>
>>I have neither root access nor archer group membership, so cannot remove
>>them, and sent a request to overseers yesterday.  No reply yet.
>
> How did rmosely manage to create these files when he does not have
> login privileges?

Via git.
tmp_pack_ files are created by git, but obviously not always
removed by the version of git that was running back then.
rmosely *does* have write access to the archer git repository.

> Do we need to close a hole here somewhere?

It'd be good to make sure that can't happen again,
but it's not a security problem (DoS, maybe, though)


  reply	other threads:[~2009-10-04 15:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03 12:30 Jim Meyering
2009-10-03 13:22 ` Jim Meyering
2009-10-03 15:38   ` Jim Meyering
2009-10-03 17:05     ` Joel Brobecker
2009-10-03 23:35     ` Daniel Jacobowitz
2009-10-04  6:51       ` Jim Meyering
2009-10-04 11:09         ` Frank Ch. Eigler
2009-10-04 12:15           ` Matt Rice
2009-10-04 12:43             ` Jim Meyering
     [not found]               ` <20091004142139.GA19501@host0.dyn.jankratochvil.net>
2009-10-04 20:16                 ` Jim Meyering
2009-10-05  1:46                   ` Jan Kratochvil
2009-10-05 10:14                 ` Jim Meyering
2009-10-06 20:48                   ` Jan Kratochvil
2009-10-06 21:12                     ` Jim Meyering
2009-10-06 21:23                     ` Jim Meyering
2009-10-04 12:15           ` Jim Meyering
2009-10-04 12:40             ` Frank Ch. Eigler
2009-10-04 14:49         ` Christopher Faylor
2009-10-04 15:05           ` Jim Meyering [this message]
2009-10-04 15:15             ` Christopher Faylor
2009-10-04 20:34               ` Jim Meyering
2009-10-06 22:03     ` Joel Brobecker
2009-10-07 14:52       ` Jim Meyering
     [not found]         ` <20091007192519.GK16338@adacore.com>
2009-10-07 21:13           ` Jim Meyering
2009-10-08  9:20           ` Jim Meyering

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=878wfri4ip.fsf@meyering.net \
    --to=jim@meyering.net \
    --cc=gdb@sourceware.org \
    --cc=overseers@sourceware.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
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