From: "J. Bruce Fields" <bfields@fieldses.org>
To: Marc Meledandri <m.meledandri@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Issues with a rather unusual configured NFS server
Date: Wed, 2 Oct 2013 10:04:46 -0400 [thread overview]
Message-ID: <20131002140446.GC14808@fieldses.org> (raw)
In-Reply-To: <CACFbnrxWCTnudK5GJK0=xpiE7xym=Jm4apMSbBHTHF-oavJP5g@mail.gmail.com>
On Tue, Oct 01, 2013 at 09:24:34PM -0400, Marc Meledandri wrote:
> On Tue, Oct 1, 2013 at 10:34 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
> > On Sat, Sep 28, 2013 at 11:37:40AM -0400, Marc Meledandri wrote:
> >> I was pointed at this thread by the linux-ext4 folks as relevant to my
> >> issue on kernels in
> >> the 3.10.x series. I see this commit was tagged for 3.12-rc2 on git,
> >> and wondering if it will be
> >> rebased for previous kernels? Maybe my issue (oops at shutdown) is
> >> caused by something
> >> else entirely? Thanks!
> >
> > That patch probably should have been cc'd to stable for kernels since
> > 3.10....
> >
> > Do you have a reproduceable test case? Would it be possible for you to
> > confirm that this fixes your problem if applied on top of 3.10.x?
> >
> > --b.
> >
>
> Thanks for replying. Regarding confirmation, the patch does not apply
> cleanly to 3.10.x kernels, but needs to be backported/rebased. I began
> that process, as it's a small patch, but didn't want to step on, or
> conflict with other changes that hadn't been merged yet from the
> latest nfs codebase if such changes are forthcoming.
Oops, hadn't noticed the patch didn't apply to 3.10.x. OK, let me know
when you have that. In fact, if you could just send it to
stable@vger.kernel.org and cc: me then I'll ACK it.
--b.
>
> Regarding STR, I was seeing this on vanilla kernels 3.10.10 and
> 3.10.11 on shutdown (hangs with oops), and didn't pin down the exact
> conditions. I have the simplest of nfs setups with a single
> export/mount point and single client. I've recently built 3.10.13 with
> no patches and will try to reproduce the oops. I think I need to leave
> a client connected during shutdown.
>
> Will follow up with more info...
next prev parent reply other threads:[~2013-10-02 14:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 15:37 Issues with a rather unusual configured NFS server Marc Meledandri
2013-10-01 14:34 ` J. Bruce Fields
2013-10-02 1:24 ` Marc Meledandri
2013-10-02 14:04 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-11 9:48 Toralf Förster
2013-08-12 14:36 ` Jan Kara
2013-08-13 21:53 ` J. Bruce Fields
2013-08-14 16:44 ` Toralf Förster
2013-08-27 18:06 ` J. Bruce Fields
2013-08-28 17:21 ` Toralf Förster
2013-09-07 20:44 ` Toralf Förster
2013-09-10 14:09 ` J. Bruce Fields
2013-09-10 15:51 ` Toralf Förster
2013-09-22 16:58 ` Toralf Förster
2013-09-23 17:41 ` J. Bruce Fields
2013-10-02 20:29 ` Toralf Förster
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=20131002140446.GC14808@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=m.meledandri@gmail.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).