From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Larry McVoy <lm@work.bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: BK2CVS problem
Date: Wed, 5 Nov 2003 12:58:13 -0800 [thread overview]
Message-ID: <20031105125813.A5648@one-eyed-alien.net> (raw)
In-Reply-To: <20031105204522.GA11431@work.bitmover.com>; from lm@bitmover.com on Wed, Nov 05, 2003 at 12:45:22PM -0800
[-- Attachment #1: Type: text/plain, Size: 2878 bytes --]
Out of curiosity, what were the changed lines?
Matt
On Wed, Nov 05, 2003 at 12:45:22PM -0800, Larry McVoy wrote:
> Somebody has modified the CVS tree on kernel.bkbits.net directly. Dave looked
> at the machine and it looked like someone may have been trying to break in and
> do it.
>
> We've fixed the file in question, the conversion is done back here at BitMover
> and after we transfer the files we check them and make sure they are OK and
> this file got flagged.
>
> The CVS tree is fine, you might want to remove and update exit.c to make sure
> you have the current version in your tree however.
>
> The problem file is kernel/exit.c which has a few extra entries like so:
>
> revision 1.121
> date: 2003/11/04 16:44:19; author: davem; state: Exp; lines: +58 -0
> Oops, I worked on the the wrong file, fixed again.
> ----------------------------
> revision 1.120
> date: 2003/11/04 16:42:00; author: davem; state: Exp; lines: +0 -58
> *** empty log message ***
> ----------------------------
> revision 1.119
> date: 2003/11/04 16:22:47; author: davem; state: Exp; lines: +2 -0
> *** empty log message ***
> ----------------------------
> revision 1.118
> date: 2003/10/27 19:50:03; author: torvalds; state: Exp; lines: +11 -5
> Fix ZOMBIE race with self-reaping threads.
>
> exit_notify() used to leave a window open when a thread
> died that made the thread visible as a ZOMBIE even though
> the thread reaped itself. This closes that window by marking
> the thread DEAD within the tasklist_lock.
>
> (Logical change 1.14141)
> ----------------------------
>
> Notice how the top 3 do not have the (Logical change X.YZ) at the end?
> That is a pointer so you can figure out the changeset boundaries and
> it is added back here during the conversion process. The file here is
> fine which leads me to believe that someone modified the file either on
> kernel.bkbits.net or managed to get in through the pserver. Dave swears
> up and down that it wasn't him so if anyone can step forward and claim
> responsibility that would be nice.
>
> It's not a big deal, we catch stuff like this, but it's annoying to the
> CVS users.
> --
> ---
> Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
Oh great modem, why hast thou forsaken me?
-- Dust Puppy
User Friendly, 3/2/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2003-11-05 20:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 20:45 Larry McVoy
2003-11-05 20:58 ` Matthew Dharm [this message]
2003-11-05 22:23 ` Larry McVoy
2003-11-05 22:33 ` Zwane Mwaikambo
2003-11-05 22:51 ` Andries Brouwer
2003-11-06 7:07 ` Brian McGroarty
2003-11-06 11:41 ` Andrew Walrond
2003-11-06 12:02 ` nosp
2003-11-06 12:02 ` Xavier Bestel
2003-11-06 13:27 ` Scott Robert Ladd
2003-11-06 13:59 ` Richard B. Johnson
2003-11-05 22:48 Chad Kitching
2003-11-05 22:53 ` Zwane Mwaikambo
2003-11-05 23:03 ` Larry McVoy
2003-11-06 0:52 ` Tomas Szepe
2003-11-06 1:57 ` Andreas Dilger
2003-11-06 2:20 ` Linus Torvalds
2003-11-06 3:01 ` Larry McVoy
2003-11-06 10:40 ` Matthias Andree
2003-11-06 4:09 ` Scott Robert Ladd
2003-11-06 10:06 ` bert hubert
2003-11-06 13:22 ` Theodore Ts'o
2003-11-06 14:43 ` Rik van Riel
2003-11-06 15:56 ` Linus Torvalds
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=20031105125813.A5648@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.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
all inboxes | Powered by JetHome®