License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 17:07:57 +03:00
/* SPDX-License-Identifier: GPL-2.0 */
2015-03-25 15:07:37 +03:00
# ifndef _TICK_SCHED_H
# define _TICK_SCHED_H
# include <linux/hrtimer.h>
2015-03-25 15:11:52 +03:00
enum tick_device_mode {
TICKDEV_MODE_PERIODIC ,
TICKDEV_MODE_ONESHOT ,
} ;
struct tick_device {
struct clock_event_device * evtdev ;
enum tick_device_mode mode ;
} ;
2015-03-25 15:07:37 +03:00
enum tick_nohz_mode {
NOHZ_MODE_INACTIVE ,
NOHZ_MODE_LOWRES ,
NOHZ_MODE_HIGHRES ,
} ;
/**
* struct tick_sched - sched tick emulation and no idle tick control / stats
2023-02-22 17:46:42 +03:00
*
2019-03-21 15:09:18 +03:00
* @ inidle : Indicator that the CPU is in the tick idle mode
* @ tick_stopped : Indicator that the idle tick has been stopped
* @ idle_active : Indicator that the CPU is actively in the tick idle mode ;
2021-03-23 00:39:03 +03:00
* it is reset during irq handling phases .
2023-02-22 17:46:42 +03:00
* @ do_timer_last : CPU was the last one doing do_timer before going idle
2019-03-21 15:09:18 +03:00
* @ got_idle_tick : Tick timer function has run with @ inidle set
2023-02-22 17:46:42 +03:00
* @ stalled_jiffies : Number of stalled jiffies detected across ticks
* @ last_tick_jiffies : Value of jiffies seen on last tick
* @ sched_timer : hrtimer to schedule the periodic tick in high
* resolution mode
2015-03-25 15:07:37 +03:00
* @ last_tick : Store the last tick expiry time when the tick
* timer is modified for nohz sleeps . This is necessary
* to resume the tick timer operation in the timeline
* when the CPU returns from nohz sleep .
nohz: Fix collision between tick and other hrtimers, again
This restores commit:
24b91e360ef5: ("nohz: Fix collision between tick and other hrtimers")
... which got reverted by commit:
558e8e27e73f: ('Revert "nohz: Fix collision between tick and other hrtimers"')
... due to a regression where CPUs spuriously stopped ticking.
The bug happened when a tick fired too early past its expected expiration:
on IRQ exit the tick was scheduled again to the same deadline but skipped
reprogramming because ts->next_tick still kept in cache the deadline.
This has been fixed now with resetting ts->next_tick from the tick
itself. Extra care has also been taken to prevent from obsolete values
throughout CPU hotplug operations.
When the tick is stopped and an interrupt occurs afterward, we check on
that interrupt exit if the next tick needs to be rescheduled. If it
doesn't need any update, we don't want to do anything.
In order to check if the tick needs an update, we compare it against the
clockevent device deadline. Now that's a problem because the clockevent
device is at a lower level than the tick itself if it is implemented
on top of hrtimer.
Every hrtimer share this clockevent device. So comparing the next tick
deadline against the clockevent device deadline is wrong because the
device may be programmed for another hrtimer whose deadline collides
with the tick. As a result we may end up not reprogramming the tick
accidentally.
In a worst case scenario under full dynticks mode, the tick stops firing
as it is supposed to every 1hz, leaving /proc/stat stalled:
Task in a full dynticks CPU
----------------------------
* hrtimer A is queued 2 seconds ahead
* the tick is stopped, scheduled 1 second ahead
* tick fires 1 second later
* on tick exit, nohz schedules the tick 1 second ahead but sees
the clockevent device is already programmed to that deadline,
fooled by hrtimer A, the tick isn't rescheduled.
* hrtimer A is cancelled before its deadline
* tick never fires again until an interrupt happens...
In order to fix this, store the next tick deadline to the tick_sched
local structure and reuse that value later to check whether we need to
reprogram the clock after an interrupt.
On the other hand, ts->sleep_length still wants to know about the next
clock event and not just the tick, so we want to improve the related
comment to avoid confusion.
Reported-and-tested-by: Tim Wright <tim@binbash.co.uk>
Reported-and-tested-by: Pavel Machek <pavel@ucw.cz>
Reported-by: James Hartsock <hartsjc@redhat.com>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Rik van Riel <riel@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: stable@vger.kernel.org
Link: http://lkml.kernel.org/r/1492783255-5051-2-git-send-email-fweisbec@gmail.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2017-04-21 17:00:54 +03:00
* @ next_tick : Next tick to be fired when in dynticks mode .
2015-03-25 15:07:37 +03:00
* @ idle_jiffies : jiffies at the entry to idle for idle time accounting
2023-02-22 17:46:42 +03:00
* @ idle_waketime : Time when the idle was interrupted
* @ idle_entrytime : Time when the idle call was entered
* @ nohz_mode : Mode - one state of tick_nohz_mode
* @ last_jiffies : Base jiffies snapshot when next event was last computed
* @ timer_expires_base : Base time clock monotonic for @ timer_expires
* @ timer_expires : Anticipated timer expiration time ( in case sched tick is stopped )
* @ next_timer : Expiry time of next expiring timer for debugging purpose only
* @ idle_expires : Next tick in idle , for debugging purpose only
2015-03-25 15:07:37 +03:00
* @ idle_calls : Total number of idle calls
* @ idle_sleeps : Number of idle calls , where the sched tick was stopped
* @ idle_exittime : Time when the idle state was left
* @ idle_sleeptime : Sum of the time slept in idle with sched tick stopped
* @ iowait_sleeptime : Sum of the time slept in idle with sched tick stopped , with IO outstanding
2019-03-21 15:09:18 +03:00
* @ tick_dep_mask : Tick dependency mask - is set , if someone needs the tick
2023-02-22 17:46:42 +03:00
* @ check_clocks : Notification mechanism about clocksource changes
2015-03-25 15:07:37 +03:00
*/
struct tick_sched {
2023-02-22 17:46:42 +03:00
/* Common flags */
2018-04-06 05:32:37 +03:00
unsigned int inidle : 1 ;
unsigned int tick_stopped : 1 ;
unsigned int idle_active : 1 ;
unsigned int do_timer_last : 1 ;
unsigned int got_idle_tick : 1 ;
2023-02-22 17:46:42 +03:00
/* Tick handling: jiffies stall check */
unsigned int stalled_jiffies ;
unsigned long last_tick_jiffies ;
/* Tick handling */
struct hrtimer sched_timer ;
2015-03-25 15:07:37 +03:00
ktime_t last_tick ;
nohz: Fix collision between tick and other hrtimers, again
This restores commit:
24b91e360ef5: ("nohz: Fix collision between tick and other hrtimers")
... which got reverted by commit:
558e8e27e73f: ('Revert "nohz: Fix collision between tick and other hrtimers"')
... due to a regression where CPUs spuriously stopped ticking.
The bug happened when a tick fired too early past its expected expiration:
on IRQ exit the tick was scheduled again to the same deadline but skipped
reprogramming because ts->next_tick still kept in cache the deadline.
This has been fixed now with resetting ts->next_tick from the tick
itself. Extra care has also been taken to prevent from obsolete values
throughout CPU hotplug operations.
When the tick is stopped and an interrupt occurs afterward, we check on
that interrupt exit if the next tick needs to be rescheduled. If it
doesn't need any update, we don't want to do anything.
In order to check if the tick needs an update, we compare it against the
clockevent device deadline. Now that's a problem because the clockevent
device is at a lower level than the tick itself if it is implemented
on top of hrtimer.
Every hrtimer share this clockevent device. So comparing the next tick
deadline against the clockevent device deadline is wrong because the
device may be programmed for another hrtimer whose deadline collides
with the tick. As a result we may end up not reprogramming the tick
accidentally.
In a worst case scenario under full dynticks mode, the tick stops firing
as it is supposed to every 1hz, leaving /proc/stat stalled:
Task in a full dynticks CPU
----------------------------
* hrtimer A is queued 2 seconds ahead
* the tick is stopped, scheduled 1 second ahead
* tick fires 1 second later
* on tick exit, nohz schedules the tick 1 second ahead but sees
the clockevent device is already programmed to that deadline,
fooled by hrtimer A, the tick isn't rescheduled.
* hrtimer A is cancelled before its deadline
* tick never fires again until an interrupt happens...
In order to fix this, store the next tick deadline to the tick_sched
local structure and reuse that value later to check whether we need to
reprogram the clock after an interrupt.
On the other hand, ts->sleep_length still wants to know about the next
clock event and not just the tick, so we want to improve the related
comment to avoid confusion.
Reported-and-tested-by: Tim Wright <tim@binbash.co.uk>
Reported-and-tested-by: Pavel Machek <pavel@ucw.cz>
Reported-by: James Hartsock <hartsjc@redhat.com>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Rik van Riel <riel@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: stable@vger.kernel.org
Link: http://lkml.kernel.org/r/1492783255-5051-2-git-send-email-fweisbec@gmail.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2017-04-21 17:00:54 +03:00
ktime_t next_tick ;
2015-03-25 15:07:37 +03:00
unsigned long idle_jiffies ;
ktime_t idle_waketime ;
2023-02-22 17:46:42 +03:00
/* Idle entry */
2023-02-22 17:46:44 +03:00
seqcount_t idle_sleeptime_seq ;
2023-02-22 17:46:42 +03:00
ktime_t idle_entrytime ;
/* Tick stop */
enum tick_nohz_mode nohz_mode ;
2015-03-25 15:07:37 +03:00
unsigned long last_jiffies ;
2018-04-05 20:07:57 +03:00
u64 timer_expires_base ;
2023-02-22 17:46:42 +03:00
u64 timer_expires ;
2015-04-15 00:08:58 +03:00
u64 next_timer ;
2015-03-25 15:07:37 +03:00
ktime_t idle_expires ;
2023-02-22 17:46:42 +03:00
unsigned long idle_calls ;
unsigned long idle_sleeps ;
/* Idle exit */
ktime_t idle_exittime ;
ktime_t idle_sleeptime ;
ktime_t iowait_sleeptime ;
/* Full dynticks handling */
2016-03-24 17:38:00 +03:00
atomic_t tick_dep_mask ;
2023-02-22 17:46:42 +03:00
/* Clocksource changes */
unsigned long check_clocks ;
2015-03-25 15:07:37 +03:00
} ;
extern struct tick_sched * tick_get_tick_sched ( int cpu ) ;
extern void tick_setup_sched_timer ( void ) ;
# if defined CONFIG_NO_HZ_COMMON || defined CONFIG_HIGH_RES_TIMERS
extern void tick_cancel_sched_timer ( int cpu ) ;
# else
static inline void tick_cancel_sched_timer ( int cpu ) { }
# endif
2015-07-07 17:29:38 +03:00
# ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
extern int __tick_broadcast_oneshot_control ( enum tick_broadcast_state state ) ;
# else
static inline int
__tick_broadcast_oneshot_control ( enum tick_broadcast_state state )
{
return - EBUSY ;
}
# endif
2015-03-25 15:07:37 +03:00
# endif
