From: Piotr Szymaniak <szarpaj@grubelek.pl>
To: "Zhong, Xin" <xin.zhong@intel.com>
Cc: "Maria Wikström" <maria@ponstudios.se>,
"Johannes Hirte" <johannes.hirte@fem.tu-ilmenau.de>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2]Btrfs: pwrite blocked when writing from the mmaped buffer of the same page
Date: Fri, 25 Feb 2011 00:35:23 +0100 [thread overview]
Message-ID: <20110224233523.GK26836@wloczykij> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB686421B24FB@shsmsx502.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 2887 bytes --]
On Mon, Feb 21, 2011 at 09:51:11AM +0800, Zhong, Xin wrote:
> The backtrace in your attachment looks like a known bug of 2.6.37 which have already been fixed in 2.6.38. I have no idea why latest btrfs still hang in your environment if there's no debug info...
Hi list.
I'm watching this list for a while because it seems, that I'm also
affected by this bug. In the archives I found someone with Gentoo system
with freezing `svn info' (thats why I joined). Well, seems that I have
same issue here.
Attached latest _rc kernel sysrq+t output (first part when the `svn
info' freezed on libgcrypt, and second after ctrl+c that emerge).
Seems that my backtrace is small compared to Marias. I'm missing some
features in kernel to get larger backtraces?
Piotr Szymaniak.
> -----Original Message-----
> From: Maria Wikström [mailto:maria@ponstudios.se]
> Sent: Friday, February 18, 2011 7:32 PM
> To: Zhong, Xin
> Cc: Johannes Hirte; linux-btrfs@vger.kernel.org
> Subject: RE: [PATCH v2]Btrfs: pwrite blocked when writing from the mmaped buffer of the same page
>
>
> Seems like my reply got eaten by the lists spam filter, so I resend with attachment compressed. Should have thought of that :p
>
>
> fre 2011-02-11 klockan 12:39 +0800 skrev Zhong, Xin:
> > Hi,
> >
> > Could you paste the output of sysrq+t here? Thanks!
>
> Yes, it's in the attachment. I tried latest btrfs from git (last commit Mon Feb 14 00:45:29 2011 +0000) but it hang so bad that I couldn't get the output from sysrq+t to hit the disk. So the output is from vanilla
> 2.6.37
>
> // Maria
>
> > -----Original Message-----
> > From: Johannes Hirte [mailto:johannes.hirte@fem.tu-ilmenau.de]
> > Sent: Wednesday, February 02, 2011 7:35 AM
> > To: Zhong, Xin
> > Cc: Maria Wikström; linux-btrfs@vger.kernel.org
> > Subject: Re: [PATCH v2]Btrfs: pwrite blocked when writing from the
> > mmaped buffer of the same page
> >
> > On Friday 28 January 2011 04:53:24 Zhong, Xin wrote:
> > > Could you describe the steps to recreate it?
> > > It will be a great help for me to look further. Thanks!
> >
> > It's a little strange. I have to systems with btrfs, both
> > Gentoo-based. One is affected by this bug the other is not. On the
> > affected system it is enough to do a 'emerge dev-libs/libgcrypt' that
> > should normaly compile and install libgcrypt. The emerge command is
> > part of portage, the package management of Gentoo.
> > The strace output looks similar to the one from Maria:
> >
>
> N?????r??y????b?X??ǧv?^?){.n?+????{?n?߲)????w*\x1fjg???\x1e?????ݢj/???z?ޖ??2?ޙ????&?)ߡ?a??\x7f??\x1e?G???h?\x0f?j:+v???w??٥
--
Druzyna futbolowa tutaj jest do niczego, ale ucze sie troche pilki
noznej. Trener mowi, ze pilka nozna to futbol dla inteligentnych, a
futbol to futbol dla kretynow.
-- Stephen King, "The Dead Zone"
[-- Attachment #1.2: vanilla-2.6.38-rc6_sysrq-t.bz2 --]
[-- Type: application/x-bzip2, Size: 4837 bytes --]
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-24 23:35 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 9:30 [PATCH v2]Btrfs: pwrite blocked when writing from the mmaped buffer of the same page Zhong, Xin
2011-01-27 13:09 ` Johannes Hirte
2011-01-27 22:12 ` Maria Wikström
2011-01-28 1:26 ` Zhong, Xin
2011-01-28 2:54 ` Johannes Hirte
2011-01-28 3:53 ` Zhong, Xin
2011-02-01 23:34 ` Johannes Hirte
2011-02-11 4:39 ` Zhong, Xin
2011-02-18 11:31 ` Maria Wikström
2011-02-21 1:51 ` Zhong, Xin
2011-02-24 14:51 ` Maria Wikström
2011-02-24 15:55 ` Mitch Harder
2011-02-24 16:00 ` Chris Mason
2011-02-24 16:03 ` Mitch Harder
2011-02-24 16:19 ` Chris Mason
2011-02-24 16:32 ` Mitch Harder
[not found] ` <AANLkTinvyb-bTVVignd1KGojvh-QrYCFmCnwYKBsYC_2@mail.gmail.com>
2011-02-25 17:11 ` Mitch Harder
2011-02-25 18:43 ` Mitch Harder
2011-02-25 19:19 ` Chris Mason
2011-02-28 1:46 ` [PATCH] btrfs file write debugging patch Chris Mason
2011-02-28 8:56 ` Zhong, Xin
2011-02-28 14:02 ` Chris Mason
2011-02-28 10:13 ` Johannes Hirte
2011-02-28 14:00 ` Chris Mason
2011-02-28 16:10 ` Josef Bacik
2011-02-28 16:45 ` Maria Wikström
2011-02-28 17:47 ` Mitch Harder
2011-02-28 20:20 ` Mitch Harder
2011-03-01 5:09 ` Mitch Harder
2011-03-01 10:14 ` Zhong, Xin
2011-03-01 11:56 ` Zhong, Xin
2011-03-01 14:54 ` Mitch Harder
2011-03-01 14:51 ` Mitch Harder
2011-03-01 21:56 ` Piotr Szymaniak
2011-02-24 23:35 ` Piotr Szymaniak [this message]
2011-02-22 22:27 ` [PATCH v2]Btrfs: pwrite blocked when writing from the mmaped buffer of the same page Johannes Hirte
2011-02-23 7:27 ` Zhong, Xin
2011-02-23 21:56 ` Chris Mason
2011-02-23 23:02 ` Johannes Hirte
2011-02-24 15:23 ` Chris Mason
2011-01-28 16:47 ` Maria Wikström
2011-01-28 18:27 ` Rui Miguel Silva
2011-01-29 15:38 ` Maria Wikström
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=20110224233523.GK26836@wloczykij \
--to=szarpaj@grubelek.pl \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=maria@ponstudios.se \
--cc=xin.zhong@intel.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).