1. 17 9月, 2010 3 次提交
  2. 31 7月, 2010 1 次提交
    • D
      nfs: include space for the NUL in root path · 674b2222
      Dan Carpenter 提交于
      In root_nfs_name() it does the following:
      
              if (strlen(buf) + strlen(cp) > NFS_MAXPATHLEN) {
                      printk(KERN_ERR "Root-NFS: Pathname for remote directory too long.\n");
                      return -1;
              }
              sprintf(nfs_export_path, buf, cp);
      
      In the original code if (strlen(buf) + strlen(cp) == NFS_MAXPATHLEN)
      then the sprintf() would lead to an overflow.  Generally the rest of the
      code assumes that the path can have NFS_MAXPATHLEN (1024) characters and
      a NUL terminator so the fix is to add space to the nfs_export_path[]
      buffer.
      Signed-off-by: NDan Carpenter <error27@gmail.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      674b2222
  3. 15 5月, 2010 1 次提交
  4. 18 6月, 2009 2 次提交
  5. 27 5月, 2009 1 次提交
    • S
      nfs: fix build error in nfsroot with initconst · d0367a50
      Sam Ravnborg 提交于
      fix build error with latest kbuild adjustments to initconst.
      
      The commit a447c093 ("vfs: Use
      const for kernel parser table") changed:
      
          static match_table_t __initdata tokens = {
      to
          static match_table_t __initconst tokens = {
      
      But the missing const causes popwerpc to fail with latest
      updates to __initconst like this:
      
      fs/nfs/nfsroot.c:400: error: __setup_str_nfs_root_setup causes a section type conflict
      fs/nfs/nfsroot.c:400: error: __setup_str_nfs_root_setup causes a section type conflict
      
      The bug is only present with kbuild-next.
      Following patch has been build tested.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Steven Whitehouse <swhiteho@redhat.com>
      Cc: Stephen Rothwell <sfr@canb.auug.org.au>
      Acked-by: NJan Beulich <jbeulich@novell.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      d0367a50
  6. 24 12月, 2008 3 次提交
  7. 31 10月, 2008 1 次提交
  8. 14 10月, 2008 1 次提交
  9. 08 10月, 2008 1 次提交
  10. 05 8月, 2008 1 次提交
  11. 25 7月, 2008 1 次提交
  12. 10 7月, 2008 2 次提交
  13. 07 12月, 2007 1 次提交
  14. 20 10月, 2007 1 次提交
  15. 10 10月, 2007 1 次提交
  16. 11 7月, 2007 2 次提交
  17. 01 5月, 2007 1 次提交
  18. 03 12月, 2006 1 次提交
  19. 04 10月, 2006 1 次提交
  20. 02 10月, 2006 1 次提交
  21. 08 2月, 2006 1 次提交
    • A
      [PATCH] nfsroot port= parameter fix [backport of 2.4 fix] · 8854eddb
      Al Viro 提交于
      Direct backport of 2.4 fix that didn't get propagated to 2.6; original
      comment follows:
      <quote>
         When I specify the NFS port for nfsroot (e.g.,
         nfsroot=<dir>,port=2049), the
         kernel uses the wrong port. In my case it tries to use 264 (0x108)
         instead
         of 2049 (0x801).
      
         This patch adds the missing htons().
      
         Eric
      </quote>
      
      Patch got applied in 2.4.21-pre6.  Author: Eric Lammerts (<eric@lammerts.org>,
      AFAICS).
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      8854eddb
  22. 09 1月, 2006 1 次提交
  23. 07 1月, 2006 1 次提交
    • C
      NFS: support large reads and writes on the wire · 40859d7e
      Chuck Lever 提交于
       Most NFS server implementations allow up to 64KB reads and writes on the
       wire.  The Solaris NFS server allows up to a megabyte, for instance.
      
       Now the Linux NFS client supports transfer sizes up to 1MB, too.  This will
       help reduce protocol and context switch overhead on read/write intensive NFS
       workloads, and support larger atomic read and write operations on servers
       that support them.
      
       Test-plan:
       Connectathon and iozone on mount point with wsize=rsize>32768 over TCP.
       Tests with NFS over UDP to verify the maximum RPC payload size cap.
      Signed-off-by: NChuck Lever <cel@netapp.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      40859d7e
  24. 23 6月, 2005 1 次提交
  25. 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