1. 28 8月, 2006 1 次提交
    • E
      [PATCH] ufs: write to hole in big file · c37336b0
      Evgeniy Dushistov 提交于
      On UFS, this scenario:
      	open(O_TRUNC)
      	lseek(1024 * 1024 * 80)
      	write("A")
      	lseek(1024 * 2)
      	write("A")
      
      may cause access to invalid address.
      
      This happened because of "goal" is calculated in wrong way in block
      allocation path, as I see this problem exists also in 2.4.
      
      We use construction like this i_data[lastfrag], i_data array of pointers to
      direct blocks, indirect and so on, it has ceratain size ~20 elements, and
      lastfrag may have value for example 40000.
      
      Also this patch fixes related to handling such scenario issues, wrong
      zeroing metadata, in case of block(not fragment) allocation, and wrong goal
      calculation, when we allocate block
      Signed-off-by: NEvgeniy Dushistov <dushistov@mail.ru>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      c37336b0
  2. 02 7月, 2006 1 次提交
  3. 30 6月, 2006 1 次提交
  4. 29 6月, 2006 1 次提交
  5. 28 6月, 2006 1 次提交
  6. 26 6月, 2006 8 次提交
  7. 04 2月, 2006 1 次提交
  8. 15 1月, 2006 1 次提交
    • E
      [PATCH] ufs cleanup · 7b4ee73e
      Evgeniy 提交于
      Here is update of ufs cleanup patch, brought on by the recently fixed
      ubh_get_usb_second() bug that made some ugly code rather painfully
      obvious.  It also includes
      
       - fix compilation warnings which appears if debug mode turn on
       - remove unnecessary duplication of code to support UFS2
      
      I tested it on ufs1 and ufs2 file-systems.
      Signed-off-by: NEvgeniy Dushistov <dushistov@mail.ru>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      7b4ee73e
  9. 10 9月, 2005 1 次提交
  10. 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