Linux NFS development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Trond Myklebust <trondmy@primarydata.com>,
	Anna Schumaker <Anna.Schumaker@Netapp.com>,
	linux-nfs@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] pnfs/blocklayout: require 64-bit ѕector_t
Date: Fri, 11 Aug 2017 17:14:11 +0200	[thread overview]
Message-ID: <20170811151411.GA4301@lst.de> (raw)
In-Reply-To: <20170805085914.3188-1-hch@lst.de>

Trond, Anna,

can you pick this up?  Maybe even for 3.13 given that it should
be pretty harmless for 98% of the configfs, and will prevent problems
for the others.

On Sat, Aug 05, 2017 at 10:59:14AM +0200, Christoph Hellwig wrote:
> The blocklayout code does not compile cleanly for a 32-bit sector_t,
> and also has no reliable checks for devices sizes, which makes it
> unsafe to use with a kernel that doesn't support large block devices.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: 5c83746a0cf2 ("pnfs/blocklayout: in-kernel GETDEVICEINFO XDR parsing")
> ---
>  fs/nfs/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/fs/nfs/Kconfig b/fs/nfs/Kconfig
> index 69d02cf8cf37..5f93cfacb3d1 100644
> --- a/fs/nfs/Kconfig
> +++ b/fs/nfs/Kconfig
> @@ -121,6 +121,7 @@ config PNFS_FILE_LAYOUT
>  config PNFS_BLOCK
>  	tristate
>  	depends on NFS_V4_1 && BLK_DEV_DM
> +	depends on 64BIT || LBDAF
>  	default NFS_V4
>  
>  config PNFS_FLEXFILE_LAYOUT
> -- 
> 2.11.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
---end quoted text---

  reply	other threads:[~2017-08-11 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-05  8:59 [PATCH] pnfs/blocklayout: require 64-bit ѕector_t Christoph Hellwig
2017-08-11 15:14 ` Christoph Hellwig [this message]
2017-08-11 19:00   ` Anna Schumaker

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=20170811151411.GA4301@lst.de \
    --to=hch@lst.de \
    --cc=Anna.Schumaker@Netapp.com \
    --cc=arnd@arndb.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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