From: Tiger Yang <tiger.yang@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext3/4: fix uninitialized bs in ext3/4_xattr_set_handle()
Date: Tue, 13 May 2008 15:48:19 +0800 [thread overview]
Message-ID: <482947C3.9040601@oracle.com> (raw)
In-Reply-To: <4828DE73.2070001@redhat.com>
Hi, Eric,
I don't have tesecase about this bug. I did the test manually. I use
khexedit to confirm the attributes whether in inody or block.
The problem about this bug is we want to replace an existing attribute
in ibody with big size value which larger than free space in ibody.
Because we didn't do block_find(), so the struct bs have not been
initialized. Then when we try to set attribute in block by block_set(),
we find bs->base is empty, we need alloc a new block for attributes. The
old block pointed by i_file_acl will lost with attributes in it.
Best regards,
tiger
Eric Sandeen wrote:
> Tiger Yang wrote:
>
>> Hi,
>> I met a bug when I try to replace a xattr entry in ibody with a big size
>> value. But in ibody there has no space for the new value. So it should
>> set new xattr entry in block and remove the old xattr entry in ibody.
>>
>> Best regards,
>> tiger
>>
>>
>
> Tiger, do you have a testcase handy to demonstrate this?
>
> Is the new, large out-of-inode xattr unique so that it does not match
> any existing attribute block, I assume?
>
> Thanks,
>
> -Eric
>
next prev parent reply other threads:[~2008-05-13 7:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 3:24 [PATCH] ext3/4: fix uninitialized bs in ext3/4_xattr_set_handle() Tiger Yang
2008-05-13 0:02 ` Andrew Morton
2008-05-13 2:31 ` Tiger Yang
2008-05-13 20:00 ` Andreas Dilger
2008-05-14 10:56 ` Andreas Gruenbacher
2008-05-14 16:00 ` [stable] " Greg KH
2008-05-14 17:28 ` Andrew Morton
2008-05-14 22:30 ` Theodore Tso
2008-05-14 22:54 ` Andrew Morton
2008-05-13 0:18 ` Eric Sandeen
2008-05-13 7:48 ` Tiger Yang [this message]
2008-05-13 12:48 ` Eric Sandeen
2008-05-13 8:48 ` Kalpak Shah
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=482947C3.9040601@oracle.com \
--to=tiger.yang@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).