Selectively switching memory access permission for manipulating data in a database

• US 5,895,467 A
• Filed: 04/11/1997
• Issued: 04/20/1999
• Est. Priority Date: 04/11/1997
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: Informix Software, Inc. (International Business Machines Corporation)
• Inventors: Kelleman, Keith, Ubell, Michael
• Primary Examiner(s): Amsbury, Wayne
• Assistant Examiner(s): CHANNAVAJJALA, SRIRAMA T
• Application Number:
  US08/835,967
• Time in Patent Office: 739 Days
• Field of Search: 707/2, 707/3, 707/8, 707/9, 707/10, 707/4, 707/5, 707/102, 707/101, 707/103, 707/1, 707/7, 707/100, 711/153, 711/100, 711/150, 711/200, 711/103, 395/610, 395/477, 395/186
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2291 User-Defined Types; Storage management thereof
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 9/468 Specific access rights for resources, e.g. using capability register
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99939 Privileged access

Abstract

Routines for manipulating data in a database are performed by a database server by determining whether or not a database manipulation routine is to be isolated from a specified range of memory, and, in response, selectively switching memory access permission to the specified range of memory (e.g., from read/write to read-only) for the database manipulation routine under consideration. The database manipulation routine is then executed using the selectively switched memory access permission. A database manipulation routine that is to be isolated can be executed with read-only memory access thereby protecting the specified range of memory (e.g., corresponding to core data structures) from improper modification.

Claims

1. A method, performed by a database server, of executing one or more database manipulation routines to perform a corresponding database operation, the method comprising:

determining whether a database manipulation routine is to be isolated from a specified range of core memory;

selectively switching a core memory access permission for the database manipulation routine based on the determination; and

executing the database manipulation routine using the selectively switched core memory access permission.

2. The method of claim 1 in which the determining comprises inspecting a parameter associated with the database manipulation routine.

3. The method of claim 2 further comprising, prior to the determining, setting the parameter to a value that specifies a class of processor for executing the database manipulation routine.

4. The method of claim 3 in which the setting comprises assigning the parameter a value that specifies a class of processor that is isolated from the specified range of memory.

5. The method of claim 1 in which the selective switching comprises making a local procedure call.

6. The method of claim 1 in which the selective switching comprises setting the memory access permission for the database manipulation routine to read-only for the specified range of memory if the database manipulation routine is determined to be a routine that is to be isolated from the specified range of memory.

7. The method of claim 1 in which the selective switching comprises setting the memory access permission for the database manipulation routine to read/write for the specified range of memory if the database manipulation routine is determined to be a routine that is not to be isolated from the specified range of memory.

8. The method of claim 1 in which the selective switching comprises migrating a thread of execution for the database manipulation routine from a processor that has read/write permission to the specified range of memory to a processor that has read-only permission to the specified range of memory.

9. The method of claim 8 in which the migrating comprises maintaining the thread of execution within a same address space as the specified range of memory.

10. The method of claim 1 in which the selective switching comprises switching from a trusted context in which a thread of execution for the database manipulation has read/write permission to the specified range of memory to an untrusted context in which the thread of execution has read-only permission to the specified range of memory.

11. The method of claim 10 further comprising detecting that the thread of execution requires access to a resource residing in the specified range of memory for which the thread of execution has read-only access to execute the database manipulation routine.

12. The method of claim 11 further comprising, upon detecting that the thread of execution requires access to a resource residing in the specified range of memory, switching from the untrusted context to another trusted context in which the thread of execution has read/write permission to the specified range of memory.

13. The method of claim 12 further comprising switching from the another trusted context to the untrusted context after the thread of execution for the database manipulation routine has completed accessing the resource in the specified range of memory.

14. The method of claim 13 further comprising switching from the untrusted context to the trusted context after execution of the database manipulation routine has completed.

15. The method of claim 1 in which the selective switching comprises performing an arbitrary number of switches between a trusted context and an untrusted context.

16. The method of claim 1 in which the executing comprises remaining in a same address space as the specified range of memory while executing the database manipulation routine.

17. The method of claim 1 in which the executing comprises performing the database manipulation routine with a processor that has read-only permission to the specified range of memory if the database manipulation routine is determined to be a routine that is to be isolated from the specified range of memory.

18. The method of claim 1 in which the executing comprises performing the database manipulation routine with a processor that has read/write permission to the specified range of memory if the database manipulation routine is determined to be a routine that is not to be isolated from the specified range of memory.

19. The method of claim 1 in which the executing comprises performing the database manipulation routine in a memory segment that is logically partitioned from the specified range of memory if the database manipulation routine is determined to be a routine that is to be isolated from the specified range of memory.

20. The method of claim 1 in which the executing comprises performing the database manipulation routine in the specified range of memory if the database manipulation routine is determined to be a routine that is not to be isolated from the specified range of memory.

21. The method of claim 1 in which the executing comprises selectively allowing modification of resources residing in the specified range of memory.

22. The method of claim 21 in which the selective modification is limited to one or more permissible execution entry points in the specified range of memory.

23. The method of claim 22 further comprising specifying the one or more permissible execution entry points in a call back table.

24. A method, performed by a database server, of executing one or more database manipulation routines to perform a corresponding database operation, the method comprising:

dividing a core database memory address space into memory segments;

selectively executing a database manipulation routine in a first memory segment; and

preventing the executing database manipulation routine from writing information to another of the memory segments.

25. The method of claim 24 further comprising allowing the database manipulation routine executing in the first memory segment to read information from another memory segment.

26. The method of claim 24 further comprising allowing the database manipulation routine executing in the first memory segment to migrate to another memory segment to perform a predetermined routine.

27. The method of claim 26 further comprising checking whether an entry point specified for the predetermined routine in the another segment is a permissible entry point.

28. The method of claim 27 in which the checking comprises comparing the specified entry point against a predetermined set of one or more permissible entry points.

29. The method of claim 27 further comprising blocking execution of the predetermined routine if the specified entry point in the another segment is an impermissible entry point.

30. The method of claim 24 further comprising returning the database manipulation routine to the first memory segment after the predetermined routine has completed.

31. The method of claim 24 in which the database manipulation routine is executed in the first memory segment if the database manipulation routine is identified as one from which information in another memory segment is to be protected.

32. The method of claim 31 in which the database manipulation routine from which information in another memory segment is to be protected comprises a user-defined routine.

33. The method of claim 31 in which the database manipulation routine from which information in another memory segment is to be protected comprises an untrusted routine.

34. The method of claim 24 further comprising, if the database manipulation routine is not identified as one from which information in another memory segment is to be protected, executing the database manipulation routine with full read and write privileges to all memory segments.

35. The method of claim 34 in which the database manipulation routine comprises a trusted routine.

36. The method of claim 24 in which the memory segments reside in the same memory address space.

37. The method of claim 36 in which the dividing comprises logically partitioning the memory segments from each other.

38. The method of claim 24 in which the selective executing comprises performing the database manipulation routine with a process that has read-only access to memory segments other than the first memory segment.

39. The method of claim 38 in which the process comprises a multi-threaded virtual processor.

40. The method of claim 24 further comprising concurrently executing a plurality of database manipulation routines in respective ones of the memory segments, each database manipulation routine having read-only access to all memory segments other than its own memory segment.

41. A database server comprising:

a shared memory address space having a plurality of memory segments including a core memory segment and a fenced memory segment;

a plurality of database manipulation routines collectively representing a database operation, the routines including a trusted routine that is allowed to modify the core memory segment and an untrusted routine that is prohibited from modifying the core memory segment; and

a plurality of virtual processors linked to the plurality of routines, the virtual processors including a full-access virtual processor that executes trusted routines in the core memory segment and a fenced virtual processor that executes untrusted routines in the fenced memory segment.

42. The database server of claim 41 in which the full-access virtual processor has read/write access to all memory segments.

43. The database server of claim 41 in which the fenced virtual processor has read-only access to the core memory segment.

44. The database server of claim 41 in which each database manipulation routine has an associated parameter that specifies whether the routine is a trusted routine or an untrusted routine.

45. The database server of claim 41 further comprising a thread for executing database manipulation routines, the thread migrating from one virtual processor to another virtual processor based on whether the database manipulation routine being executed is trusted or untrusted.

46. The database server of claim 45 in which the thread migrates to a fenced virtual processor if the database manipulation routine being executed is an untrusted routine.

47. The database server of claim 45 in which the thread migrates to a full-access virtual processor if the database manipulation routine being executed is a trusted routine.

48. Computer software, residing on a computer readable medium, for a database server having linked routines for performing database manipulation methods, the computer software comprising instructions for causing a computer to perform the following operations:

(a) receive a database query from a client;

(b) identify which routines to perform to service the database query, each identified routine being either a trusted routine that is allowed to modify a core database memory or an untrusted routine that is prohibited from modifying the core database memory;

(c) perform one or more trusted routines using read/write access to the core database memory; and

(d) perform one or more untrusted routines using read-only access to the core database memory.

49. The computer software of claim 48 in which (d) comprises instructions to cause a thread of execution to migrate from a first processor having read/write access to the core database memory to another processor having read-only access to the core database memory.

50. The computer software of claim 48 in which (d) comprises instructions to change memory access permission for the core database memory to read-only in connection with performing an untrusted routine.