1. 17 12月, 2010 2 次提交
    • C
      NFS: Introduce new-style XDR decoding functions for NFSv2 · e4f93234
      Chuck Lever 提交于
      We'd like to prevent local buffer overflows caused by malicious or
      broken servers.  New xdr_stream style decoders can do that.
      
      For efficiency, we also eventually want to be able to pass xdr_streams
      from call_decode() to all XDR decoding functions, rather than building
      an xdr_stream in every XDR decoding function in the kernel.
      
      Static helper functions are left without the "inline" directive.  This
      allows the compiler to choose automatically how to optimize these for
      size or speed.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Tested-by: NJ. Bruce Fields <bfields@redhat.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      e4f93234
    • C
      NFS: Introduce new-style XDR encoding functions for NFSv3 · d9c407b1
      Chuck Lever 提交于
      We're interested in taking advantage of the safety benefits of
      xdr_streams.  These data structures allow more careful checking for
      buffer overflow while encoding.  More careful type checking is also
      introduced in the new functions.
      
      For efficiency, we also eventually want to be able to pass xdr_streams
      from call_encode() to all XDR encoding functions, rather than building
      an xdr_stream in every XDR encoding function in the kernel.  To do
      this means all encoders must be ready to handle a passed-in
      xdr_stream.
      
      The new encoders follow the modern paradigm for XDR encoders: BUG on
      error, and always return a zero status code.
      
      Static helper functions are left without the "inline" directive.  This
      allows the compiler to choose automatically how to optimize these for
      size or speed.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Tested-by: NJ. Bruce Fields <bfields@redhat.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      d9c407b1
  2. 18 6月, 2009 1 次提交
  3. 24 4月, 2008 1 次提交
  4. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4