[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Badness in mod_dav_svn?

From: John Szakmeister <john_at_szakmeister.net>
Date: 2005-12-10 13:06:46 CET

I decided to take a look through some of the mod_dav_svn code to see if I
could find anything related to the mysterious FSFS issue Malcome and I have
been trying to track down. I ran across something interesting in
      /* res2's fs_root object is now invalid. regenerate it using
         the now-shared filesystem. */
      if (res2->info->root.txn_name)
          /* reopen the txn by name */

          /* regenerate the txn "root" object */
      else if (res2->info->root.rev)
          /* default: regenerate the revision "root" object */

It looks like the code is always expected to pass, or that we don't care about
the errors (I believe it's the first situation). However, I'm not sure that
the right thing to do is to proceed as if nothing had gone wrong. I assume
that res2->info->root.txn had something valid given it's previous file system
pointer. However, if we try to reopen the txn and fail for some reason, then
we attempt to use the txn tied to the original res2 file system pointer to
get the "root" object. I'm not sure whether that's an acceptable thing to
do. I assume not, otherwise there would have been no need to do this in the
first place. There are also other equally bad situations: the txn could be
opened, but opening the root fails; and we could fail to open the revision
root. All would pass this helper function claiming that they're the same
resource though.

Anyone with more mod_dav_svn foo able to comment on this? Seems like we're
counting on something happening, but we haven't documented that and I don't
believe that our APIs will guarantee success either.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 10 13:08:47 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.