linux-kernel - Re: linux-next: build warning after merge of the usb tree

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YtaUYmzTfKmx0Ek0@kroah.com>
Date:   Tue, 19 Jul 2022 13:24:18 +0200
From:   Greg KH <greg@...ah.com>
To:     Maxim Devaev <mdevaev@...il.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the usb tree

On Tue, Jul 19, 2022 at 01:25:59PM +0300, Maxim Devaev wrote:
> В Tue, 19 Jul 2022 19:43:37 +1000
> Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> > Hi all,
> > 
> > After merging the usb tree, today's linux-next build (htmldocs) produced
> > this warning:
> > 
> > Documentation/ABI/testing/configfs-usb-gadget-mass-storage:17: WARNING: Malformed table.
> > Text in column margin in table line 14.
> > 
> > ===========     ==============================================
> > file            The path to the backing file for the LUN.
> >                 Required if LUN is not marked as removable.
> > ro              Flag specifying access to the LUN shall be
> >                 read-only. This is implied if CD-ROM emulation
> >                 is enabled as well as when it was impossible
> >                 to open "filename" in R/W mode.
> > removable       Flag specifying that LUN shall be indicated as
> >                 being removable.
> > cdrom           Flag specifying that LUN shall be reported as
> >                 being a CD-ROM.
> > nofua           Flag specifying that FUA flag
> >                 in SCSI WRITE(10,12)
> > forced_eject    This write-only file is useful only when
> >                 the function is active. It causes the backing
> >                 file to be forcibly detached from the LUN,
> >                 regardless of whether the host has allowed it.
> >                 Any non-zero number of bytes written will
> >                 result in ejection.
> > ===========     ==============================================
> > 
> > Introduced by commit
> > 
> >   421c8d9a20da ("usb: gadget: f_mass_storage: forced_eject attribute")
> > 
> 
> Sorry. Should I send a patch?

Yes please.