Re: [Issue 1273] Changed - svn cp corrupts *two* repositories

issues@subversion.tigris.org writes:

> + ------- Additional Comments From jgoerzen@tigris.org 2003-04-30 08:29 PDT -------
> + I'm not sure that I agree with closing this; despite the block for the svn
> + cp being put in place now, it seems that this is a denial-of-service attack
> + in the making if any old client can crash the server so easily.

[taking this to the dev list, because the issue-tracker is awkward for
discussion.]

Ah, so maybe we should investigate exactly how/why apache didn't
gracefully shutdown the DB environment.

In the repository you were committing to, the client told the server
to copy some data into your transaction from an invalid path (i.e. the
path didn't exist in the repository.) Did that cause httpd to abort
BDB incorrectly? Can we reproduce this?

As for the 'source' repository, I'd really like to know what's going
on there... I have no explanation for that. All you did was
'checkout' some data from it into your working copy. It makes me
wonder if 'svn commit' tried to commit to two different repositories
or something, since the checked-out data might have
source-repositories url.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 30 17:36:55 2003