All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/2] ocfs2: two bug fixes about xattr and inline-data
Date: Mon, 09 Mar 2009 18:48:35 +0800	[thread overview]
Message-ID: <49B4F403.5070907@oracle.com> (raw)
In-Reply-To: <49B4F1EB.4060601@oracle.com>



Wengang Wang wrote:
>> He runs the command "dd if=/dev/zero of=testfile bs=1 count=3641" which 
>> can not hit the bug2. But I found "dd if=/dev/zero of=testfile bs=3641 
>> count=1" will hit the bug2.
> 
> 3641, cool number!
Hey, 3641 is the max_inline_size_with_xattr + 1 when bs = 4K. ;) So you 
see, they create it intentionally.

Regards,
Tao

  reply	other threads:[~2009-03-09 10:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  3:18 [Ocfs2-devel] [PATCH 0/2] ocfs2: two bug fixes about xattr and inline-data Tiger Yang
2009-03-04  3:21 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: reserve xattr block for directory inode in mknod Tiger Yang
2009-03-05  1:37   ` Joel Becker
2009-03-04  3:21 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: fix check condition of max inline data Tiger Yang
2009-03-04  3:43   ` Tao Ma
2009-03-04  5:47     ` Tiger Yang
2009-03-04  5:49       ` Tao Ma
2009-03-05  1:44         ` Joel Becker
2009-03-05  2:36 ` [Ocfs2-devel] [PATCH 0/2] ocfs2: two bug fixes about xattr and inline-data Joel Becker
2009-03-09  4:17   ` tristan.ye
2009-03-09  4:57     ` Tao Ma
2009-03-09  5:04       ` tristan.ye
2009-03-09  5:42         ` Tao Ma
2009-03-09  6:14           ` tristan.ye
2009-03-09  6:35             ` Tiger Yang
2009-03-09  6:47               ` Joel Becker
2009-03-09  6:54                 ` tristan.ye
2009-03-09  7:02                   ` Tao Ma
2009-03-09  7:24                     ` Tiger Yang
2009-03-09 10:36                       ` Tiger Yang
2009-03-09 10:39                         ` Wengang Wang
2009-03-09 10:48                           ` Tao Ma [this message]
2009-03-09 10:57                         ` tristan.ye
2009-03-09  6:28   ` tristan.ye

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49B4F403.5070907@oracle.com \
    --to=tao.ma@oracle.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.