From: David Sterba <dsterba@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Josef Bacik <josef@toxicpanda.com>,
Dave Jones <davej@codemonkey.org.uk>,
Filipe Manana <fdmanana@suse.com>,
David Sterba <dsterba@suse.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.6-rc2
Date: Mon, 17 Feb 2020 13:30:54 +0100 [thread overview]
Message-ID: <20200217123054.GH2902@twin.jikos.cz> (raw)
In-Reply-To: <CAHk-=wiG+wjLjuDDNiqfL3iLW25yqsMK_gNEWomyMH=8kxOLwQ@mail.gmail.com>
On Sun, Feb 16, 2020 at 09:08:18PM -0800, Linus Torvalds wrote:
> On Sun, Feb 16, 2020 at 7:02 PM Josef Bacik <josef@toxicpanda.com> wrote:
> >
> > I assume Filipe wrote this based on my patch here
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git/commit/?id=c821555d2b9733d8f483c9e79481c7209e1c1fb0
> >
> > which makes it so we can allocate safely in this context, but that patch hasn't
> > made it's way to you yet. Do you want it now? It was prep for a much less safe
> > patchset, but is fine by itself. Thanks,
>
> I assume it's either that, or revert 28553fa992cb and do it differently..
>
> I'll leave that whole decision to the btrfs people who actually know
> the code and the situations and what the alternative would look
> like...
I'll send a pull request with fix today. The fixes get cherry-picked
from development branch to current rc branch and sometimes affect each
other. I do test the rc branch independently before sending but I
haven't seen the bug Dave reported.
next prev parent reply other threads:[~2020-02-17 12:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 21:32 Linus Torvalds
2020-02-17 2:08 ` Dave Jones
2020-02-17 2:24 ` Linus Torvalds
2020-02-17 3:02 ` Josef Bacik
2020-02-17 5:08 ` Linus Torvalds
2020-02-17 12:30 ` David Sterba [this message]
2020-02-17 16:45 ` Dave Jones
2020-02-17 16:04 ` Filipe Manana
2020-02-17 16:21 ` Chris Wilson
2020-02-17 21:20 ` Linus Torvalds
2020-02-17 21:29 ` Chris Wilson
2020-02-20 22:41 ` Rafael J. Wysocki
2020-02-21 0:46 ` Rafael J. Wysocki
2020-02-21 9:19 ` Chris Wilson
[not found] ` <CAJZ5v0h07em8y5bXcnUTBcjie8pCttADK9QX9W_cB0WQRcDfGQ@mail.gmail.com>
2020-02-21 18:02 ` Linus Torvalds
2020-02-23 23:57 ` Rafael J. Wysocki
2020-02-17 18:42 ` sinisa
2020-02-17 20:17 ` Dominik Brodowski
2020-02-21 1:38 ` Dave Airlie
2020-02-21 2:23 ` [Intel-gfx] " Souza, Jose
2020-02-24 18:24 ` Siniša Bandin
2020-03-02 16:39 ` Siniša Bandin
2020-03-02 17:04 ` Jani Nikula
2020-03-03 7:08 ` Sinisa
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=20200217123054.GH2902@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=davej@codemonkey.org.uk \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®