From: Takashi Iwai <tiwai@suse.de>
To: Chris Mason <clm@fb.com>
Cc: Josef Bacik <jbacik@fb.com>, <linux-btrfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: Fix memory corruption by ulist_add_merge() on 32bit arch
Date: Thu, 14 Aug 2014 11:54:31 +0200 [thread overview]
Message-ID: <s5hvbpvo0q0.wl-tiwai@suse.de> (raw)
In-Reply-To: <53EA513F.3080804@fb.com>
At Tue, 12 Aug 2014 13:39:11 -0400,
Chris Mason wrote:
>
>
>
> On 08/06/2014 11:14 AM, Takashi Iwai wrote:
> >>>
> >>> I meant that I don't care how you do it, if you want to do it the simple way
> >>> first and then send the cleanup later thats fine by me. Thanks,
> >>
> >> Ah, misunderstood. Then please disregard my v2 patches and take just
> >> v1 patch. It's even good for 3.16, if possible.
> >>
> >> I'll send the cleanup patch on top of that.
> >
> > Ping. I don't want to play a bot, but slowly wondering what's going
> > on...
>
> Sorry for the delay Takashi. This patch is a ';' away from compiling.
> I've fixed it up here and I'm running tests, but I wanted to double
> check this was the latest version.
Yes, the first version (posted on July 28) is the right patch.
(Sorry for the missing ";", I thought I did build test on both
architectures.)
thanks,
Takashi
prev parent reply other threads:[~2014-08-14 9:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 8:57 Takashi Iwai
2014-07-28 9:38 ` Wang Shilong
2014-07-28 9:49 ` Takashi Iwai
2014-07-28 13:16 ` Josef Bacik
2014-07-28 13:48 ` Takashi Iwai
2014-07-28 14:01 ` Takashi Iwai
2014-07-30 9:57 ` Takashi Iwai
2014-07-30 14:29 ` Josef Bacik
2014-07-30 15:01 ` Takashi Iwai
2014-07-30 15:05 ` Takashi Iwai
2014-07-30 15:40 ` Josef Bacik
2014-07-30 15:52 ` Takashi Iwai
2014-07-30 16:01 ` Josef Bacik
2014-07-30 16:35 ` Takashi Iwai
2014-07-30 17:00 ` Josef Bacik
2014-07-30 17:45 ` Takashi Iwai
2014-08-06 15:14 ` Takashi Iwai
2014-08-12 17:39 ` Chris Mason
2014-08-14 9:54 ` Takashi Iwai [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=s5hvbpvo0q0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®