4.13-stable review patch. If anyone has any objections, please let me know.
--
From: David Kozub
commit eb39a7c0355393c5a8d930f342ad7a6231b552c4 upstream.
The interrupt handler mfgpt_tick() is not robust versus spurious interrupts
which happen before the clock event device is
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit c503dd38f850be28867ef7a42d9abe5ade81a9bd upstream.
With KASAN and a couple of other patches applied, this driver is one
of the few remaining ones that actually use more th
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Chen-Yu Tsai
commit a231d2783c332ef3e3ba238e82dbe599ff41ba14 upstream.
When the second display pipeline device nodes for the A31/A31s were
added, it was not known that the TCONs could (through
Em Mon, Oct 23, 2017 at 09:39:57PM +0200, Milian Wolff escreveu:
> So to fix this all, I guess the suggested approach by Namhyung would be best,
> i.e. fixup my initial match_addresses to take the map, and then if the map is
> valid also take the dso into account when comparing the addresses:
>
On Tue, Oct 24, 2017 at 5:52 AM, Bryan O'Donoghue
wrote:
> On 24/10/17 13:47, Kees Cook wrote:
>>
>> On Tue, Oct 24, 2017 at 2:40 AM, Bryan O'Donoghue
>> wrote:
>>>
>>> On 24/10/17 10:35, Bryan O'Donoghue wrote:
On 24/10/17 09:25, Kees Cook wrote:
>
>
> In preparation f
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Quinn Tran
commit a9e170e28636fd577249f39029d59e4e960a42b8 upstream.
Fixes following stack trace
kernel: Call Trace:
kernel: dump_stack+0x63/0x84
kernel: __warn+0xd1/0xf0
kernel: warn_slowpat
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 1c0edc3633b56000e18d82fc241e3995ca18a69e upstream.
Andrey used the syzkaller fuzzer to find an out-of-bounds memory
access in usb_get_bos_descriptor(). The code wasn't check
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Christian Borntraeger
commit b7662eef14caf4f582d453d45395825b5a8f594c upstream.
On CPU hotplug some cpu stats contain bogus values:
$ cat /proc/stat
cpu 0 0 49 1280 0 0 0 3 0 0
cpu0 0 0 49 61
* Baoquan He wrote:
> For register_page_bootmem_memmap(), the 3rd argument 'size' indicates
> the number of pages which are inside the memory section, not a size.
>
> Signed-off-by: Baoquan He
> ---
> arch/x86/mm/init_64.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Jussi Laako
commit 9bb201a5d5acc733943e8af7151cceab9d976a69 upstream.
Add native DSD support quirk for Pro-Ject Pre Box S2 Digital USB id
2772:0230.
Signed-off-by: Jussi Laako
Signed-off-by:
On 24/10/17 14:14, Kees Cook wrote:
On Tue, Oct 24, 2017 at 5:52 AM, Bryan O'Donoghue
wrote:
On 24/10/17 13:47, Kees Cook wrote:
On Tue, Oct 24, 2017 at 2:40 AM, Bryan O'Donoghue
wrote:
On 24/10/17 10:35, Bryan O'Donoghue wrote:
On 24/10/17 09:25, Kees Cook wrote:
In preparation for
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Adrian Hunter
commit eb701ce16a45ed9880897c48f05ee608d77c72e3 upstream.
The default for d3_retune is true, but that was not being set in all cases,
which results in eMMC errors because re-tuni
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: ZHU Yi (ST-FIR/ENG1-Zhu)
commit fb5b91d61bebc24686ffc379138fd67808b1a1e6 upstream.
Enable FLEXCAN_QUIRK_BROKEN_WERR_STATE and
FLEXCAN_QUIRK_BROKEN_PERR_STATE for p1010 to report correct state
Hi Huacai,
On 2017-10-23 09:12, Huacai Chen wrote:
Make dma_get_cache_alignment() to accept a 'dev' argument. As a result,
it can return different alignments due to different devices' I/O cache
coherency.
Currently, ARM/ARM64 and MIPS support coherent & noncoherent devices
co-exist. This may be
Em Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar escreveu:
>
> * Jiri Olsa wrote:
>
> > I recently made some changes on threaded record, which are based
> > on Namhyungs time* API, which is needed to read/sort the data afterwards
> >
> > but I wasn't able to get any substantial and constan
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 0c3aae9bd59978fb8c3557d7883380bef0f2cfa1 upstream.
The musb delayed irq work was never flushed on suspend, something which
since 4.9 can lead to an external abort if the wo
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Lars-Peter Clausen
commit be94a6f6d488b4767662e8949dc62361bd1d6311 upstream.
Add missing break in iio_simple_dummy_write_event_config() for the voltage
threshold event enable attribute. Withou
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit 845d584f41eac3475c21e4a7d5e88d0f6e410cf7 upstream.
Taking the uurb->buffer_length userspace passes in as a maximum for the
actual urbs transfer_buffer_length causes 2 seri
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 31dc3f819bac28a0990b36510197560258ab7421 upstream.
Add device-id entry for (Honeywell) Metrologic MS7820 bar code scanner.
The device has two interfaces (in this mode?); a
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Phil Elwell
commit c97d96b4e612c7dc1b37d7afc61b598a9a25994d upstream.
The previous commit (0adbfd46) fixed a memory leak but also freed a
block in the success case, causing a stale pointer to
We want to centralize the isolation management from the housekeeping
subsystem. Therefore we need to handle the nohz_full= parameter from
there.
Since nohz_full= so far has involved unbound timers, watchdog, RCU
and tilegx NAPI isolation, we keep that default behaviour.
nohz_full= is deemed to be
Signed-off-by: Frederic Weisbecker
Cc: Chris Metcalf
Cc: Rik van Riel
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Mike Galbraith
Cc: Ingo Molnar
Cc: Christoph Lameter
Cc: Paul E. McKenney
Cc: Wanpeng Li
Cc: Luiz Capitulino
---
Documentation/admin-guide/kernel-parameters.txt | 35
Before we implement isolcpus under housekeeping, we need the isolation
features to be more finegrained. For example some people want nohz_full
without the full scheduler isolation, others want full scheduler
isolation without nohz_full.
So let's cut all these isolation features piecewise, at the r
housekeeping_any_cpu() doesn't handle correctly the case where
CONFIG_NO_HZ_FULL=y and no CPU is in nohz_full mode. So far no caller
needs this but let's prepare to avoid any future surprise.
Signed-off-by: Frederic Weisbecker
Cc: Chris Metcalf
Cc: Rik van Riel
Cc: Peter Zijlstra
Cc: Thomas Gl
To keep a proper housekeeping namespace.
Signed-off-by: Frederic Weisbecker
Cc: Chris Metcalf
Cc: Rik van Riel
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Mike Galbraith
Cc: Ingo Molnar
Cc: Christoph Lameter
Cc: Paul E. McKenney
Cc: Wanpeng Li
Cc: Luiz Capitulino
---
include/linux/house
While trying to disable the watchog on nohz_full CPUs, the watchdog
implements an ad-hoc version of housekeeping_cpumask(). Lets replace
those re-invented lines.
Signed-off-by: Frederic Weisbecker
Cc: Chris Metcalf
Cc: Rik van Riel
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Mike Galbraith
Cc
Hi Ingo,
On 10/24/17 at 03:29pm, Ingo Molnar wrote:
> > diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> > index 048fbe8fc274..f5aa0d7c4cd1 100644
> > --- a/arch/x86/mm/init_64.c
> > +++ b/arch/x86/mm/init_64.c
> > @@ -1426,10 +1426,10 @@ int __meminit vmemmap_populate(unsigned long st
On Tue, Oct 24, 2017 at 03:04:04AM -0500, Kim Phillips wrote:
> Introduce new tools/perf/arch/*/util/evsel.c:perf_evsel__suppl_strerror()
> so each arch can start to customize usability for its h/w PMU drivers.
>
> Signed-off-by: Kim Phillips
> ---
> tools/perf/arch/x86/util/Build | 1 +
> to
On Tue, Oct 24, 2017 at 03:04:15AM -0500, Kim Phillips wrote:
> Use the Arm CCN driver as an example of how to try to improve
> upon its existing dmesg error output, and duplicate error string
> generation logic in the perf tool.
[...]
> Comments? Is this really that much better than the existin
On Tue, Oct 24, 2017 at 03:04:08AM -0500, Kim Phillips wrote:
> Call perf_evsel__open_strerror() to potentially expand upon why the
> event was "not supported by the kernel." See the enhanced '-v' example
> output messages in the next patch.
Nit: it would be better if the commit message was self-
Housekeeping code still depends on nohz_full static key. Since we want
to decouple housekeeping from nohz, let's create a housekeeping own static
key. It's mostly relevant for calls to is_housekeeping_cpu() from the
scheduler.
Signed-off-by: Frederic Weisbecker
Cc: Chris Metcalf
Cc: Rik van Riel
On Tue, Oct 24, 2017 at 03:06:50PM +0200, Frederic Weisbecker wrote:
> The housekeeping code is currently tied to the nohz code. As we are
> planning to make housekeeping independant from it, start with moving
> the relevant code to its own file.
>
> Signed-off-by: Frederic Weisbecker
> Cc: Chris
The housekeeping code is currently tied to the nohz code. As we are
planning to make housekeeping independant from it, start with moving
the relevant code to its own file.
Signed-off-by: Frederic Weisbecker
Cc: Chris Metcalf
Cc: Rik van Riel
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Mike Gal
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Larry Finger
commit b8b8b16352cd90c6083033fd4487f04fae935c18 upstream.
In commit 40b368af4b75 ("rtlwifi: Fix alignment issues"), the read
of REG_DBI_READ was changed from 16 to 8 bits. For unkn
Nobody needs to access this detail. housekeeping_cpumask() already
takes care about it.
Signed-off-by: Frederic Weisbecker
Cc: Chris Metcalf
Cc: Rik van Riel
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Mike Galbraith
Cc: Ingo Molnar
Cc: Christoph Lameter
Cc: Paul E. McKenney
Cc: Wanpeng Li
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Darrick J. Wong
commit 3af423b03435c81036fa710623d3ae92fbe346a3 upstream.
When we perform an finsert/fcollapse operation, cancel all the CoW
extents for the affected file offset range so that t
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Sesterhenn
commit 68a1fdbbf8bd3378325e45c19e167a165f9ffc3a upstream.
The ASN.1 parser does not necessarily set the sinfo field,
this patch prevents a NULL pointer dereference on broken
inp
(No significant change since v4, only a rebase against -rc6)
Ingo,
Please pull the core/isolation-v5 branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
core/isolation-v5
HEAD: 64b71f4e9bffef1d7c9ffd2fae9b688be6da95b5
Summary of change
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit 60ff5b2f547af3828aebafd54daded44cfb0807a upstream.
Currently, when passed a key that already exists, add_key() will call the
key's ->update() method if such exists. But th
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dexuan Cui
[Fixes upstream in a much larger set of patches that are not worth backporting
to 4.9 - gregkh]
When the space available before start of reading (cached_write_sz)
is the same as the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Brian Foster
commit f35c5e10c6ed6ba52a8dd8573924a80b6a02f03f upstream.
xfs_attr3_root_inactive() walks the attr fork tree to invalidate the
associated blocks. xfs_attr3_node_inactive() recursiv
On Sun, Oct 22, 2017 at 10:09:16PM -0700, Dave Hansen wrote:
> On 10/22/2017 07:55 PM, Jarkko Sakkinen wrote:
> > On Fri, Oct 20, 2017 at 07:32:42AM -0700, Dave Hansen wrote:
> >> I've always been curious, and the changelog and thread are curiously
> >> oblique on this topic: what the heck does thi
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit e12199f85d0ad1b04ce6c425ad93cd847fe930bb upstream.
If we got two AIO writes into a COW area the second one might not have any
COW extents left to convert. Handle that
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Carlos Maiolino
commit 842f6e9f786226c58fcbd5ef80eadca72fdfe652 upstream.
My previous patch: d3a304b6292168b83b45d624784f973fdc1ca674 check for
XFS_LI_FAILED flag xfs_iflush done, so the failed
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: John David Anglin
commit 374b3bf8e8b519f61eb9775888074c6e46b3bf0c upstream.
As discussed on the debian-hppa list, double-wordcompare and exchange
operations fail on 32-bit kernels. Looking at
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eryu Guan
commit ee70daaba82d70766d0723b743d9fdeb3b06102a upstream.
Since commit d531d91d6990 ("xfs: always use unwritten extents for
direct I/O writes"), we start allocating unwritten extents
On 20 October 2017 at 23:11, Bjorn Helgaas wrote:
>
> On Thu, Oct 12, 2017 at 10:11:08AM +0530, Pankaj Dubey wrote:
> > IATU unroll feature can be enabled in EP mode as well, so we need to
> > have this check in pcie-designware-ep.c, so instead of making this
> > function as static in pcie-desigwa
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 1ac7db6db1eeff901bfd6bbcd502b4634fa4 upstream.
If the connect status change is set during reset signaling, but
the status remains connected just retry port reset.
This
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 31dc3f819bac28a0990b36510197560258ab7421 upstream.
Add device-id entry for (Honeywell) Metrologic MS7820 bar code scanner.
The device has two interfaces (in this mode?); a
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: David Kozub
commit eb39a7c0355393c5a8d930f342ad7a6231b552c4 upstream.
The interrupt handler mfgpt_tick() is not robust versus spurious interrupts
which happen before the clock event device is r
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 098a0a62c1554f5a3813ef1b8539563214ada8f6 upstream.
The loop in snd_hdac_bus_parse_capabilities() may go to nirvana when
it hits an invalid register value read:
BUG: unable
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Pontus Andersson
commit c6ebcedbab7ca78984959386012a17b21183e1a3 upstream.
Commit b6c159a9cb69 ("i2c: ismt: Don't duplicate the receive length for
block reads") broke I2C block reads. It aimed
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 6bf88a343db2b3c160edf9b82a74966b31cc80bd upstream.
While converting the error messages to the standard macros in the
commit 4e76a8833fac ("ALSA: hda - Replace with standard
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 8009d506a1dd00cf436b0c4cca0dcec130580a21 upstream.
The 'use' locking macros are no-ops if neither SMP or SND_DEBUG is
enabled. This might once have been OK in non-preempti
On 10/20/2017 05:34 PM, Greg Kroah-Hartman wrote:
@@ -938,6 +940,7 @@ int device_add_properties(struct device *dev,
p->fwnode.ops = &pset_fwnode_ops;
set_secondary_fwnode(dev, &p->fwnode);
+ p->dev = dev;
Don't you also need to increment the reference counter here? Or how
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ilia Mirkin
commit 194d68dd051c2dd5ac2b522ae16100e774e8d869 upstream.
G92's seem to require some additional bit of initialization before the
BSP engine can work. It feels like clocks are not se
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit ea7d0d69426cab6747ed311c53f4142eb48b9454 upstream.
Many USB 3.1 capable hosts never updated the Serial Bus Release Number
(SBRN) register to USB 3.1 from USB 3.0
xhci driv
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jonathan Liu
commit 6ed05c68cbcae42cd52b8e53b66952bfa9c002ce upstream.
This fixes a kernel oops when unloading the driver due to usb_put_phy
being called after usb_phy_generic_unregister when t
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit 845d584f41eac3475c21e4a7d5e88d0f6e410cf7 upstream.
Taking the uurb->buffer_length userspace passes in as a maximum for the
actual urbs transfer_buffer_length causes 2 serio
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Lars-Peter Clausen
commit be94a6f6d488b4767662e8949dc62361bd1d6311 upstream.
Add missing break in iio_simple_dummy_write_event_config() for the voltage
threshold event enable attribute. Without
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 8009d506a1dd00cf436b0c4cca0dcec130580a21 upstream.
The 'use' locking macros are no-ops if neither SMP or SND_DEBUG is
enabled. This might once have been OK in non-preempti
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Wolfgang Grandegger
commit 97819f943063b622eca44d3644067c190dc75039 upstream.
If sending messages with no cable connected, it quickly happens that
there is no more TX context available. Then "g
On Mon, Oct 23, 2017 at 07:02:18PM +0530, Nayna Jain wrote:
>
>
> On 10/20/2017 02:26 PM, Jarkko Sakkinen wrote:
> > On Thu, Oct 19, 2017 at 05:00:29PM +, alexander.stef...@infineon.com
> > wrote:
> > > > On Tue, Oct 17, 2017 at 04:32:29PM -0400, Nayna Jain wrote:
> > > > > The function wait
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 1c0edc3633b56000e18d82fc241e3995ca18a69e upstream.
Andrey used the syzkaller fuzzer to find an out-of-bounds memory
access in usb_get_bos_descriptor(). The code wasn't checki
Em Tue, Oct 24, 2017 at 03:45:34PM +0800, Cheng Jian escreveu:
> When running perf sched record, there is a bug.
>
> It's system_wide when we specify a command line.
Humm, isn't this because if you trace just a workload you will miss the
sched-in events?
Perhaps with PERF_RECORD_SWITCH we can so
* Jiri Olsa wrote:
> I recently made some changes on threaded record, which are based
> on Namhyungs time* API, which is needed to read/sort the data afterwards
>
> but I wasn't able to get any substantial and constant reduce of LOST events
> and then I got sidetracked and did not finish, but i
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 1ac7db6db1eeff901bfd6bbcd502b4634fa4 upstream.
If the connect status change is set during reset signaling, but
the status remains connected just retry port reset.
Thi
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: John David Anglin
commit f4125cfdb3008363137f744c101e5d76ead760ba upstream.
There is no need to trash sr2 and sr3 in the Light-weight syscall (LWS). sr2
already points to kernel space (it's z
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 1c0edc3633b56000e18d82fc241e3995ca18a69e upstream.
Andrey used the syzkaller fuzzer to find an out-of-bounds memory
access in usb_get_bos_descriptor(). The code wasn't check
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit 60ff5b2f547af3828aebafd54daded44cfb0807a upstream.
Currently, when passed a key that already exists, add_key() will call the
key's ->update() method if such exists. But t
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit c503dd38f850be28867ef7a42d9abe5ade81a9bd upstream.
With KASAN and a couple of other patches applied, this driver is one
of the few remaining ones that actually use more th
On Tue, Oct 24, 2017 at 11:34:13AM +0200, Ingo Molnar wrote:
>
> * Johannes Berg wrote:
>
> > On Mon, 2017-10-23 at 21:07 +, Paul E. McKenney wrote:
> > > From: Mark Rutland
> > >
> > > For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
> > > preference to ACCESS_ONCE(), an
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 6bf88a343db2b3c160edf9b82a74966b31cc80bd upstream.
While converting the error messages to the standard macros in the
commit 4e76a8833fac ("ALSA: hda - Replace with standard
There are a few DT files that make use of sst25vf016b in their
compatible strings, and the driver supports this chip already.
This patch improves the documentation and therefore the result
of ./scripts/checkpatch.pl.
Signed-off-by: Fabrizio Castro
Signed-off-by: Chris Paterson
Acked-by: Rob Herr
On 10/23/2017 07:25 PM, kemi wrote:
>
>
> On 2017年10月24日 09:21, Andi Kleen wrote:
>> kemi writes:
>>>
>>> I'll see if I can find some
time to implement the above in a nice way.
>>>
>>> Agree. Maybe something like test_and_set_bit() would be more suitable.
>>
>> test_and_set_bit is a very di
On 10/23/2017 07:03 PM, Stefano Stabellini wrote:
> On Tue, 17 Oct 2017, Boris Ostrovsky wrote:
>> On 10/06/2017 08:30 PM, Stefano Stabellini wrote:
>>> + /*
>>> +* Backend only supports 1 inflight accept request, will return
>>> +* errors for the others
>>> +*/
>>> + if (test_and_s
Hi Kees,
On Tue, Oct 24, 2017 at 03:13:31AM -0700, Kees Cook wrote:
> In preparation for unconditionally passing the struct timer_list pointer to
> all timer callbacks, switch to using the new timer_setup() and from_timer()
> to pass the timer pointer explicitly.
> Also adds missing call to destr
On Mon, Oct 23, 2017 at 03:44:01PM +0200, Jarkko Sakkinen wrote:
> On Sun, Oct 22, 2017 at 01:30:46PM +0200, SF Markus Elfring wrote:
> > From: Markus Elfring
> > Date: Sun, 22 Oct 2017 13:15:16 +0200
> >
> > A return was performed with the same error code after two condition checks.
> > Thus use
On 10/24, Corentin Labbe wrote:
> On Tue, Oct 24, 2017 at 01:36:28AM -0700, Stephen Boyd wrote:
> > On 10/20, Maxime Ripard wrote:
> > > Hi Stephen, Mike,
> > >
> > > On Thu, Oct 19, 2017 at 09:09:48PM +0200, Corentin Labbe wrote:
> > > > This patch fix the following build warning:
> > > > drivers
Markus,
I normally keep quiet on threads like this. I half agree with you. Yes, perhaps
a reportError function would be a good idea, but it seems that what you are
suggesting is trading an inline subroutine call for a spaghetti-code vondition.
The goto is used only if you do not have any code
On Mon, Oct 23, 2017 at 03:51:09PM +0200, SF Markus Elfring wrote:
> >> @@ -315,6 +311,8 @@ static int tpm_tis_send_data(struct tpm_chip *chip,
> >> const u8 *buf, size_t len)
> >>
> >>return 0;
> >>
> >> +report_timeout:
> >> + rc = -ETIME;
> >> out_err:
> >>tpm_tis_ready(chip);
> >
Hi Jens,
I just noticed a testing leftover that made it in one of this window's
patches. Can you pick this up (and eventually squash it)?
Thanks,
Javier
Javier González (1):
lightnvm: pblk: remove testing leftover
drivers/lightnvm/pblk.h | 5 -
1 file changed, 5 deletions(-)
--
2.7.4
On Mon, Oct 23, 2017 at 03:57:30PM +0200, SF Markus Elfring wrote:
> >> @@ -108,11 +106,14 @@ static int vtpm_send(struct tpm_chip *chip, u8 *buf,
> >> size_t count)
> >>if (wait_for_tpm_stat(chip, VTPM_STATUS_IDLE, duration,
> >>&priv->read_queue, true) < 0) {
> >>
fixes: 8bd400204bd5 ("lightnvm: pblk: cleanup unused and static functions")
Signed-off-by: Javier González
---
drivers/lightnvm/pblk.h | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/lightnvm/pblk.h b/drivers/lightnvm/pblk.h
index 6b64288de6f7..90961033a79f 100644
--- a/drivers/li
From: Markus Elfring
Date: Tue, 24 Oct 2017 15:54:32 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an unnecessary goto statement in intel_dp_sink_crc()
Use common error handling code in intel_dp_sink_crc_stop()
drivers/gpu
From: Markus Elfring
Date: Tue, 24 Oct 2017 15:15:20 +0200
A jump was specified for a location which was directly behind.
Thus remove such an unnecessary goto statement.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/i915/intel_dp.c
On 10/24/2017 07:56 AM, Javier González wrote:
> fixes: 8bd400204bd5 ("lightnvm: pblk: cleanup unused and static functions")
> Signed-off-by: Javier González
Added, thanks.
--
Jens Axboe
From: Markus Elfring
Date: Tue, 24 Oct 2017 15:40:47 +0200
Adjust jump targets so that a specific error code assignment
will be in the implementation only at the end of this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/i
On 10/23/2017 07:06 PM, Stefano Stabellini wrote:
> On Tue, 17 Oct 2017, Boris Ostrovsky wrote:
>>> +static unsigned int pvcalls_front_poll_passive(struct file *file,
>>> + struct pvcalls_bedata *bedata,
>>> + struct
On 2017/10/24 20:46, Jaegeuk Kim wrote:
> On 10/24, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2017/10/4 9:08, Chao Yu wrote:
>>> From: Chao Yu
>>>
>>> In ->umount, once we drop remained discard entries, we should not
>>> set CP_TRIMMED_FLAG with another checkpoint.
>>>
>>> Signed-off-by: Chao Yu
>>>
On Mon, Oct 23, 2017 at 10:07:31AM -0400, Stefan Berger wrote:
> I think every kernel internal TPM driver API should be called with the
> tpm_chip as a parameter. This is in foresight of namespacing of IMA where we
> want to provide the flexibility of passing a dedicated vTPM to each
> namespace an
Hi Palmer,
Some late comments on this which you might want to address as you get the
chance.
On Tue, Sep 26, 2017 at 06:56:31PM -0700, Palmer Dabbelt wrote:
> This contains all the code that directly interfaces with the RISC-V
> memory model. While this code corforms to the current RISC-V ISA
>
(I just noticed that I missed this patch, sorry)
On 10/06/2017 08:30 PM, Stefano Stabellini wrote:
> Send PVCALLS_RELEASE to the backend and wait for a reply. Take both
> in_mutex and out_mutex to avoid concurrent accesses. Then, free the
> socket.
>
> For passive sockets, check whether we have al
The number of unsignaled work-requests posted to the IB send queue is
tracked by a counter in the rds_ib_connection struct. When it reaches
zero, or the caller explicitly asks for it, the send-signaled bit is
set in send_flags and the counter is reset. This is performed by the
rds_ib_set_wr_signal_
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Dmitry Torokhov
Cc: Rakesh Iyer
Cc: Laxman Dewangan
Cc: Thierry Reding
Cc: Jonathan Hunter
Cc: Guen
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Signed-off-by: Kees Cook
---
drivers/input/serio/hil_
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Michael Hennerich
Cc: Dmitry Torokhov
Cc: Ferruh Yigit
Cc: Wan ZongShun
Cc: Guenter Roeck
Cc: linux
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
Cc: Dmitry Torokhov
Cc: Al Viro
Cc: Helge Deller
Cc: linux-in...@vger.kernel.org
Signed-off-by: Kees Cook
From: Gustavo A. R. Silva
> Sent: 24 October 2017 04:46
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Addresses-Coverity-ID: 145713
> Signed-off-by: Gustavo A. R. Silva
> ---
> drivers/usb/gadget/udc/goku_udc.c | 14 +
Perf top is often crashing at very random locations on powerpc.
After investigating, I found the crash only happens when sample
is of zero length symbol. Powerpc kernel has many such symbols
which does not contain length details in vmlinux binary and thus
start and end addresses of such symbols are
401 - 500 of 1177 matches
Mail list logo
