From: Zhu Yanhai <zhu.yanhai@gmail.com>
To: Itaru Kitayama <kitayama@cl.bb4u.ne.jp>
Cc: chris.mason@oracle.com, linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/inode.c:2642!
Date: Fri, 10 Sep 2010 16:37:26 +0800 [thread overview]
Message-ID: <AANLkTik9k3Er1P408Kzqte9WaW7_HMf=26Yk8jP5bBrY@mail.gmail.com> (raw)
In-Reply-To: <20100910160713.ef663160.kitayama@cl.bb4u.ne.jp>
Please feel free to forward it, as I don't know the addr for -mm tree.
-zyh
2010/9/10 Itaru Kitayama <kitayama@cl.bb4u.ne.jp>:
>
> Thank you, Zhu. Would you send the patch to Andrew or should I pass it on to him?
>
> Itaru
>
> On Thu, 9 Sep 2010 23:30:52 +0800
> Zhu Yanhai <zhu.yanhai@gmail.com> wrote:
>
>> Hi,
>> That's because btrfs_del_dir_entries_in_log() will return the real
>> errno after Andi's
>> commit, so btrfs_unlink_inode() has to check the return value more seriously.
>> A patch for this has been sent out.
>>
>> Regards,
>> Zhu Yanhai
>
prev parent reply other threads:[~2010-09-10 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 13:33 kernel BUG at fs/btrfs/inode.c:2642! Itaru Kitayama
2010-09-09 15:30 ` Zhu Yanhai
2010-09-10 7:07 ` Itaru Kitayama
2010-09-10 8:37 ` Zhu Yanhai [this message]
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='AANLkTik9k3Er1P408Kzqte9WaW7_HMf=26Yk8jP5bBrY@mail.gmail.com' \
--to=zhu.yanhai@gmail.com \
--cc=chris.mason@oracle.com \
--cc=kitayama@cl.bb4u.ne.jp \
--cc=linux-btrfs@vger.kernel.org \
/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).