From: Christoph Hellwig <hch@lst.de>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] pnfs/blocklayout: serialize GETDEVICEINFO calls
Date: Wed, 5 Nov 2014 09:30:48 +0100 [thread overview]
Message-ID: <20141105083048.GA26612@lst.de> (raw)
In-Reply-To: <20141024142939.GA22472@lst.de>
On Fri, Oct 24, 2014 at 04:29:39PM +0200, Christoph Hellwig wrote:
> Turns out we can't do anything like that with the existing blkmapd
> ABI. The other callers that support concurrency have some sort
> of uniqueue identifier embedded in their messages both on the upcall
> and the downcall, so that the kernel can find the right structure
> on the downcall side.
>
> Because of that I'd like to request inclusion of this patch with a Cc
> to stable for 3.17.
ping? This is an easily expoitable oops, so I'd really like to see the/a
fix in 3.18-rc and 3.17-stable.
Thanks,
Christoph
prev parent reply other threads:[~2014-11-05 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 14:02 blocklayout GETDEVICEINFO fix Christoph Hellwig
2014-09-26 14:02 ` [PATCH] pnfs/blocklayout: serialize GETDEVICEINFO calls Christoph Hellwig
2014-09-26 14:29 ` Trond Myklebust
2014-09-26 15:48 ` Christoph Hellwig
2014-09-26 16:21 ` Trond Myklebust
2014-09-26 16:41 ` Christoph Hellwig
2014-10-24 14:29 ` Christoph Hellwig
2014-11-05 8:30 ` Christoph Hellwig [this message]
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=20141105083048.GA26612@lst.de \
--to=hch@lst.de \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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