From: Chris Mason <chris.mason@oracle.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
Dan Merillat <dan.merillat@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
BTRFS Mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: processes stuck in llseek
Date: Thu, 18 Aug 2011 12:00:27 -0400 [thread overview]
Message-ID: <1313683211-sup-3134@shiny> (raw)
In-Reply-To: <CAKcLGm-c8zEi+=j2M_QjvS3GGJezvN_DTbUwb-tZtjPj9ZhNrQ@mail.gmail.com>
Excerpts from Mitch Harder's message of 2011-08-18 11:40:17 -0400:
> On Tue, Aug 16, 2011 at 8:23 PM, Li Zefan <lizf@cn.fujitsu.com> wrote=
:
> > Dan Merillat wrote:
> >> On Tue, Aug 16, 2011 at 8:51 AM, Chris Mason <chris.mason@oracle.c=
om> wrote:
> >>> Excerpts from Dan Merillat's message of 2011-08-15 23:59:50 -0400=
:
> >>
> >>> Dan Carpenter sent a patch for this, I'll get it queued up for rc=
3.
> >>
> >> Can you send it? =C2=A0I'd like to test it to see if it fixes my s=
ystem.
> >
> > Here it is.
> >
> > http://marc.info/?l=3Dlinux-btrfs&m=3D131176036219732&w=3D2
> >
>=20
> Doesn't this patch rely on Josef's SEEK_HOLE/SEEK_DATA patch set whic=
h
> isn't in the kernel yet?
>=20
> http://marc.info/?l=3Dlinux-btrfs&m=3D130927580606177&w=3D2
It does, but the hang was reported on 3.1-rc1, which does have Josef's
code.
-chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Mason <chris.mason@oracle.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
Dan Merillat <dan.merillat@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
BTRFS Mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: processes stuck in llseek
Date: Thu, 18 Aug 2011 12:00:27 -0400 [thread overview]
Message-ID: <1313683211-sup-3134@shiny> (raw)
In-Reply-To: <CAKcLGm-c8zEi+=j2M_QjvS3GGJezvN_DTbUwb-tZtjPj9ZhNrQ@mail.gmail.com>
Excerpts from Mitch Harder's message of 2011-08-18 11:40:17 -0400:
> On Tue, Aug 16, 2011 at 8:23 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
> > Dan Merillat wrote:
> >> On Tue, Aug 16, 2011 at 8:51 AM, Chris Mason <chris.mason@oracle.com> wrote:
> >>> Excerpts from Dan Merillat's message of 2011-08-15 23:59:50 -0400:
> >>
> >>> Dan Carpenter sent a patch for this, I'll get it queued up for rc3.
> >>
> >> Can you send it? I'd like to test it to see if it fixes my system.
> >
> > Here it is.
> >
> > http://marc.info/?l=linux-btrfs&m=131176036219732&w=2
> >
>
> Doesn't this patch rely on Josef's SEEK_HOLE/SEEK_DATA patch set which
> isn't in the kernel yet?
>
> http://marc.info/?l=linux-btrfs&m=130927580606177&w=2
It does, but the hang was reported on 3.1-rc1, which does have Josef's
code.
-chris
next prev parent reply other threads:[~2011-08-18 16:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 3:59 processes stuck in llseek Dan Merillat
2011-08-16 12:36 ` David Sterba
2011-08-16 12:51 ` Chris Mason
2011-08-16 19:22 ` Dan Merillat
2011-08-17 1:23 ` Li Zefan
2011-08-18 15:40 ` Mitch Harder
2011-08-18 15:40 ` Mitch Harder
2011-08-18 16:00 ` Chris Mason [this message]
2011-08-18 16:00 ` Chris Mason
2011-08-18 16:53 ` Mitch Harder
2011-08-18 16:53 ` Mitch Harder
2011-08-18 17:52 ` Chris Mason
2011-08-18 17:52 ` Chris Mason
2011-08-19 16:20 ` Dan Merillat
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=1313683211-sup-3134@shiny \
--to=chris.mason@oracle.com \
--cc=dan.merillat@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mitch.harder@sabayonlinux.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 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.