From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Eryu Guan <guaneryu@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
xfs <linux-xfs@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Chinner <david@fromorbit.com>,
Salvatore Bonaccorso <carnil@debian.org>,
Security Officers <security@kernel.org>,
Debian Security Team <team@security.debian.org>,
benjamin.moody@gmail.com, Ben Hutchings <benh@debian.org>,
fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH v2] generic: test for failure to unlock inode after chgrp fails with EDQUOT
Date: Tue, 27 Aug 2019 20:47:09 +0200 [thread overview]
Message-ID: <20190827184709.GB2987@kroah.com> (raw)
In-Reply-To: <20190827152648.GB534@kroah.com>
On Tue, Aug 27, 2019 at 05:26:48PM +0200, Greg KH wrote:
> On Tue, Aug 27, 2019 at 05:19:27PM +0200, Thomas Gleixner wrote:
> > Darrick,
> >
> > On Tue, 27 Aug 2019, Darrick J. Wong wrote:
> >
> > > On Tue, Aug 27, 2019 at 08:13:19AM +0200, Thomas Gleixner wrote:
> > > > On Mon, 26 Aug 2019, Darrick J. Wong wrote:
> > > > > +++ b/tests/generic/719
> > > > > @@ -0,0 +1,59 @@
> > > > > +#! /bin/bash
> > > > > +# SPDX-License-Identifier: GPL-2.0-or-newer
> > > >
> > > > Please run scripts/spdxcheck.py on that file and consult the licensing
> > > > documentation.
> > >
> > > -or-later, sorry.
> > >
> > > So .... now that everyone who wanted these SPDX identifiers have spread
> > > "GPL-2.0+" around the kernel and related projects (xfsprogs, xfstests)
> > > just in time for SPDX 3.0 to deprecate the "+" syntax, what are we
> > > supposed to do? Another treewide change to fiddle with SPDX syntax?
> > > Can we just put:
> > >
> > > Valid-License-Identifier: GPL-2.0+
> > > Valid-License-Identifier: GPL-2.0-or-later
> > >
> > > in the LICENSES/GPL-2.0 file like the kernel does?
> >
> > The kernel is not going to change that because we have started with this
> > before the s/+/-or-later/ happened. Tools need to read both.
> >
> > > Is that even going to stay that way? I thought I heard that Greg was
> > > working on phasing out the "2.0+" tags since SPDX deprecated that?
> >
> > For new stuff we should use -or-later methinks.
>
> For new stuff, if you wish to be "kind" to some community members, we
> should use "-or-later" and "-only". But as you say, both are fine.
>
> And no, I am NOT working on phasing out any SPDX tags for the older
> stuff. Personally, I like the older ones.
>
> > Yeah, we should add a MAINTAINERS entry for LICENSES. Greg and myself are
> > going to be volunteered I fear.
>
> Yeah, I figured it was only a matter of time. Let me go create an entry
> given that we already have git tree for it in linux-next for a while
> now...
Now submitted:
https://lore.kernel.org/lkml/20190827172519.GA28849@kroah.com/T/#u
next prev parent reply other threads:[~2019-08-27 18:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 4:18 [PATCH v2] generic: test for failure to unlock inode after chgrp fails with EDQUOT Darrick J. Wong
2019-08-27 6:13 ` Thomas Gleixner
2019-08-27 15:04 ` Darrick J. Wong
2019-08-27 15:19 ` Thomas Gleixner
2019-08-27 15:26 ` Greg KH
2019-08-27 18:47 ` Greg KH [this message]
2019-08-27 15:24 ` Greg KH
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=20190827184709.GB2987@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benh@debian.org \
--cc=benjamin.moody@gmail.com \
--cc=carnil@debian.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=security@kernel.org \
--cc=team@security.debian.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).