http://oss.sgi.com/bugzilla/show_bug.cgi?id=882
Dave Chinner <david@xxxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |david@xxxxxxxxxxxxx
--- Comment #1 from Dave Chinner <david@xxxxxxxxxxxxx> 2010-05-03 18:37:28 CST
---
(In reply to comment #0)
> I am a graduate student at the University of Wisconsin-Madison, working with
> Prof. Ben Liblit. We have a tool that performs static program analysis to find
> the list of basic error codes that each system call may return, along with
> sample paths that illustrate how specific error instances reach a given
> function's exit points. We have analyzed the Linux 2.6.32.4 kernel and
> compared
> the error codes against version 2.39 of the Linux manual pages for 42
> file-related system calls. Our tool reports 78 undocumented error-code
> instances returned by several system calls when analyzing XFS (from which 23
> seem to be VFS related).
Inteesting work. v2.39 of the man pages is rather old - debian unstable has
v3.24 in it, so quite a few of these might have already been documented.
Also, for interfaces such as ioctl you probably also need to include scanning
the XFS specific man pages (in xfsprogs and xfsdump packages) to get all the
documented error values that relevant to that syscall.
What I do find interesting is that there's no report of XFS returning
EUCLEAN/EFSCORRUPTED to any syscall. I'm pretty sure that is not documented in
any of the main manpages, and most syscalls into XFS have the potential to
return that error as it indicates a shutdown filesystem.
> This work has been accepted for workshop publication. Any feedback would be
> really helpful to improve our tool. It could be the case that (1) the
> documentation is in fact incomplete, (2) the file system implementation is not
> supposed to return a given error code, or (3) the error code cannot possibly
> be
> returned (we believe that none of the 78 reports fall into this category).
This will take some time to do - I'd really like to be working with information
from the latest packages rather that waste time on tracking down reports of
things that have already been documented.
Cheers,
Dave.
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
|