lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 25 Oct 2017 23:09:50 +0200
From:   Arnd Bergmann <>
To:     Greg Kroah-Hartman <>
Cc:     Linux Kernel Mailing List <>,
        "# 3.4.x" <>,
        Brian Foster <>,
        Geert Uytterhoeven <>,
        "Darrick J. Wong" <>
Subject: Re: [PATCH 4.13 85/85] xfs: move two more RT specific functions into CONFIG_XFS_RT

On Tue, Oct 24, 2017 at 3:07 PM, Greg Kroah-Hartman
<> wrote:
> 4.13-stable review patch.  If anyone has any objections, please let me know.
> ------------------
> From: Arnd Bergmann <>
> commit 785545c8982604fe3ba79d16409e83993be77d5e upstream.
> The last cleanup introduced two harmless warnings:
> fs/xfs/xfs_fsmap.c:480:1: warning: '__xfs_getfsmap_rtdev' defined but not used
> fs/xfs/xfs_fsmap.c:372:1: warning: 'xfs_getfsmap_rtdev_rtbitmap_helper' defined but not used
> This moves those two functions as well.
> Fixes: bb9c2e543325 ("xfs: move more RT specific code under CONFIG_XFS_RT")

I haven't checked what kernel contains bb9c2e543325, but if I remember correctly
the warning only showed up during the 4.14-rc cycle, so unless you backported
bb9c2e543325 or I misremembered it, backporting my fix would be wrong.

I lost remote access to my build box, so I can't verify at the moment.
Can you double-check that we want this backport?


Powered by blists - more mailing lists