stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* 6.6.19 won't compile with " [*] Compile the kernel with warnings as errors"
@ 2024-03-01 14:42 Rainer Fiebig
  2024-03-01 17:56 ` Nathan Chancellor
  0 siblings, 1 reply; 4+ messages in thread
From: Rainer Fiebig @ 2024-03-01 14:42 UTC (permalink / raw)
  To: stable@vger.kernel.org

The problem seems to be in fs/ntfs3/frecord.c.  Original messages were
in German, so here's my translation (original at the end of the post):

[...]
  CC      lib/zstd/common/zstd_common.o
  CC      arch/x86/kernel/cpu/feat_ctl.o
fs/ntfs3/frecord.c: In Funktion »ni_read_frame«:
fs/ntfs3/frecord.c:2460:16: Error: variable >>i_size<< is not used"
[-Werror=unused-variable]
 2460 |         loff_t i_size = i_size_read(&ni->vfs_inode);
      |                ^~~~~~
  AR      lib/zstd/built-in.a
[...]
cc1: All warnings are treated as errors
make[4]: *** [scripts/Makefile.build:243: fs/ntfs3/frecord.o] error 1
make[3]: *** [scripts/Makefile.build:480: fs/ntfs3] error 2
make[3]: *** Waiting for not yet finished processes....
[...]

Let me know if you need further information.  Thanks.

Rainer


--
Original messages:
[...]
  CC      lib/zstd/common/zstd_common.o
  CC      arch/x86/kernel/cpu/feat_ctl.o
fs/ntfs3/frecord.c: In Funktion »ni_read_frame«:
fs/ntfs3/frecord.c:2460:16: Fehler: Variable »i_size« wird nicht
verwendet [-Werror=unused-variable]
 2460 |         loff_t i_size = i_size_read(&ni->vfs_inode);
      |                ^~~~~~
  AR      lib/zstd/built-in.a
  CC      lib/bug.o
  CC      fs/udf/inode.o
  CC      arch/x86/kernel/cpu/intel.o
  CC      arch/x86/kernel/process_64.o
  CC      kernel/events/callchain.o
  CC      lib/buildid.o
cc1: Alle Warnungen werden als Fehler behandelt
make[4]: *** [scripts/Makefile.build:243: fs/ntfs3/frecord.o] Fehler 1
make[3]: *** [scripts/Makefile.build:480: fs/ntfs3] Fehler 2
make[3]: *** Es wird auf noch nicht beendete Prozesse gewartet....
  CC      kernel/events/hw_breakpoint.o
  CC      lib/clz_tab.o
  CC      lib/cmdline.o
  CC      fs/udf/lowlevel.o
[...]




-- 
The truth always turns out to be simpler than you thought.
Richard Feynman

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 6.6.19 won't compile with " [*] Compile the kernel with warnings as errors"
  2024-03-01 14:42 6.6.19 won't compile with " [*] Compile the kernel with warnings as errors" Rainer Fiebig
@ 2024-03-01 17:56 ` Nathan Chancellor
  2024-03-02  9:30   ` Rainer Fiebig
  0 siblings, 1 reply; 4+ messages in thread
From: Nathan Chancellor @ 2024-03-01 17:56 UTC (permalink / raw)
  To: Greg Kroah-Hartman, Sasha Levin; +Cc: stable@vger.kernel.org, Rainer Fiebig

On Fri, Mar 01, 2024 at 03:42:17PM +0100, Rainer Fiebig wrote:
> fs/ntfs3/frecord.c: In Funktion »ni_read_frame«:
> fs/ntfs3/frecord.c:2460:16: Error: variable >>i_size<< is not used"
> [-Werror=unused-variable]
>  2460 |         loff_t i_size = i_size_read(&ni->vfs_inode);
>       |                ^~~~~~

This is a regression that was inherited from mainline because
commit 4fd6c08a16d7 ("fs/ntfs3: Use i_size_read and i_size_write") was
applied to stable without commit c8e314624a16 ("fs/ntfs3: fix build
without CONFIG_NTFS3_LZX_XPRESS").

Cheers,
Nathan

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 6.6.19 won't compile with " [*] Compile the kernel with warnings as errors"
  2024-03-01 17:56 ` Nathan Chancellor
@ 2024-03-02  9:30   ` Rainer Fiebig
  2024-03-02 17:03     ` Greg Kroah-Hartman
  0 siblings, 1 reply; 4+ messages in thread
From: Rainer Fiebig @ 2024-03-02  9:30 UTC (permalink / raw)
  To: Nathan Chancellor, Greg Kroah-Hartman, Sasha Levin; +Cc: stable@vger.kernel.org

Am 01.03.24 um 18:56 schrieb Nathan Chancellor:
> On Fri, Mar 01, 2024 at 03:42:17PM +0100, Rainer Fiebig wrote:
>> fs/ntfs3/frecord.c: In Funktion »ni_read_frame«:
>> fs/ntfs3/frecord.c:2460:16: Error: variable >>i_size<< is not used"
>> [-Werror=unused-variable]
>>  2460 |         loff_t i_size = i_size_read(&ni->vfs_inode);
>>       |                ^~~~~~
> 
> This is a regression that was inherited from mainline because
> commit 4fd6c08a16d7 ("fs/ntfs3: Use i_size_read and i_size_write") was
> applied to stable without commit c8e314624a16 ("fs/ntfs3: fix build
> without CONFIG_NTFS3_LZX_XPRESS").
With  CONFIG_NTFS3_LZX_XPRESS=y  the build was fine.
Thanks.

Rainer

> 
> Cheers,
> Nathan
> 


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 6.6.19 won't compile with " [*] Compile the kernel with warnings as errors"
  2024-03-02  9:30   ` Rainer Fiebig
@ 2024-03-02 17:03     ` Greg Kroah-Hartman
  0 siblings, 0 replies; 4+ messages in thread
From: Greg Kroah-Hartman @ 2024-03-02 17:03 UTC (permalink / raw)
  To: Rainer Fiebig; +Cc: Nathan Chancellor, Sasha Levin, stable@vger.kernel.org

On Sat, Mar 02, 2024 at 10:30:54AM +0100, Rainer Fiebig wrote:
> Am 01.03.24 um 18:56 schrieb Nathan Chancellor:
> > On Fri, Mar 01, 2024 at 03:42:17PM +0100, Rainer Fiebig wrote:
> >> fs/ntfs3/frecord.c: In Funktion »ni_read_frame«:
> >> fs/ntfs3/frecord.c:2460:16: Error: variable >>i_size<< is not used"
> >> [-Werror=unused-variable]
> >>  2460 |         loff_t i_size = i_size_read(&ni->vfs_inode);
> >>       |                ^~~~~~
> > 
> > This is a regression that was inherited from mainline because
> > commit 4fd6c08a16d7 ("fs/ntfs3: Use i_size_read and i_size_write") was
> > applied to stable without commit c8e314624a16 ("fs/ntfs3: fix build
> > without CONFIG_NTFS3_LZX_XPRESS").
> With  CONFIG_NTFS3_LZX_XPRESS=y  the build was fine.

Thanks for the report, will go do a new release with this fix in it.

greg k-h

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-03-02 17:03 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-03-01 14:42 6.6.19 won't compile with " [*] Compile the kernel with warnings as errors" Rainer Fiebig
2024-03-01 17:56 ` Nathan Chancellor
2024-03-02  9:30   ` Rainer Fiebig
2024-03-02 17:03     ` Greg Kroah-Hartman

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).