From: Adam Borowski <kilobyte@angband.pl>
To: Gabriel C <nix.or.die@gmail.com>
Cc: Chris Mason <clm@fb.com>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
linux-btrfs@vger.kernel.org, quwenruo@cn.fujitsu.com
Subject: Re: A lot warnings in dmesg while running thunderbird
Date: Fri, 22 Jul 2016 02:53:18 +0200 [thread overview]
Message-ID: <20160722005318.GA12929@angband.pl> (raw)
In-Reply-To: <2cf60d0b-1d80-ae27-4d37-fa07681afb77@gmail.com>
On Thu, Jul 21, 2016 at 11:25:02PM +0200, Gabriel C wrote:
> On 21.07.2016 14:56, Chris Mason wrote:
> > On 07/20/2016 01:50 PM, Gabriel C wrote:
> >> After 24h of running the program and thundirbird all is still fine here.
> >>
> >> I let it run one more day.. But looks very good.
> >>
> >
> > Thanks for your time in helping to track this down. It'll go into the
> > next merge window and be cc'd to stable.
> >
>
> You are welcome :)
>
> Test program was running without problems for 52h.. I think your fix is fine :)
AOL.
I haven't tested it for as long, but had it running concurrently with some
big compiles (kernel, sbuild ie snapshot+dpkg+subv delete), cleanup of
several tens of daily snapshots, etc.
No problems.
--
An imaginary friend squared is a real enemy.
next prev parent reply other threads:[~2016-07-22 0:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 10:24 A lot warnings in dmesg while running thunderbird Gabriel C
2016-07-07 19:21 ` Chris Mason
2016-07-08 9:57 ` Gabriel C
2016-07-08 12:41 ` Chris Mason
2016-07-08 14:05 ` Gabriel C
2016-07-08 15:02 ` Gabriel C
2016-07-08 16:02 ` Chris Mason
2016-07-08 18:21 ` Adam Borowski
2016-07-08 21:47 ` Adam Borowski
2016-07-08 18:23 ` Duncan
2016-07-11 5:58 ` Chandan Rajendra
2016-07-11 10:51 ` Chris Mason
2016-07-19 11:05 ` Chris Mason
2016-07-20 0:11 ` Gabriel C
2016-07-20 13:50 ` Chris Mason
2016-07-20 17:50 ` Gabriel C
2016-07-21 12:56 ` Chris Mason
2016-07-21 21:25 ` Gabriel C
2016-07-22 0:53 ` Adam Borowski [this message]
2016-07-25 0:36 ` Dave Chinner
2016-08-01 15:23 ` Chris Mason
2016-07-15 19:35 ` Chris Mason
2016-07-15 21:08 ` Chris Mason
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=20160722005318.GA12929@angband.pl \
--to=kilobyte@angband.pl \
--cc=chandan@linux.vnet.ibm.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nix.or.die@gmail.com \
--cc=quwenruo@cn.fujitsu.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.