Sine the cpu/hotplug refactor is done, the hotplug
callbacks are called properly. So the workaround is
useless.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 5c99beb8577d..528321bc4
On Mon, Sep 25, 2017 at 02:58:25PM +0200, Michal Hocko wrote:
> On Thu 21-09-17 00:40:34, Seth Forshee wrote:
> > On Wed, Sep 20, 2017 at 11:29:31AM +0200, Michal Hocko wrote:
> > > Hi,
> > > I am currently at a conference so I will most probably get to this next
> > > week but I will try to ASAP.
On Thu, Nov 30, 2017 at 10:40:14PM +0100, Nguyen Phan Quang Minh wrote:
> Fix checkpatch warning and add result holder variable to reduce overhead
> since the macro is called on functions.
>
> Signed-off-by: Nguyen Phan Quang Minh
> ---
> Since SET_CHECKED has a return statement, I'm very tempted
On Fri, Dec 01, 2017 at 02:39:42PM +0100, Philippe Ombredanne wrote:
> On Fri, Dec 1, 2017 at 1:49 PM, Mark Brown wrote:
> >> or at least this with the id on the first and the // comment style
> >> > +// SPDX-License-Identifier: GPL-2.0
I snipped a bit of context here, the full example was actu
Also it's not a style issue, it's a bug. We double call the failing
function on error.
regards,
dan carpenter
From: Rafael J. Wysocki
There is a variable name mismatch in acpi_ut_strtoul_multiply64()
between the ACPICA code in the kernel and the corresponding upstream
code which may be problematic if changes to this particular piece of
code are made upstream and ported to Linux, so rename the variable
in
On Fri, Dec 01, 2017 at 10:27:57AM +, Lorenzo Pieralisi wrote:
> On Thu, Nov 30, 2017 at 02:15:05PM -0600, Bjorn Helgaas wrote:
> > From: Bjorn Helgaas
> >
> > On arm, PCI_REASSIGN_ALL_RSRC is used only in pcibios_assign_all_busses(),
> > which helps decide whether to reconfigure bridge bus n
On Friday, December 1, 2017 3:18:01 PM CET Lukas Wunner wrote:
> On Fri, Dec 01, 2017 at 02:58:34PM +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Prevent rpm_get_suppliers() from returning an error code if runtime
> > PM is disabled for one or more of the supplier devices it
Bom dia!
On Fri, Dec 01, 2017 at 11:59:33AM -0200, Mauro Carvalho Chehab wrote:
> Em Fri, 1 Dec 2017 15:52:55 +0200
> Sakari Ailus escreveu:
>
> > Hi Mauro,
> >
> > On Fri, Dec 01, 2017 at 11:47:10AM -0200, Mauro Carvalho Chehab wrote:
> > > diff --git a/drivers/media/usb/au0828/au0828-input.c
Hi Stephen, Lucas,
On Thu, 2017-11-30 at 10:53 +1100, Stephen Rothwell wrote:
> Hi Lucas,
>
> On Tue, 28 Nov 2017 11:44:46 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the etnaviv tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/gpu/drm/tve20
On Fri, Dec 1, 2017 at 3:18 PM, Lukas Wunner wrote:
> On Fri, Dec 01, 2017 at 02:58:34PM +0100, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> Prevent rpm_get_suppliers() from returning an error code if runtime
>> PM is disabled for one or more of the supplier devices it wants to
>> ru
On 2017-12-01 14:18:28 [+], Mark Rutland wrote:
> [Adding Ard, who wrote the NEON crypto code]
>
> On Fri, Dec 01, 2017 at 02:45:06PM +0100, Sebastian Andrzej Siewior wrote:
> > +arm folks, to let you know
> >
> > On 2017-12-01 11:43:32 [+0100], To linux-rt-us...@vger.kernel.org wrote:
> > >
On Fri, Dec 01, 2017 at 03:07:44PM +0800, Jason Wang wrote:
>
>
> On 2017年12月01日 13:54, w...@redhat.com wrote:
> > From: Wei Xu
> >
> > tun_recvmsg() supports accepting skb by msg_control after
> > commit ac77cfd4258f ("tun: support receiving skb through msg_control"),
> > the skb if presented
On Fri, Dec 01, 2017 at 03:11:05PM +0800, Jason Wang wrote:
>
>
> On 2017年12月01日 13:54, w...@redhat.com wrote:
> > From: Wei Xu
> >
> > Matthew found a roughly 40% tcp throughput regression with commit
> > c67df11f(vhost_net: try batch dequing from skb array) as discussed
> > in the following t
On Fri, Dec 01, 2017 at 11:31:08PM +1100, Michael Ellerman wrote:
> "Michael S. Tsirkin" writes:
>
> > fill_balloon doing memory allocations under balloon_lock
> > can cause a deadlock when leak_balloon is called from
> > virtballoon_oom_notify and tries to take same lock.
> >
> > To fix, split p
4.14.3 is still affected.
I am still bisecting between 4.13 and 4.14, 5 steps to go. Defining a
kernel as "good" if it survived 24 hours on the hosts.
Greetings
Marc
On Wed, Nov 22, 2017 at 04:04:42PM +0100, 王金浦 wrote:
> From: 王金浦
> Subject: Re: VMs freezing when host is running 4.14
> To: Mar
Hi,
Am 01.12.2017 um 08:49 schrieb H. Nikolaus Schaller:
> Introduce vendor prefix for Wi2Wi, Inc. for W2SG00x4 GPS modules
> and W2CBW003 Bluetooth/WiFi combo (CSR/Marvell).
If there's more iterations, maybe you could clarify what the company
does overall (just these 2?) vs. what specifically yo
Em Fri, Dec 01, 2017 at 06:57:34PM +0800, Jin Yao escreveu:
> Perf already has a function thread_map__new_by_uid() which can
> enumerate all threads from /proc by uid.
>
> This patch creates a static function enumerate_threads() which
> reuses the common code in thread_map__new_by_uid() to enumera
On Fri, Dec 1, 2017 at 1:35 PM, Ming Lei wrote:
> Basically all IO hang happen inside get_request(), and seems this issue
> isn't related with recent change in V4.15, could you run V4.14 to see if
> there is such issue?
I tried several times and I could not reproduce the problem on linus's v4.14.
On Fri, Dec 01, 2017 at 05:10:35AM -0500, w...@redhat.com wrote:
> From: Wei Xu
>
> Matthew found a roughly 40% tcp throughput regression with commit
> c67df11f(vhost_net: try batch dequing from skb array) as discussed
> in the following thread:
> https://www.mail-archive.com/netdev@vger.kernel.o
On Fri, Dec 01, 2017 at 05:10:37AM -0500, w...@redhat.com wrote:
> From: Wei Xu
>
> tun_recvmsg() supports accepting skb by msg_control after
> commit ac77cfd4258f ("tun: support receiving skb through msg_control"),
> the skb if presented should be freed no matter how far it can go
> along, other
On Fri, Dec 01, 2017 at 05:10:36AM -0500, w...@redhat.com wrote:
> From: Wei Xu
>
> Matthew found a roughly 40% tcp throughput regression with commit
> c67df11f(vhost_net: try batch dequing from skb array) as discussed
> in the following thread:
> https://www.mail-archive.com/netdev@vger.kernel.o
On Fri, Dec 01, 2017 at 05:10:38AM -0500, w...@redhat.com wrote:
> From: Wei Xu
>
> tap_recvmsg() supports accepting skb by msg_control after
> commit 3b4ba04acca8 ("tap: support receiving skb from msg_control"),
> the skb if presented should be freed within the function, otherwise
> it would be
hello Bjorn,
Sorry for these late remarks/questions
On 11/30/2017 02:16 AM, Bjorn Andersson wrote:
> remoteproc instances can be stopped either by invoking shutdown or by an
> attempt to recover from a crash. For some subdev types it's expected to
> clean up gracefully during a shutdown, but are
On 12/01/2017 09:47 AM, Michael S. Tsirkin wrote:
> On Fri, Dec 01, 2017 at 05:10:35AM -0500, w...@redhat.com wrote:
>> From: Wei Xu
>>
>> Matthew found a roughly 40% tcp throughput regression with commit
>> c67df11f(vhost_net: try batch dequing from skb array) as discussed
>> in the following thr
On 12/01/2017 12:50 AM, Song Liu wrote:
> Changes PATCH v2 to PATCH v3:
> Remove fixed type PERF_TYPE_KPROBE and PERF_TYPE_UPROBE, use dynamic
> type instead.
> Update userspace (samples/bpf, bcc) to look up type from sysfs.
> Change License info in test_many_kprobe_user.c as Philippe Ombre
On 12/01/2017 07:30 AM, Mark Brown wrote:
> On Wed, Nov 29, 2017 at 03:32:51PM -0600, Andrew F. Davis wrote:
>> Leaving microphone bias off is a valid setting and even used in the DT
>> binding document example. Add this setting here and document the same.
>
>> - ai31xx-micbias-vg - MicBias Volta
On Fri, Dec 01, 2017 at 09:54:02AM -0500, Matthew Rosato wrote:
> On 12/01/2017 09:47 AM, Michael S. Tsirkin wrote:
> > On Fri, Dec 01, 2017 at 05:10:35AM -0500, w...@redhat.com wrote:
> >> From: Wei Xu
> >>
> >> Matthew found a roughly 40% tcp throughput regression with commit
> >> c67df11f(vhost
On 12/01/2017 07:36 AM, Mark Brown wrote:
> On Wed, Nov 29, 2017 at 03:32:55PM -0600, Andrew F. Davis wrote:
>> A regulator being forcefully disabled is a catastrophic event that
>> should never happen to most devices, especially not sound CODECs.
>
> That's not what the disable notification handl
Em Fri, Dec 01, 2017 at 11:44:25AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Dec 01, 2017 at 06:57:34PM +0800, Jin Yao escreveu:
> > Perf already has a function thread_map__new_by_uid() which can
> > enumerate all threads from /proc by uid.
> >
> > This patch creates a static function en
l
> On 1 Dec 2017, at 14:36, Sebastian Andrzej Siewior
> wrote:
>
>> On 2017-12-01 14:18:28 [+], Mark Rutland wrote:
>> [Adding Ard, who wrote the NEON crypto code]
>>
>>> On Fri, Dec 01, 2017 at 02:45:06PM +0100, Sebastian Andrzej Siewior wrote:
>>> +arm folks, to let you know
>>>
O
On 12/01/2017 07:37 AM, Mark Brown wrote:
> On Wed, Nov 29, 2017 at 03:32:56PM -0600, Andrew F. Davis wrote:
>
>> +gpiod_set_value(aic31xx->gpio_reset, 1);
>> +ndelay(10); /* At least 10ns */
>> +gpiod_set_value(aic31xx->gpio_reset, 0);
>
> _cansleep(), this is
This change fixes the calculation of B-frames and GOP size by
adopt v4l2 controls with the firmware interface expectations.
Signed-off-by: Stanimir Varbanov
---
Drop usage of do_div to avoid compiler warnings on 32bit systems.
drivers/media/platform/qcom/venus/venc.c | 15 ---
drivers
On Friday, December 1, 2017 9:02 PM, Tetsuo Handa wrote:
> Wei Wang wrote:
> > On 11/30/2017 06:34 PM, Tetsuo Handa wrote:
> > > Wei Wang wrote:
> > >> + * @start: the start of the bit range, inclusive
> > >> + * @end: the end of the bit range, inclusive
> > >> + *
> > >> + * This function is used
On Thu, Nov 23, 2017 at 03:02:04PM +0100, Marc-André Lureau wrote:
> Modify fw_cfg_read_blob() to use DMA if the device supports it.
> Return errors, because the operation may fail.
>
> The DMA operation is expected to run synchronously with today qemu,
> but the specification states that it may b
On 30/11/2017 19:05, Radim Krčmář wrote:
> Does roughly what kvm_mmu_notifier_invalidate_page did before.
>
> I am not certain why this would be needed. It might mean that we have
> another bug with start/end or just that I missed something.
I don't think this is needed, because we don't have sh
On 12/01/17 at 02:52pm, Juerg Haefliger wrote:
> Loading a kexec kernel using today's linux-tip master with KAISER=y
> triggers the following warning:
I also noticed this when trigger a crash to jump to kdump kernel, and
kdump kernel failed to bootup. I am trying to fix it on tip/WIP.x86/mm.
Maybe
On 12/01/2017 10:55 AM, Yisheng Xie wrote:
> As in manpage of migrate_pages, the errno should be set to EINVAL when
> none of the node IDs specified by new_nodes are on-line and allowed by the
> process's current cpuset context, or none of the specified nodes contain
> memory. However, when test b
Thank you, it fixes the issue on the multi-address eeprom that I have access to.
Tested-by: Sven Van Asbroeck on a 24AA16/24LC16B
One very minor remark:
+ struct device *dev = &at24->client[0]->dev;
It is sufficiently clear to others (and us a few months down the line)
why we are
using o
On Tue, Nov 28, 2017 at 06:49:20PM -0500, Theodore Ts'o wrote:
> On Tue, Nov 28, 2017 at 03:29:01PM -0800, Kees Cook wrote:
> > > So in these two cases, if the kernel was built w/o modules, and HDLC
> > > and DCCP was built-in, you'd be screwed, then?
> >
> > Sure, but that's not the common situat
Hi Florian,
Florian Fainelli writes:
> +#if IS_ENABLED(CONFIG_NET_DSA_LEGACY)
> /* Legacy driver registration */
> void register_switch_driver(struct dsa_switch_driver *type);
> void unregister_switch_driver(struct dsa_switch_driver *type);
> struct mii_bus *dsa_host_dev_to_mii_bus(struct de
On 30/11/2017 19:05, Radim Krčmář wrote:
> Implementation of the unpinned APIC page didn't update the VMCS address
> cache when invalidation was done through range mmu notifiers.
> This became a problem when the page notifier was removed.
>
> Re-introduce the arch-specific helper and call it from
On Fri, Dec 01, 2017 at 11:18:51PM +0800, Baoquan He wrote:
> On 12/01/17 at 02:52pm, Juerg Haefliger wrote:
> > Loading a kexec kernel using today's linux-tip master with KAISER=y
> > triggers the following warning:
>
> I also noticed this when trigger a crash to jump to kdump kernel, and
> kdump
Hi!
> > MAP_FIXED_UNIQUE
> > MAP_FIXED_ONCE
> > MAP_FIXED_FRESH
>
> Well, I can open a poll for the best name, but none of those you are
> proposing sound much better to me. Yeah, naming sucks...
Given that MAP_FIXED replaces the previous mapping MAP_FIXED_NOREPLACE
would probably be a best fit.
Hi,
On Mon, Nov 20, 2017 at 12:58:27PM -0800, Jesse Chan wrote:
> This change resolves a new compile-time warning
> when built as a loadable module:
>
> WARNING: modpost: missing MODULE_LICENSE() in drivers/power/reset/zx-reboot.o
> see include/linux/module.h for more information
>
> This adds t
Hi,
On Tue, Nov 21, 2017 at 01:27:12PM +0900, raito...@gmail.com wrote:
> From: Ryosuke Saito
>
> Should be discharging_max_duration_ms, not charging_max_duration_ms.
>
> Signed-off-by: Ryosuke Saito
> ---
Thanks, queued.
-- Sebastian
> drivers/power/supply/charger-manager.c | 2 +-
> 1 fi
The irq_balancing_disabled and irq_is_percpu{,_devid} functions are
clearly intended to return bool like the functions in
kernel/irq/settings.h, but actually return an int containing a masked
value of desc->status_use_accessors. This can lead to subtle breakage
if, for example, the return value is
Hi,
On Wed, Nov 22, 2017 at 09:27:31PM +0100, Christophe JAILLET wrote:
> 'ret' is know to be 0 at this point, because it has not been updated by the
> the previous call to 'abx500_mask_and_set_register_interruptible()'.
>
> Fix it by updating 'ret' before checking if an error occurred.
>
> Fixe
Hi,
On Wed, Nov 22, 2017 at 09:31:20PM +0100, Christophe JAILLET wrote:
> If an error occurs when we enable the backup battery charging, we should
> go through the error handling path directly.
>
> Before commit db43e6c473b5 ("ab8500-bm: Add usb power path support") this
> was the case, but this
Hi,
On Fri, Nov 24, 2017 at 10:31:40PM +0530, Arvind Yadav wrote:
> The platform_get_irq_byname() function returns -1 if an error occurs.
> zero or positive number on success. platform_get_irq_byname() error
> checking for zero is not correct.
>
> Signed-off-by: Arvind Yadav
> ---
Thanks, queue
On 12/01/2017 05:52 AM, Juerg Haefliger wrote:
> Loading a kexec kernel using today's linux-tip master with KAISER=y
> triggers the following warning:
>
> [ 18.054017] [ cut here ]
> [ 18.054024] WARNING: CPU: 0 PID: 1183 at
> ./arch/x86/include/asm/pgtable_64.h:258 nat
On Fri, 1 Dec 2017, Boqun Feng wrote:
> > > But in case of AMOs, which directly send the addition request to memory
> > > controller, so there wouldn't be any read part or even write part of the
> > > atomic_inc() executed by CPU. Would this be allowed then?
> >
> > Firstly, sending the addition
On 12/01/2017 07:39 AM, Mark Brown wrote:
> On Wed, Nov 29, 2017 at 03:32:57PM -0600, Andrew F. Davis wrote:
>
>> +static irqreturn_t aic31xx_irq(int irq, void *data)
>> +{
>> +struct aic31xx_priv *aic31xx = (struct aic31xx_priv *)data;
>
> There is no need to cast away from void, doing so ca
On Fri, Dec 01, 2017 at 02:46:39PM +, Ivan Kozik wrote:
> On Fri, Dec 1, 2017 at 1:35 PM, Ming Lei wrote:
> > Basically all IO hang happen inside get_request(), and seems this issue
> > isn't related with recent change in V4.15, could you run V4.14 to see if
> > there is such issue?
>
> I tri
On Fri, Dec 01, 2017 at 09:54:43AM +, Ard Biesheuvel wrote:
> On 1 December 2017 at 09:48, Greg Kroah-Hartman
> wrote:
> > On Thu, Nov 30, 2017 at 05:18:42PM +, Ard Biesheuvel wrote:
> >> On 30 November 2017 at 17:10, Greg Kroah-Hartman
> >> wrote:
> >> > On Thu, Nov 30, 2017 at 04:32:35P
Hi Sven,
On Fri, Dec 01, 2017 at 10:20:41AM -0500, Sven Van Asbroeck wrote:
> Thank you, it fixes the issue on the multi-address eeprom that I have access
> to.
>
> Tested-by: Sven Van Asbroeck on a 24AA16/24LC16B
>
> One very minor remark:
>
> + struct device *dev = &at24->client[0]->d
Hi Arnd,
On Mon, Nov 27, 2017 at 12:42:34PM +0100, Arnd Bergmann wrote:
> struct timespec should no longer be used because of the y2038
> overflow problem. This code does not suffer from the overflow,
> but it's trivial to change it to use timespec64 without changing
> the interface, so let's do t
On Fri, Dec 01, 2017 at 07:31:36AM -0800, Dave Hansen wrote:
> The only question is whether we want to preserve _some_ kind of warning
> there, or just axe it entirely.
Right, my fear would be if we keep it, then we'd have to go and
whitelist or somehow track those users which are an exception...
On Wed, Nov 29, 2017 at 09:55:23PM +0800, Wei Wang wrote:
> Add a new feature, VIRTIO_BALLOON_F_SG, which enables the transfer of
> balloon (i.e. inflated/deflated) pages using scatter-gather lists to the
> host. A scatter-gather list is described by a vring desc.
>
> The implementation of the pre
Hi everyone,
Here is a V4 series to add the driver of the touchscreen Cypress,
TrueTouch Generation 5.
Based on last master branch of "input" kernel's tree, last commit c1b433e04ef9.
This touchscreen is similar to Cypress generation 4 but the
registers are different.
This driver uses regmap as i
This is the basic driver for the Cypress TrueTouch Gen5 touchscreen
controllers. This driver supports only the I2C bus but it uses regmap
so SPI support could be added later.
The touchscreen can retrieve some defined zone that are handled as
buttons (according to the hardware). That is why it handl
Add the Cypress TrueTouch Generation 5 touchscreen device tree bindings
documentation. It can use I2C or SPI bus.
This touchscreen can handle some defined zone that are designed and
sent as button. To be able to customize the keycode sent, the
"linux,keycodes" property can be used.
Acked-by: Rob H
Hi,
On Thu, Nov 23, 2017 at 03:41:05PM +0100, Mike Looijmans wrote:
> The driver sets the fuel gauge to continuous monitoring on startup, for
> the models that support this. When the board shuts down, the chip remains
> in that mode, causing a few mA drain on the battery every 2 or 10 seconds.
>
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
This reverts commit "fs: jbd2: pull your plug when waiting for space".
This was a duct-tape fix which shouldn't be needed since commit
"locking/rt-mutex: fix
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
1. When trying to acquire an rtmutex, we first try to grab it without
queueing the waiter, and explicitly check for that initial attempt
in the !waiter path of __try_to
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
Mart reported a deadlock in -RT in the call path:
hci_send_monitor_ctrl_event() -> hci_send_to_channel()
because both functions acquire the same read lock
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
get_cpu_ptr() disabled preemption and returns the ->flush_queue object
of the current CPU. raw_cpu_ptr() does the same except that it not
disable preemption
On Wed, Nov 29, 2017 at 09:55:26PM +0800, Wei Wang wrote:
> The guest free pages should not be discarded by the live migration thread
> when page poisoning is enabled with PAGE_POISONING_NO_SANITY=n, because
> skipping the transfer of such poisoned free pages will trigger false
> positive when new
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
Mart reported a deadlock in -RT in the call path:
hci_send_monitor_ctrl_event() -> hci_send_to_channel()
because both functions acquire the same read lock
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
Since the futex rework, __rt_mutex_start_proxy_lock() does no longer
acquire the wait_lock so it must not drop it. Otherwise the lock is not
only unlocked tw
From: Yazen Ghannam
Scalable MCA systems have various types of banks. The bank's type can
determine how we handle errors from it. For example, if a bank represents
a UMC then we will need to convert its address from a normalized address
to a system physical address before handling the error.
Def
From: Yazen Ghannam
The MCA_STATUS[ErrorCodeExt] field is very bank type specific. We currently
check if the ErrorCodeExt value is 0x0 or 0x8 in mce_is_memory_error(), but
we don't check the bank. This means that we could flag non-memory errors as
memory errors.
We know that we want to flag DRAM
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
In v4.11 it is possible to disable the posix timers and so we must not
attempt to initialize the task_struct on RT with !POSIX_TIMERS.
This patch does so.
S
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
1. When trying to acquire an rtmutex, we first try to grab it without
queueing the waiter, and explicitly check for that initial attempt
in the !waiter path of __try_to
On 12/1/2017 4:13 AM, Sakari Ailus wrote:
> Most of the dev->of_node checks have been removed from property.c and
> replaced by calls to the firmware specific fwnode operations. What remains
> should probably be moved there, too (apart from dev_fwnode).
>
> How about adding a new op for this one t
Sorry for this spam. I tried to cancel, because I needed to check
something. But quilt decided to send anyway.
The patch set with a real subject is the real deal.
-- Steve
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
required for following networking patch which does recursive try-lock.
While at it, add the !RT version of it because it did not yet exist.
Cc: rt-sta...@vg
On Fri, 2017-12-01 at 11:10 +, David Howells wrote:
> Fix the MAINTAINERS record so that it's more obvious who the maintainer for
> AF_RXRPC is.
Thanks Davids...
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
The original patch changed betwen its posting and what finally went into
Rafael's tree so here is the delta.
Signed-off-by: Sebastian Andrzej Siewior
---
> > That's general misuse of /tmp. Things like "command > /tmp/file"
> > without having pre-created the file with O_EXCL e.g. by mktemp(1).
>
> I'm sorry, I've been using Unix for over 30 years.
> /tmp is a place that temporary files were created - nothing special.
> Traditionally it was emptie
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
get_cpu_ptr() disabled preemption and returns the ->flush_queue object
of the current CPU. raw_cpu_ptr() does the same except that it not
disable preemption
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Alex Shi
This patch replace a rwlock and raw notifier by atomic notifier which
protected by spin_lock and rcu.
The first to reason to have this replace is due to a 'scheduling while
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
We must not wake any process (and thus acquire the pi->lock) while
holding the hrtimer's base lock. This does not happen usually because
the hrtimer-callback
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
hrtimers, which were deferred to the softirq context, and expire between
softirq shutdown and hrtimer migration are dangling around. If the CPU
goes back up
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
kernel/hrtimer: don't wakeup a process while holding the hrtimer base lock
missed a path, namely hrtimers_dead_cpu() -> migrate_hrtimer_list(). Defer
raising softirq u
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
Lockdep may complain about an unsafe locking scenario:
| CPU0CPU1
|
| lock((tcp_sk_lock).lock);
|
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (VMware)"
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index fdb0f880c7e9..c12fc9d17724 1
[ Sorry for the duplicate, I tried to cancel sending, but quilt decided
to send anyway :-p ]
Dear RT Folks,
This is the RT stable review cycle of patch 4.9.65-rt57-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org an
On Fri, Dec 01, 2017 at 09:01:19AM -0600, Andrew F. Davis wrote:
> Looking into the call sites, at least in this case the only time this
> notification will be called, outside the normal enable/disable paths
> (which do the same thing here: turn on regmap cache only mode and mark
> it dirty), will
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (VMware)"
The commit "memcontrol: Prevent scheduling while atomic in cgroup code"
fixed this issue:
refill_stock()
get_cpu_var()
drain_stoc
On Fri, Dec 01, 2017 at 09:04:41AM -0600, Andrew F. Davis wrote:
> On 12/01/2017 07:37 AM, Mark Brown wrote:
> > On Wed, Nov 29, 2017 at 03:32:56PM -0600, Andrew F. Davis wrote:
> >> + } else {
> >> + ret = regmap_write(aic31xx->regmap, AIC31XX_RESET, 1);
> >> + if (ret < 0)
> >
On Fri, Dec 01, 2017 at 01:17:34PM +0530, Sagar Arun Kamble wrote:
> There is no real need for the users of timecounters to define cyclecounter
> and timecounter variables separately. Since timecounter will always be
> based on cyclecounter, have cyclecounter struct as member of timecounter
> struc
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
This reverts commit "fs: jbd2: pull your plug when waiting for space".
This was a duct-tape fix which shouldn't be needed since commit
"locking/rt-mutex: fix
Hi stable/arm/Willy,
1f65c13efef69b6dc908e588f91a133641d8475c is an important commit,
because it involves evaluation of pointers from userspace. I'm running
into issues with RNDADDTOENTCNT reading bogus values, because p is
incremented twice as much as it should in this random.c block:
ca
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
required for following networking patch which does recursive try-lock.
While at it, add the !RT version of it because it did not yet exist.
Cc: rt-sta...@vg
On Fri, Dec 01, 2017 at 09:32:12AM -0600, Andrew F. Davis wrote:
> On 12/01/2017 07:39 AM, Mark Brown wrote:
> > Is the interrupt only available on GPIO1?
> Some devices can route this to GPIO2 IIRC.
> I'm not sure how that would be supported, I think we would need to add
> interrupt names to DT
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
We must not wake any process (and thus acquire the pi->lock) while
holding the hrtimer's base lock. This does not happen usually because
the hrtimer-callback
4.9.65-rt57-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
hrtimers, which were deferred to the softirq context, and expire between
softirq shutdown and hrtimer migration are dangling around. If the CPU
goes back up
add irq error handlers for cmu, plb, opb, mcue, conf
with debug information output in case of problems.
Signed-off-by: Ivan Mikhaylov
---
arch/powerpc/platforms/44x/fsp2.c | 205 -
1 files changed, 204 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/
301 - 400 of 834 matches
Mail list logo
