Rapid file system development using ptrace

Spillane, Richard P.; Wright, Charles P.; Sivathanu, Gopalan; Zadok, Erez

doi:10.1145/1281700.1281722

Cited by 16 publications

(10 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The ptrace() system call can also be used to build an infrastructure for developing file systems in user space [31]. An advantage of this technique is that all OS entry points, rather than just file system operations, can be intercepted.…”

Section: Introductionmentioning

confidence: 99%

Performance and extension of user space file systems

Rajgarhia

Gehani

2010

Proceedings of the 2010 ACM Symposium on Applied Computing

View full text Add to dashboard Cite

Several efforts have been made over the years for developing file systems in user space. Many of these efforts have failed to make a significant impact as measured by their use in production systems. Recently, however, user space file systems have seen a strong resurgence. FUSE is a popular framework that allows file systems to be developed in user space while offering ease of use and flexibility.In this paper, we discuss the evolution of user space file systems with an emphasis on FUSE, and measure its performance using a variety of test cases. We also discuss the feasibility of developing file systems in high-level programming languages, by using as an example Java bindings for FUSE that we have developed. Our benchmarks show that FUSE offers adequate performance for several kinds of workloads.

show abstract

Section: Introductionmentioning

confidence: 99%

Performance and extension of user space file systems

Rajgarhia

Gehani

2010

Proceedings of the 2010 ACM Symposium on Applied Computing

View full text Add to dashboard Cite

show abstract

“…Frameworks for rapid filesystem development were created, although, with moderate success. One example is Goanna, presented in 2007 [18].…”

Section: Ptrace System Call -Goannamentioning

confidence: 99%

Portable Userspace Virtual Filesystem Switch

Faber

Boryczko

2013

csci

View full text Add to dashboard Cite

Multiple different filesystems -including disk-based, network, distributed, abstract -are an integral part of every operating system. They are usually written as kernel modules and abstracted to the user via a virtual filesystem switch.In this paper, we analyze the feasibility of reimplementing the virtual filesystem switch as a userspace daemon and applicability of this approach in real-life usage. Such reimplementation will require a way to virtualize processes behavior related to filesystem operations. The problem is non-trivial, as we assume limited capabilities of the VFS switch implemented in userspace. We present a layered architecture comprising of a monitoring process, the VFS abstraction and real filesystem implementations. All working in userspace. Then, we evaluate this solution in four areas: portability, feasibility, usability, and performance. Our results demonstrate possible gains in the use of a userspacebased approach with monolithic kernels, but also underline problems that are encountered in this approach.

show abstract

“…Researchers have also used similar program monitoring techniques to implement user space file systems (Spillane et al 2007).…”

Section: Related Workmentioning

confidence: 99%

AFID: an automated approach to collecting software faults

2010

View full text Add to dashboard Cite

We present a new approach for creating repositories of real software faults. We have developed a tool, the Automatic Fault IDentification Tool (AFID), that implements this approach. AFID records both a fault revealing test case and a faulty version of the source code for any crashing faults that the developer discovers and a fault correcting source code change for any crashing faults that the developer corrects. The test cases are a significant contribution, because they enable new research that explores the dynamic behaviors of the software faults. AFID uses an operating system level monitoring mechanism to monitor both the compilation and execution of the application. This technique makes it straightforward for AFID to support a wide range of programming languages and compilers.We present our experience using AFID in a controlled case study and in a real development environment to collect software faults in the internal development of our group's compiler. The case studies collected several real software faults and validated the basic approach. The longer term internal study revealed weaknesses in using the original version of AFID for real development. This experience led to a number of refinements to the tool for use in real software development. We have collected over 20 real software faults in large programs and continue to collect software faults.

show abstract

Rapid file system development using ptrace

Cited by 16 publications

References 10 publications

Performance and extension of user space file systems

Performance and extension of user space file systems

Portable Userspace Virtual Filesystem Switch

AFID: an automated approach to collecting software faults

Contact Info

Product

Resources

About