> On 25 Apr 2018, at 13:22, Dag Moxnes wrote:
>
> The function rds_ib_setup_qp is calling rds_ib_get_client_data and
> should correspondingly call rds_ib_dev_put. This call was lost in
> the non-error path with the introduction of error handling done in
> commit 3b12f73a5c29 ("rds: ib: add erro
There is no reason to initialize uartclk to BASE_BAUD * 16 for DT based
systems.
Signed-off-by: Michal Simek
Tested-by: Matt Redfearn
---
It looks like from history that portclk = BASE_BAUD * 16 was setup to
get on calculation on x86 (divisor = 1) but it shouldn't be needed on DT based
system.
Hello Alex,
I have already proposed it few weeks ago.
https://lkml.org/lkml/2018/4/10/192
could you ack it, if you test it on your side?
Thanks,
Arnaud
On 04/25/2018 03:36 PM, Alex Elder wrote:
> The last commit to "remoteproc_core.c":
> 880f5b388252 remoteproc: eAPass type of shutdown to su
On Tue, Apr 24, 2018 at 03:18:21PM +0200, Luc Van Oostenryck wrote:
> The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
> which is a typedef for an enum type, but the implementation in this
> driver returns an 'int'.
>
> Fix this by returning 'netdev_tx_t' in this driver too.
>
From: Kan Liang
Perf stat doesn't count the uncore event aliases from the same uncore
block in a group, for example:
perf stat -e '{unc_m_cas_count.all,unc_m_clockticks}' -a -I 1000
# time counts unit events
1.000447342unc_m_cas_count.all
1.000
On 25/04/2018 10:25, Cornelia Huck wrote:
On Thu, 19 Apr 2018 16:48:06 +0200
Pierre Morel wrote:
The Sub channel event callback is threaded using workqueues.
The work uses the FSM introducing the VFIO_CCW_EVENT_SCH_EVENT
event.
I don't think this is a good name; after all, all of the events a
On Wed, 25 Apr 2018 16:47:01 +0300
Jani Nikula wrote:
> On Fri, 06 Apr 2018, Heikki Krogerus wrote:
> > Using reStructuredText literal-block element with ascii-art.
> > That prevents the ascii art from being processed as
> > reStructuredText.
> >
> > Reported-by: Masanari Iida
> > Fixes: bdecb3
On 04/24, Eric W. Biederman wrote:
>
> Let me respectfully suggest that the wait_event_killable on that code
> path is wrong.
I tend to agree even if I don't know this code.
But if it can be called from f_op->release() then any usage of "current" or
signals looks suspicious. Simply because "curre
* Eyal Reizer [180425 13:43]:
> pm_runtime handles sdio power on and power off transitions.
> An old workaround for trying to control the power explicitly from the
> driver was in fact causing failures on suspend/resume as the mmc layer
> already power the module on resume.
>
> In case of resume
On Wed, Apr 25, 2018 at 06:29:05PM +0530, Jagan Teki wrote:
> On Tue, Apr 24, 2018 at 7:38 PM, Maxime Ripard
> wrote:
> > On Tue, Apr 24, 2018 at 07:04:12PM +0530, Jagan Teki wrote:
> >> Allwinner A64 has display engine pipeline like other Allwinner SOC's
> >> A83T/H3/H5.
> >>
> >> A64 DE2 behavi
On 25/04/2018 10:44, Cornelia Huck wrote:
On Thu, 19 Apr 2018 16:48:12 +0200
Pierre Morel wrote:
VFIO_CCW_STATE_BOXED and VFIO_CCW_STATE_BUSY are the same
states.
Let's only keep one: VFIO_CCW_STATE_BUSY
Signed-off-by: Pierre Morel
---
drivers/s390/cio/vfio_ccw_fsm.c | 9 -
dr
Eyal Reizer writes:
> pm_runtime handles sdio power on and power off transitions.
> An old workaround for trying to control the power explicitly from the
> driver was in fact causing failures on suspend/resume as the mmc layer
> already power the module on resume.
>
> In case of resume pm_runtime
On Wed, Apr 25, 2018 at 8:39 PM, Maxime Ripard
wrote:
> On Wed, Apr 25, 2018 at 11:19:20AM +0800, Chen-Yu Tsai wrote:
>> On Wed, Apr 25, 2018 at 3:37 AM, Maxime Ripard
>> wrote:
>> > On Tue, Apr 24, 2018 at 08:17:11PM +0800, Chen-Yu Tsai wrote:
>> >> On Tue, Apr 24, 2018 at 8:13 PM, Maxime Ripard
On Wed, Apr 25, 2018 at 04:47:01PM +0300, Jani Nikula wrote:
> On Fri, 06 Apr 2018, Heikki Krogerus wrote:
> > Using reStructuredText literal-block element with ascii-art.
> > That prevents the ascii art from being processed as
> > reStructuredText.
> >
> > Reported-by: Masanari Iida
> > Fixes: b
On 25/04/2018 10:48, Cornelia Huck wrote:
On Thu, 19 Apr 2018 16:48:13 +0200
Pierre Morel wrote:
In the current implementation, we do not want to start a new SSCH
command before the last one ends.
Signed-off-by: Pierre Morel
---
drivers/s390/cio/vfio_ccw_fsm.c | 3 +++
drivers/s390/c
Hi everyone,
A lot of things have happened in the move to make the kernel y2038
ready in recent times. I've sent out new patches recently but will be
on vacation for the next few weeks, so here's a quick update on where
we are today with recent changes and work in progress:
- A large number of sm
On Mon, Apr 23, 2018 at 11:19:25PM -0500, Alex G. wrote:
> That tells you what FFS said about the error.
I betcha those status and command values have a human-readable counterparts.
Btw, what do you abbreviate with "FFS"?
> It's immediately obvious if there's a glaring FFS bug and if we get bogu
On 24 April 2018 11:41:29 AM GMT-07:00, "Michael S. Tsirkin"
wrote:
>On Fri, Apr 20, 2018 at 09:17:59PM +0300, Michael S. Tsirkin wrote:
>> Turns out virtio console tries to take a buffer out of an active vq.
>> Works by sheer luck, and is explicitly forbidden by spec. And while
>> going over
Enable the clock prior to calling clk_get_rate(), because clk_get_rate()
should only be called if the clock is enabled.
Found by Linux Driver Verification project (linuxtesting.org).
Fixes: 142168eba9dc ("spi: bcm63xx-hsspi: add bcm63xx HSSPI driver")
Signed-off-by: Stefan Potyra
---
drivers/sp
On 04/24/2018 11:22 AM, David Howells wrote:
> Stephen Smalley wrote:
>
>> Neither fsopen() nor fscontext_fs_write() appear to perform any kind of
>> up-front permission checking (DAC or MAC), although some security hooks may
>> be ultimately called to allocate structures, parse security options,
On 4/23/2018 3:10 PM, Alex Williamson wrote:
>> Do we need a retrain API with the speed that driver wants to reach to?
>> API can return what was actually accomplished. The quirk from Alex can
>> run inside this API to make a decision on what speed do we actually want
>> to reach to for a given PCI
On Wed, Apr 25, 2018 at 05:25:47PM +0800, Leo Yan wrote:
>
> If we have concern for security issue, should we remove support for
> 'bpf_jit_enable = 2' and modify the doc to reflect this change?
I suggest to fix the doc.
Since tmpfs THP was supported in 4.8, hugetlbfs is not the only
filesystem with huge page support anymore. tmpfs can use huge page via
THP when mounting by "huge=" mount option.
When applications use huge page on hugetlbfs, it just need check the
filesystem magic number, but it is not enough for t
On Wed, Apr 25, 2018 at 07:36:21PM +0900, Tetsuo Handa wrote:
> Kees Cook wrote:
> > On Tue, Apr 24, 2018 at 12:58 PM, Serge E. Hallyn wrote:
> > > Quoting Tycho Andersen (ty...@tycho.ws):
> > >> On Tue, Apr 24, 2018 at 11:46:38PM +0900, Tetsuo Handa wrote:
> > >> > Tycho Andersen wrote:
> > >> >
On Tue, Apr 24, 2018 at 4:15 PM, Luc Van Oostenryck
wrote:
> The method struct vga_switcheroo_handler::get_client_id() is defined
> as returning an 'enum vga_switcheroo_client_id' but the implementation
> in this driver, gmux_get_client_id(), returns an 'int'.
>
> Fix this by returning 'enum vga_s
On 04/25, Daniel Vetter wrote:
>
> On Wed, Apr 25, 2018 at 3:22 PM, Oleg Nesterov wrote:
> > On 04/24, Daniel Vetter wrote:
> >>
> >> wait_event_killabel doesn't check for fatal_signal_pending before calling
> >> schedule, so definitely has a nice race there.
> >
> > This is fine. See the signal_p
Apologies for any problems my patch may be causing.
I'm unclear on what is the proposed fix, other than reverting the commit.
In the problem scenario, is a --symfs option used? Is the debug info being
obtained from the symfs directory?
Unfortunately, I've had to change my focus for the time be
On Tue, Apr 24, 2018 at 07:30:43PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> We want to add support for device tree based early platform devices.
>
> In order not to introduce additional bloat for all users when we extend
> struct device to accomodate early platform DT su
On Wed, Apr 25, 2018 at 4:24 AM, Pankaj Gupta wrote:
> This patch adds virtio-pmem driver for KVM
> guest.
Minor nit, please expand your changelog line wrapping to 72 columns.
>
> Guest reads the persistent memory range
> information from Qemu over VIRTIO and registers
> it on nvdimm_bus. It als
On 04/25/2018 09:55 AM, Oleg Nesterov wrote:
On 04/24, Eric W. Biederman wrote:
Let me respectfully suggest that the wait_event_killable on that code
path is wrong.
I tend to agree even if I don't know this code.
But if it can be called from f_op->release() then any usage of "current" or
sig
Commit-ID: 51fc4be41c7ea7a00f6a17ad15ac9ea684d07921
Gitweb: https://git.kernel.org/tip/51fc4be41c7ea7a00f6a17ad15ac9ea684d07921
Author: Thomas Gleixner
AuthorDate: Tue, 24 Apr 2018 21:22:18 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 25 Apr 2018 16:11:58 +0200
tick/sched: Do not
On Wed, Apr 25, 2018 at 06:50:18AM -0700, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> Perf stat doesn't count the uncore event aliases from the same uncore
> block in a group, for example:
>
> perf stat -e '{unc_m_cas_count.all,unc_m_clockticks}' -a -I 1000
> # time
On 04/25/2018 06:58 AM, Pankaj Gupta wrote:
>
> Hi,
>
> Compile failures are because Qemu 'Memory-Device changes' are not yet
> in qemu master. As mentioned in Qemu patch message patch is
> dependent on 'Memeory-device' patches by 'David Hildenbrand'.
On 04/25/2018 06:24 AM, Pankaj Gupta wrote:
On Wed, Apr 25, 2018 at 4:24 AM, Pankaj Gupta wrote:
> This patch adds functionality to perform
> flush from guest to hosy over VIRTIO
> when 'ND_REGION_VIRTIO'flag is set on
> nd_negion. Flag is set by 'virtio-pmem'
> driver.
>
> Signed-off-by: Pankaj Gupta
> ---
> drivers/nvdimm/region_devs.c
On 04/25/2018 06:24 AM, Pankaj Gupta wrote:
> This patch adds virtio-pmem Qemu device.
>
> This device presents memory address range
> information to guest which is backed by file
> backend type. It acts like persistent memory
> device for KVM guest. Guest can perform read
> and persistent wri
It currently only works if the parent bus uses "simple-bus". We
currently try to probe children with non-existing compatible values.
And we're missing .probe.
I noticed this while testing devices configured to probe using ti-sysc
interconnect target module driver. For that we also may want to rebi
Hi Jerome:
On 04/25/2018 09:05 PM, Jerome Brunet wrote:
> On Thu, 2018-04-19 at 21:54 +0800, Yixun Lan wrote:
>> This patch try to add AO clock and Reset driver for Amlogic's
>> Meson-AXG SoC.
>> Please note that patch 7 need to wait for the DTS changes[3] merged
>> into mainline first, otherw
- Original Message -
> From: "Catalin Marinas"
> To: "Chunyu Hu"
> Cc: "Michal Hocko" , "Chunyu Hu" ,
> "Dmitry Vyukov" ,
> "LKML" , "Linux-MM"
> Sent: Wednesday, April 25, 2018 8:51:55 PM
> Subject: Re: [RFC] mm: kmemleak: replace __GFP_NOFAIL to GFP_NOWAIT in
> gfp_kmemleak_mask
>
This patch add the node to support APSS shared
mailbox on SDM845
Signed-off-by: Sibi Sankar
---
This patch depends on https://patchwork.kernel.org/patch/10276419/
arch/arm64/boot/dts/qcom/sdm845.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
Add the corresponding APSS shared offset for SDM845 SoC
Signed-off-by: Sibi Sankar
---
drivers/mailbox/qcom-apcs-ipc-mailbox.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mailbox/qcom-apcs-ipc-mailbox.c
b/drivers/mailbox/qcom-apcs-ipc-mailbox.c
index 57bde0dfd12f..75da44d25fac 1
Include SDM845 APSS shared to the list of possible bindings
Signed-off-by: Sibi Sankar
---
.../devicetree/bindings/mailbox/qcom,apcs-kpss-global.txt| 1 +
1 file changed, 1 insertion(+)
diff --git
a/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.txt
b/Documentation/de
On Wed, 25 Apr 2018 22:20:50 +0900
DaeRyong Jeong wrote:
> tty_insert_flip_string_fixed_flag() copies chars to the buffer indicated
> by th->used and updates tb->used.
> But tty_insert_flip_string_fixed_flag() can be executed concurrently and
> tb->used can be updated improperly.
The tty input l
Never directly free @dev after calling device_register(), even
if it returned an error. Always use put_device() to give up the
reference initialized.
Signed-off-by: Arvind Yadav
---
arch/arm/common/locomo.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/arch/arm/c
On Wed, Apr 25, 2018 at 12:33:40PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.37 release.
> There are 183 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
On 04/18/2018 04:10 PM, Jakob Unterwurzacher wrote:
> bus-off is usually caused by hardware malfunction or
> configuration error (baud rate mismatch) and causes a
> complete loss of communication.
>
> Increase the "bus-off" message's severity from netdev_dbg
> to netdev_info to make it visible to
On 4/25/2018 10:23 AM, Jiri Olsa wrote:
On Wed, Apr 25, 2018 at 06:50:18AM -0700, kan.li...@linux.intel.com wrote:
From: Kan Liang
Perf stat doesn't count the uncore event aliases from the same uncore
block in a group, for example:
perf stat -e '{unc_m_cas_count.all,unc_m_clockticks}' -a
On Wed, Apr 25, 2018 at 12:26 AM, Kalle Valo wrote:
> I have already applied an almost identical patch:
>
> ath9k: dfs: remove accidental use of stack VLA
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=ath-next&id=9c27489a34548913baaaf3b2776e05d4a9389e3e
Ah! Cool, no
[ adding Jeff directly since he has also been looking at
infrastructure to track when MAP_SYNC should be disabled ]
On Wed, Apr 25, 2018 at 7:21 AM, Dan Williams wrote:
> On Wed, Apr 25, 2018 at 4:24 AM, Pankaj Gupta wrote:
>> This patch adds virtio-pmem driver for KVM
>> guest.
>
> Minor nit, p
I am seeing the following on my system with 4.17-rc2. Probably in 4.17-rc1
as well.
Something to be concerned about. Is this related to
Commit: a45403b51582a87872927a3e0fc0a389c26867f1
ext4: always initialize the crc32c checksum driver?
WARNING: inconsistent lock
Never directly free @dev after calling device_register(), even
if it returned an error. Always use put_device() to give up the
reference initialized.
Signed-off-by: Arvind Yadav
---
arch/ia64/sn/kernel/tiocx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/ia64/sn/kerne
On Thu, Apr 19, 2018 at 11:33 AM, Kirill A. Shutemov
wrote:
> On Wed, Apr 18, 2018 at 08:53:09PM +0200, Andrey Konovalov wrote:
>> Hi!
>>
>> arm64 has a feature called Top Byte Ignore, which allows to embed pointer
>> tags into the top byte of each pointer. Userspace programs (such as
>> HWASan, a
On Wed 25-04-18 08:43:32, Mikulas Patocka wrote:
>
>
> On Tue, 24 Apr 2018, Michal Hocko wrote:
>
> > On Tue 24-04-18 19:17:12, Mikulas Patocka wrote:
> > >
> > >
> > > On Tue, 24 Apr 2018, Michal Hocko wrote:
> > >
> > > > On Wed 25-04-18 00:18:40, Richard Weinberger wrote:
> > > > > Am Dien
Add all the necessary dt nodes to support SMEM driver
on SDM845. It also adds the required memory carveouts
so that the kernel does not access memory that is in
use.
Signed-off-by: Sibi Sankar
---
This patch depends on:
https://patchwork.kernel.org/patch/10276419/
https://patchwork.kernel.org/pa
In the quest to remove all stack VLA usage removed from the kernel[1],
just use XFRM_MAX_DEPTH as already done for the "class" array. In one
case, it'll do this loop up to 5, the other caller up to 6.
[1] https://lkml.org/lkml/2018/3/7/621
Co-developed-by: Andreas Christoforou
Signed-off-by: Kee
On Wed, Apr 25, 2018 at 7:54 AM, Kishon Vijay Abraham I wrote:
> From: Hari Nagalla
>
> The wilink module is a combo wireless connectivity sdio
> card based on Texas Instrument's wl18xx solution. It is a
> 4-wire, 1.8V, embedded sdio wlan device with an external
> irq line and is power-controlled
On 04/25/2018 08:49 AM, Arnaud Pouliquen wrote:
> Hello Alex,
>
> I have already proposed it few weeks ago.
>
> https://lkml.org/lkml/2018/4/10/192
>
> could you ack it, if you test it on your side?
I am unable to test it. I found the bug by inspection (perhaps as
you did). However I'll give
On Tue 2018-04-24 10:51:04, Steven Rostedt wrote:
> On Tue, 24 Apr 2018 11:28:02 +0900
> Sergey Senozhatsky wrote:
>
> > Calling console drivers from printk_safe() context does not really
> > make call_console_drivers() any safer, because printk_safe() has
> > nothing to do with console drivers o
>
> On Wed, Apr 25, 2018 at 4:24 AM, Pankaj Gupta wrote:
> > This patch adds functionality to perform
> > flush from guest to hosy over VIRTIO
> > when 'ND_REGION_VIRTIO'flag is set on
> > nd_negion. Flag is set by 'virtio-pmem'
> > driver.
> >
> > Signed-off-by: Pankaj Gupta
> > ---
> > drive
On Wed, Apr 25, 2018 at 10:13:53PM +0800, Yang Shi wrote:
> Since tmpfs THP was supported in 4.8, hugetlbfs is not the only
> filesystem with huge page support anymore. tmpfs can use huge page via
> THP when mounting by "huge=" mount option.
>
> When applications use huge page on hugetlbfs, it jus
> 2) Compiler transformations can elide binary operations, so we cannot
>rely on source level AND (&) or MOD (%) operations to narrow the
>range of an expression, regardless of the types of either operand.
>
>This means that source-level AND and MOD operations cannot be relied
>upo
On Wed, Apr 25, 2018 at 7:54 AM, Kishon Vijay Abraham I wrote:
> From: Hari Nagalla
>
> Wilink8 module is a combo wireless connectivity card based
> on Texas Instrument's wl18xx solution.
>
> Add support for the wlan capabilities of this module by muxing
> the relevant mmc lines, and setting the
Introduce interrupt handler for smp2p ready interrupt and
handle start completion. Remove the proxy votes for clocks
and regulators in the handover interrupt context. Disable
wdog and fatal interrupts on remoteproc device stop and
re-enable them on remoteproc device start.
Signed-off-by: Sibi Sank
> > Hi,
> >
> > Compile failures are because Qemu 'Memory-Device changes' are not yet
> > in qemu master. As mentioned in Qemu patch message patch is
> > dependent on 'Memeory-device' patches by 'David Hildenbrand'.
>
>
> On 04/25/2018 06:24 AM, Pankaj Gupta wrote:
> > This PV device code is d
On Tue, Apr 24, 2018 at 02:27:35PM +0300, Kirill A. Shutemov wrote:
> On Sun, Apr 22, 2018 at 07:44:39AM -0600, Michal Hocko wrote:
> > On Thu 19-04-18 13:21:14, Kirill A. Shutemov wrote:
> > > On Thu, Apr 19, 2018 at 08:51:11AM +0200, Michal Hocko wrote:
> > > > On Thu 19-04-18 10:36:39, Wu Fenggu
On 04/11/2018 03:42 AM, Jia-Ju Bai wrote:
> peak_pci_probe() is never called in atomic context.
>
> peak_pci_probe() is set as ".probe" in struct pci_driver.
>
> Despite never getting called from atomic context, peak_pci_probe()
> calls mdelay() to busily wait.
> This is not necessary and can be
On Wed, Apr 25, 2018 at 04:54:13PM +0530, Pankaj Gupta wrote:
> diff --git a/include/uapi/linux/virtio_ids.h b/include/uapi/linux/virtio_ids.h
> index 6d5c3b2..5ebd049 100644
> --- a/include/uapi/linux/virtio_ids.h
> +++ b/include/uapi/linux/virtio_ids.h
> @@ -43,5 +43,6 @@
> #define VIRTIO_ID_INP
> > I think memory allocation and io waits can't be decoupled from
> > scheduling as they are now.
>
> The scheduler is not decoupled from either, it is intimately involved
> in both. However, none of the decision making smarts for either reside
> in the scheduler, nor should they.
It belongs
>
> On 04/25/2018 06:24 AM, Pankaj Gupta wrote:
> > This patch adds virtio-pmem Qemu device.
> >
> > This device presents memory address range
> > information to guest which is backed by file
> > backend type. It acts like persistent memory
> > device for KVM guest. Guest can perform read
> > an
On Mon, 2018-04-23 at 08:47 +0200, Ulf Hansson wrote:
> On 20 April 2018 at 17:53, Eugeniy Paltsev
> wrote:
> > Hi Ulf,
> >
> > On Fri, 2018-04-20 at 09:35 +0200, Ulf Hansson wrote:
> > > [...]
> > >
> > > >
> > > > 2. Add missing stuff to support multislot mode in DesignWare MMC driver.
> > >
Miklos Szeredi:
> This patch series reverts the VFS hacks (with the exception of d_path) and
I totally agree with removing d_real things.
It must be good to the world.
If I understand correctly, this series affects file_inode() too.
So there may exist more commits to revert such as
fea6d2
Never directly free @dev after calling device_register(), even
if it returned an error. Always use put_device() to give up the
reference initialized.
Signed-off-by: Arvind Yadav
---
arch/sparc/kernel/vio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/sparc/kernel/vio.
On Wed, 2018-04-25 at 13:12 +0200, Petr Mladek wrote:
> Move the code from the long pointer() function. We are going to add a
> check
> for the access to the address that will make it even more complicated.
>
> This patch does not change the existing behavior.
> +static char *va_format(char *buf
On Wed, 2018-04-25 at 13:12 +0200, Petr Mladek wrote:
> vsprintf() must not change any data that parameters point to.
> Let's add the missing const qualifier to ptr_to_id().
>
> This patch does not change the existing behavior.
>
Reviewed-by: Andy Shevchenko
> Signed-off-by: Petr Mladek
> ---
On Wed, 2018-04-25 at 13:12 +0200, Petr Mladek wrote:
> This is just a preparation step for further changes.
>
> The patch does not change the code.
>
Reviewed-by: Andy Shevchenko
> Signed-off-by: Petr Mladek
> ---
> lib/vsprintf.c | 244 --
> -
As the Linux networking maintainer, I feel the need to reiterate my
statement of a month ago, and to provide some supporting facts on my
end so that there is no confusion in the community on these issues.
I am no longer associated with either the Netdev Society or their
event, the NetDev conferen
On Tue, Apr 24, 2018 at 03:56:23PM -0400, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> The SMM freeze feature was introduced since PerfMon V2. But the current
> code unconditionally enables the feature for all platforms. It can
> generate #GP exception, if the related FREEZE_WHILE_SMM b
On Wed, 2018-04-25 at 13:12 +0200, Petr Mladek wrote:
> restricted_pointer() pretends that it prints the address when
> kptr_restrict
> is set to zero. But it is never called in this situation. Instead,
> pointer() falls back to ptr_to_id() and hashes the pointer.
>
> This patch removes the potent
On Wed, 25 Apr 2018 07:46:39 -0700
Kees Cook wrote:
> In the quest to remove all stack VLA usage removed from the kernel[1],
> just use XFRM_MAX_DEPTH as already done for the "class" array. In one
> case, it'll do this loop up to 5, the other caller up to 6.
>
> [1] https://lkml.org/lkml/2018/3/
On Wed, Apr 25, 2018 at 10:42:27AM -0400, Liang, Kan wrote:
>
>
> On 4/25/2018 10:23 AM, Jiri Olsa wrote:
> > On Wed, Apr 25, 2018 at 06:50:18AM -0700, kan.li...@linux.intel.com wrote:
> > > From: Kan Liang
> > >
> > > Perf stat doesn't count the uncore event aliases from the same uncore
> > >
On Tue, Apr 24, 2018 at 3:56 PM, Frank Rowand wrote:
> Hi Alan,
>
> On 04/23/18 15:38, Frank Rowand wrote:
>> Hi Jan,
>>
>> + Alan Tull for fpga perspective
>>
>> On 04/22/18 03:30, Jan Kiszka wrote:
>>> On 2018-04-11 07:42, Jan Kiszka wrote:
On 2018-04-05 23:12, Rob Herring wrote:
> On T
On Tue, Apr 24, 2018 at 5:58 PM, Florian Fainelli wrote:
> Hi Linus, Rafael, all
>
> Our GPIO controller driver: gpio-brcmstb.c has a shutdown callback which
> gets invoked when the system is brought into poweroff aka S5. So far so
> good, except that we also wish to use gpio_keys.c as a possible
On 04/25/2018 09:01 AM, Borislav Petkov wrote:
> On Mon, Apr 23, 2018 at 11:19:25PM -0500, Alex G. wrote:
>> That tells you what FFS said about the error.
>
> I betcha those status and command values have a human-readable counterparts.
>
> Btw, what do you abbreviate with "FFS"?
Firmware-first
On Wed, 2018-04-25 at 13:12 +0200, Petr Mladek wrote:
> Move code from the long pointer() function. We are going to add a
> check for
> the access to the address that will make it even more complicated.
>
> Also it is better to warn about unknown specifier instead of falling
> back to the %p behav
Most architectures now use the asm-generic copy of the sysvipc data
structures (msqid64_ds, semid64_ds, shmid64_ds), which use 32-bit
__kernel_time_t on 32-bit architectures but have padding behind them to
allow extending the type to 64-bit.
Unfortunately, that fails on all big-endian architecture
The alpha ipcbuf/msgbuf/sembuf/shmbuf header files are all identical
to the version from asm-generic.
This patch removes the files and replaces them with 'generic-y'
statements as part of the y2038 series. Since there is no 32-bit
syscall support for alpha, we don't need the other changes, but
it'
The ia64 ipcbuf/msgbuf/sembuf/shmbuf header files are all identical
to the version from asm-generic.
This patch removes the files and replaces them with 'generic-y'
statements as part of the y2038 changes. While ia64 no longer has
a compat mode and doesn't need the file any more, it seem nicer
to
This extends the x86 copy of the sysvipc data structures to deal with
32-bit user space that has 64-bit time_t and wants to see timestamps
beyond 2038.
Fortunately, x86 has padding for this purpose in all the data structures,
so we can just add extra fields. With msgid64_ds and shmid64_ds, the
dat
On Wed, Apr 25, 2018 at 03:48:52PM +0100, Alan Cox wrote:
> > 2) Compiler transformations can elide binary operations, so we cannot
> >rely on source level AND (&) or MOD (%) operations to narrow the
> >range of an expression, regardless of the types of either operand.
> >
> >This mean
From: Colin Ian King
The current code decrements the timeout counter i and the end of
each loop i is incremented, so the check for timeout will always
be false and hence the timeout mechanism is just a dead code path.
Potentially, if the RD_READY bit is not set, we could end up in
an infinite loo
On Tue, Apr 24, 2018 at 11:49 AM, Srinivas Kandagatla
wrote:
> Thanks for the review.
>
>
> On 24/04/18 17:25, Rob Herring wrote:
>>
>> On Wed, Apr 18, 2018 at 04:31:55PM +0100, srinivas.kandaga...@linaro.org
>> wrote:
>>>
>>> From: Srinivas Kandagatla
>>>
>>> Add devicetree bindings documentatio
Hi,
Kindly pull the new firmware from the following URL.
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
Thanks
Ganesh
The following changes since commit 0caed67f661bfa9552b636d1e4af379eda75ed67:
cxgb4: update firmware to revision 1.19.1.0 (2018-04-25 07:48:21 -0700)
are availa
The ia64 ipcbuf/msgbuf/sembuf/shmbuf header files are all identical
to the version from asm-generic.
This patch removes the files and replaces them with 'generic-y'
statements as part of the y2038 changes. While ia64 no longer has
a compat mode and doesn't need the file any more, it seem nicer
to
MIPS is the weirdest case for sysvipc, because each of the
three data structures is done differently:
* msqid64_ds has padding in the right place so we could in theory
extend this one to just have 64-bit values instead of time_t.
As this does not work for most of the other combinations,
we j
The s390 msgbuf/sembuf/shmbuf header files are all identical to the
version from asm-generic.
This patch removes the files and replaces them with 'generic-y'
statements, to avoid having to modify each copy when we extend sysvipc
to deal with 64-bit time_t in 32-bit user space.
Note that unlike al
On Wed, Apr 25, 2018 at 07:41:10AM -0700, Guenter Roeck wrote:
> On Wed, Apr 25, 2018 at 12:33:40PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.37 release.
> > There are 183 patches in this series, all will be posted as a response
> > to this one.
The shmid64_ds/semid64_ds/msqid64_ds data structures have been extended
to contain extra fields for storing the upper bits of the time stamps,
this patch does the other half of the job and and fills the new fields on
32-bit architectures as well as 32-bit tasks running on a 64-bit kernel
in compat
On Wed, Apr 25, 2018 at 3:22 PM, Arnd Bergmann wrote:
> Most architectures now use the asm-generic copy of the sysvipc data
> structures (msqid64_ds, semid64_ds, shmid64_ds), which use 32-bit
> __kernel_time_t on 32-bit architectures but have padding behind them to
> allow extending the type to 64
The alpha ipcbuf/msgbuf/sembuf/shmbuf header files are all identical
to the version from asm-generic.
This patch removes the files and replaces them with 'generic-y'
statements as part of the y2038 series. Since there is no 32-bit
syscall support for alpha, we don't need the other changes, but
it'
Three ipc syscalls (mq_timedsend, mq_timedreceive and and semtimedop)
take a timespec argument. After we move 32-bit architectures over to
useing 64-bit time_t based syscalls, we need seperate entry points for
the old 32-bit based interfaces.
This changes the #ifdef guards for the existing 32-bit
This patch series add support for remoteproc Q6v5 modem-pil on Qualcomm
SDM845 SoC. The first patch adds AOSS (Always on subsystem) reset driver
to provide for mss reset line. The last couple of patches add the resets
sequence for Q6 on SDM845 and adds helper functions for arbitrary reset
assert/de
601 - 700 of 1348 matches
Mail list logo
