[PATCH] kconfig: Document the 'symbol' struct

Visibility and choices in particular might be a bit tricky to figure out. Also fix existing comment to point out that P_MENU is also used for menus. Signed-off-by: Ulf Magnusson --- scripts/kconfig/expr.h | 45 - 1 file changed,

Re: [PATCH 2/8] ARM: dts: aspeed: Reorder ADC node

On Wed, 2017-10-04 at 14:43 +0930, Joel Stanley wrote: > > > > > > + adc: adc@1e6e9000 { > > > + compatible = "aspeed,ast2500-adc"; > > > + reg = <0x1e6e9000 0xb0>; > > > > Did you intend to change the size cell value

Re: [PATCH 4/8] ARM: dts: aspeed-romulus: Add I2C devices

On Wed, Oct 4, 2017 at 2:32 PM, Andrew Jeffery wrote: > On Thu, 2017-09-28 at 17:21 +0930, Joel Stanley wrote: >> Enable the buses that are in use and the devices that are attached. >> Currently that is just the battery backed RTC. >> >> Some of these buses are for hotplugged

Re: [patch V2 22/29] lockup_detector: Make watchdog_nmi_reconfigure() two stage

Thomas Gleixner writes: > On Tue, 3 Oct 2017, Thomas Gleixner wrote: >> On Tue, 3 Oct 2017, Thomas Gleixner wrote: >> > On Tue, 3 Oct 2017, Michael Ellerman wrote: >> > > Hmm, I tried that patch, it makes the warning go away. But then I >> > > triggered a deliberate hard

Re: [PATCH 8/8] ARM: dts: aspeed: Clean up UART nodes

On Thu, 2017-09-28 at 17:21 +0930, Joel Stanley wrote: >  - Shorten size of reg property so it covers only the implemented >  registers >  >  - Add VUART compatible >  >  - Move stray uart1 in g5 definition >  >  - Remove outdated current-speed property. Different bootloaders use >  different

[PATCH V2] firmware: tegra: add BPMP debugfs support

Tegra power management firmware running on co-processor (BPMP) implements a simple pseudo file system akin to debugfs. The file system can be used for debugging purposes to examine and change the status of selected resources controlled by the firmware (such as clocks, resets, voltages, powergates,

Re: [PATCH] tee: ACPI support for optee driver

On 09/22/2017 05:37 AM, Lorenzo Pieralisi wrote: > On Thu, Sep 21, 2017 at 03:45:28PM +0800, Hanjun Guo wrote: >> On 2017/9/21 15:12, Mayuresh Chitale wrote: >>> This patch modifies the optee driver to add support for parsing >>> the conduit method from an ACPI node. >> >> Sorry I didn't involve

Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

On Tue, Oct 03, 2017 at 09:48:05AM -0700, Andy Lutomirski wrote: > On Tue, Oct 3, 2017 at 8:10 AM, Darren Hart wrote: > > On Tue, Oct 03, 2017 at 11:23:23AM +0200, Greg KH wrote: > >> On Wed, Sep 27, 2017 at 11:02:16PM -0500, Mario Limonciello wrote: > >> > For WMI

[PATCH 0/3 v8] oom: capture unreclaimable slab info in oom message

Recently we ran into a oom issue, kernel panic due to no killable process. The dmesg shows huge unreclaimable slabs used almost 100% memory, but kdump doesn't capture vmcore due to some reason. So, it may sound better to capture unreclaimable slab info in oom message when kernel panic to aid

[PATCH 2/3] mm: slabinfo: dump CONFIG_SLABINFO

According to the discussion with Christoph [1], it sounds it is pointless to keep CONFIG_SLABINFO around. This patch just remove CONFIG_SLABINFO config option, but /proc/slabinfo is still available. [1] https://marc.info/?l=linux-kernel=150695909709711=2 Signed-off-by: Yang Shi

[PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory

Kernel may panic when oom happens without killable process sometimes it is caused by huge unreclaimable slabs used by kernel. Although kdump could help debug such problem, however, kdump is not available on all architectures and it might be malfunction sometime. And, since kernel already panic it

[PATCH 1/3] tools: slabinfo: add "-U" option to show unreclaimable slabs only

Add "-U" option to show unreclaimable slabs only. "-U" and "-S" together can tell us what unreclaimable slabs use the most memory to help debug huge unreclaimable slabs issue. Signed-off-by: Yang Shi Acked-by: Christoph Lameter Acked-by: David Rientjes

[PATCH 2/2] scripts/dtc: Update to upstream version v1.4.5-3-gb1a60033c110

This adds the following commits from upstream: b1a60033c110 tests: Add a test for overlays syntactic sugar 737b2df39cc8 overlay: Add syntactic sugar version of overlays 497432fd2131 checks: Use proper format modifier for size_t 22a65c5331c2 dtc: Bump version to v1.4.5 c575d8059fff Add fdtoverlay

[PATCH 1/2] scripts/dtc: add fdt_overlay.c and fdt_addresses.c to sync script

libfdt has gained some new files. We need to include them in the kernel's copy. Reported-by: Kyle Yan Signed-off-by: Rob Herring --- scripts/dtc/update-dtc-source.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

Re: [PATCH 1/2] of/fdt: add of_fdt_device_is_available function

On Tue, 3 Oct 2017, Rob Herring wrote: > Add an equivalent function to of_device_is_available for flattened DT, and > convert the one existing open coded occurrence. > > Cc: Nicolas Pitre > Cc: Frank Rowand > Signed-off-by: Rob Herring

Re: [Regulator] Request for clarification - GPIO controlled regulator, USB VBUS,

Hi Łukasz, On Tue, Oct 3, 2017 at 9:58 AM, Łukasz Majewski wrote: > Dear All, > > Maybe somebody could shed some light to following issue: > > On my setup I do have USB connected touchscreen powered from VBUS. > > The VBUS power is controlled by a GPIO pin, which in turn is

Re: [PATCH 4.13 000/110] 4.13.5-stable review

On 10/03/2017 06:28 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.13.5 release. > There are 110 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 know. > > Responses

Re: Is GET_CR0_INTO_EAX macro unused?

On Mon, 2 Oct 2017, Denys Vlasenko wrote: > Hi Andy, > > From by git archaeology, looks like last use of GET_CR0_INTO_EAX > was removed long ago, in 2008 (see commit below). > > Right now, I only grep it here in a comment in entry_32.S: > /* > * We use macros for low-level operations which

Re: [PATCH 2/2] pci: Expose offset, stride, and VF device ID via sysfs

On Tue, Oct 03, 2017 at 02:31:14PM -0500, Bjorn Helgaas wrote: > On Fri, Sep 29, 2017 at 07:53:31AM +, Sironi, Filippo wrote: > > > > Hi Bjorn, > > > > > On 25. Sep 2017, at 20:55, Bjorn Helgaas wrote: > > > > > > Hi Filippo, > > > > > > On Mon, Aug 28, 2017 at

Re: [RESEND PATCH] prctl: add PR_[GS]ET_PDEATHSIG_PROC

On Tue, 2017-10-03 at 12:40 -0500, Eric W. Biederman wrote: > Jürg Billeter writes: > > What's actually the reason that CLONE_NEWPID requires CAP_SYS_ADMIN? > > Does CLONE_NEWPID pose any risks that don't exist for > > CLONE_NEWUSER|CLONE_NEWPID? Assuming we can't simply drop

Re: Problems compiling with KCFLAGS="-frecord-gcc-switches"

On Tue, Oct 03, 2017 at 10:54:57AM -0700, Guenter Roeck wrote: > Hi Josh, > > On Fri, Sep 29, 2017 at 03:46:09PM -0500, Josh Poimboeuf wrote: > > On Fri, Sep 29, 2017 at 01:00:56PM -0700, Guenter Roeck wrote: > > > Hi Josh, > > > > > > when trying to compile an image with

Re: [PATCH] iommu/vt-d: Fix scatterlist offset handling

On 03/10/17 13:55, David Woodhouse wrote: > On Thu, 2017-09-28 at 15:14 +0100, Robin Murphy wrote: >> The intel-iommu DMA ops fail to correctly handle scatterlists where >> sg->offset is greater than PAGE_SIZE - the IOVA allocation is computed >> appropriately based on the page-aligned portion of

Re: [PATCH] ARM: head-common.S: Clear lr before jumping to start_kernel()

On Tue, Oct 3, 2017 at 5:37 PM, Nicolas Pitre wrote: > On Tue, 3 Oct 2017, Geert Uytterhoeven wrote: > >> If CONFIG_DEBUG_LOCK_ALLOC=y, the kernel log is spammed with a few >> hundred identical messages: >> >> unwind: Unknown symbol address c0800300 >> unwind:

Re: [PATCH] string.h: work around for increased stack usage

-for-increased-stack-usage/20171003-210611 config: x86_64-randconfig-ws0-10040032 (attached as .config) compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All error/warnings (new ones prefixed by >>): In file include

[PATCH v2 3/4] locking: Remove dummy arch_{read,spin,write}_relax implementations

arch_{read,spin,write}_relax are defined as cpu_relax() by the core code, so architectures that can't do better (i.e. most of them) don't need to bother with the dummy definitions. Cc: Peter Zijlstra Signed-off-by: Will Deacon ---

Re: [PATCH 2/2] of/fdt: skip unflattening of disabled nodes

On Tue, 3 Oct 2017, Rob Herring wrote: > For static DT usecases, we don't need the disabled nodes and can skip > unflattening. This saves a significant amount of RAM in memory constrained > cases. In one example on STM32F469, the RAM usage goes from 118K to 26K. > > There are a few cases in the

[RFC 5/5] pm: remove kernel thread freezing

Now that all filesystems which used to rely on kthread freezing have been converted to filesystem freeze/thawing we can remove the kernel kthread freezer. Signed-off-by: Luis R. Rodriguez --- Documentation/power/freezing-of-tasks.txt | 9 -- drivers/xen/manage.c

[RFC 1/5] fs: add iterate_supers_reverse()

There are use cases where we wish to traverse the superblock list in reverse order. This particular implementation will also enable to capture errors. Signed-off-by: Luis R. Rodriguez --- fs/super.c | 43 +++ include/linux/fs.h

[RFC 3/5] xfs: allow fs freeze on suspend/hibernation

This also removes the freezer calls on the XFS kthread as they are no longer needed. Signed-off-by: Luis R. Rodriguez --- fs/xfs/xfs_super.c | 3 ++- fs/xfs/xfs_trans_ail.c | 7 ++- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/fs/xfs/xfs_super.c

Re: [RFC 5/5] pm: remove kernel thread freezing

On Tuesday, October 3, 2017 8:53:13 PM CEST Luis R. Rodriguez wrote: > Now that all filesystems which used to rely on kthread > freezing have been converted to filesystem freeze/thawing > we can remove the kernel kthread freezer. > > Signed-off-by: Luis R. Rodriguez I like

Re: [PATCH v2] ide: pci: free PCI BARs on initialization failure

[+cc linux-pci] On Tue, Oct 03, 2017 at 02:17:13PM +0200, Bartlomiej Zolnierkiewicz wrote: > Recent pci_assign_irq() changes uncovered a problem with missing > freeing of PCI BARs on PCI IDE host initialization failure: > > ide0: disabled, no IRQ > ide0: failed to initialize IDE interface >

Re: [PATCH V8 5/8] percpu-refcount: introduce __percpu_ref_tryget_live

On Tue, Oct 03, 2017 at 06:40:24PM +, Bart Van Assche wrote: > On Tue, 2017-10-03 at 22:04 +0800, Ming Lei wrote: > > Block layer need to call this function after holding > > rcu lock in a real hot path, so introduce this helper. > > Since it is allowed to nest rcu_read_lock_sched() calls I

Re: [PATCH 2/2] pci: Expose offset, stride, and VF device ID via sysfs

On Fri, Sep 29, 2017 at 07:53:31AM +, Sironi, Filippo wrote: > > Hi Bjorn, > > > On 25. Sep 2017, at 20:55, Bjorn Helgaas wrote: > > > > Hi Filippo, > > > > On Mon, Aug 28, 2017 at 03:38:50PM +0200, Filippo Sironi wrote: > >> +static ssize_t sriov_vf_did_show(struct

Re: [PATCH V8 5/8] percpu-refcount: introduce __percpu_ref_tryget_live

Hello, On Wed, Oct 04, 2017 at 03:20:40AM +0800, Ming Lei wrote: > On Tue, Oct 03, 2017 at 07:14:59AM -0700, Tejun Heo wrote: > > Hello, > > > > On Tue, Oct 03, 2017 at 10:04:03PM +0800, Ming Lei wrote: > > > Block layer need to call this function after holding > > > rcu lock in a real hot path,

Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

I think David Hermann had some review comments. --Andy On Oct 3, 2017, at 11:38 AM, wrote: >> -Original Message- >> From: Andy Lutomirski [mailto:l...@kernel.org] >> Sent: Tuesday, October 3, 2017 11:48 AM >> To: Darren Hart

Re: [PATCH] pinctrl: cherryview: fix issues caused by dynamic gpio irqs mapping

On Tue, Oct 3, 2017 at 8:00 PM, Grygorii Strashko wrote: > New GPIO IRQs are allocated and mapped dynamically by default when > GPIO IRQ infrastructure is used by cherryview-pinctrl driver. > This causes issues on some Intel platforms [1][2] with broken BIOS which >

Re: Problems compiling with KCFLAGS="-frecord-gcc-switches"

Hi Josh, On Fri, Sep 29, 2017 at 03:46:09PM -0500, Josh Poimboeuf wrote: > On Fri, Sep 29, 2017 at 01:00:56PM -0700, Guenter Roeck wrote: > > Hi Josh, > > > > when trying to compile an image with KCFLAGS="-frecord-gcc-switches", > > I get the folllowing build warning/error. > > > > make

Re: [PATCH v2 4/4] KVM: LAPIC: Don't silently accept bad vectors

2017-09-28 18:04-0700, Wanpeng Li: > From: Wanpeng Li > > Vectors 0-15 are reserved, and a physical LAPIC - upon sending or > receiving one - would generate an APIC error instead of doing the > requested action. Make our emulation behave similarly. > > Cc: Paolo Bonzini

Re: [PATCH 0/3 v8] oom: capture unreclaimable slab info in oom message

This round should be v9. Sorry for the typo. Yang On 10/3/17 11:06 AM, Yang Shi wrote: Recently we ran into a oom issue, kernel panic due to no killable process. The dmesg shows huge unreclaimable slabs used almost 100% memory, but kdump doesn't capture vmcore due to some reason. So, it

Re: [f2fs-dev] [PATCH v4] f2fs: introduce discard_granularity sysfs entry

Hi Chao. Yep, that patch seems to have fixed it. Doing "while true; do fstrim -v /; done" while "rm -rf"ing a 2GB kbuild directory (with lots of small .o files and stuff) ended flawlessly. I hope to see this patch merged with next 4.14 merge cycle. Thanks :) On Tue, Oct 3, 2017 at 12:59 AM,

RE: [PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

> -Original Message- > From: Andy Lutomirski [mailto:l...@kernel.org] > Sent: Tuesday, October 3, 2017 11:48 AM > To: Darren Hart > Cc: Greg KH ; Limonciello, Mario > ; Andy Shevchenko > ; LKML

[RELEASE] LTTng-modules 2.9.4 and 2.10.1 (Linux kernel tracer)

Hi, Those are bugfix releases for the LTTng modules Linux kernel tracer currently maintained stable branches. They also update instrumentation to support Linux kernels up to and including current 4.14-rc Linux kernels. Project website: http://lttng.org Documentation: http://lttng.org/docs

Re: [PATCH v2 4/5] powerpc: pseries: only store the device node basename in full_name

On Tue, Oct 3, 2017 at 4:26 AM, Michael Ellerman wrote: > Hi Rob, > > Unfortunately this one has a bug, which only showed up after some stress > testing. > > Rob Herring writes: >> With dependencies on full_name containing the entire device node path >>

[RFC 2/5] fs: freeze on suspend and thaw on resume

This uses the existing filesystem freeze and thaw callbacks to freeze each filesystem on suspend/hibernation and thaw upon resume. This is needed so that we properly really stop IO in flight without races after userspace has been frozen. Without this we rely on kthread freezing and its semantics

[RFC 4/5] ext4: add fs freezing support on suspend/hibernation

This also removes the superflous freezer calls as they are no longer needed. We need to avoid sync call on thaw as otherwise we end up with a stall on bio_submit(). Signed-off-by: Luis R. Rodriguez --- fs/ext4/super.c | 13 +++-- 1 file changed, 7 insertions(+), 6

[RFC 0/5] fs: replace kthread freezing with filesystem freeze/thaw

At the 2015 South Korea kernel summit Jiri Kosina had pointd out the issue of the sloppy semantics of the kthread freezer, lwn covered this pretty well [0]. In short, he explained how the original purpose of the freezer was to aid in going to suspend to ensure no uwanted IO activity would cause

Re: [PATCH v2] ide: add missing hwif->portdev freeing on hwif_init() failure

On Tue, Oct 03, 2017 at 12:57:42PM -0500, Bjorn Helgaas wrote: > [+cc linux-pci for real] > > My plan is to take these two additional fixes via the PCI tree, along > with Lorenzo's patch to add a pci_assign_irq() call in > ide_scan_pcidev(), since they're all related. > > On Tue, Oct 03, 2017 at

[PATCH] media: staging/imx: do not return error in link_notify for unknown sources

imx_media_link_notify() should not return error if the source subdevice is not recognized by imx-media, that isn't an error. If the subdev has controls they will be inherited starting from a known subdev. Signed-off-by: Steve Longerbeam ---

Re: [RFC PATCH 1/2] arm64: mm: Use READ_ONCE/WRITE_ONCE when accessing page tables

On Fri, Sep 29, 2017 at 05:33:49PM +0100, Will Deacon wrote: > On Fri, Sep 29, 2017 at 09:29:39AM -0700, Paul E. McKenney wrote: > > On Fri, Sep 29, 2017 at 10:08:43AM +0100, Will Deacon wrote: > > > On Thu, Sep 28, 2017 at 05:58:30PM -0700, Paul E. McKenney wrote: > > > > On Fri, Sep 29, 2017 at

Re: [PATCH v2] drivers/ide/pci: Fix legacy IRQ assignment

On Mon, Oct 02, 2017 at 11:52:47AM +0100, Lorenzo Pieralisi wrote: > Through struct pci_host_bridge->{map/swizzle}_irq() hooks is now > possible to define IRQ mapping functions on a per PCI host bridge basis. > > Actual IRQ allocation is carried out by the pci_assign_irq() function in >

Re: [PATCH v2] mm/mempolicy: fix NUMA_INTERLEAVE_HIT counter

On Tue, Oct 03, 2017 at 10:10:03PM +0300, Andrey Ryabinin wrote: > Commit 3a321d2a3dde separated NUMA counters from zone counters, but > the NUMA_INTERLEAVE_HIT call site wasn't updated to use the new interface. > So alloc_page_interleave() actually increments NR_ZONE_INACTIVE_FILE > instead of

Re: [PATCH v3] crypto: s5p-sss: Add HASH support for Exynos

On Tue, Oct 03, 2017 at 04:57:43PM +0200, Kamil Konieczny wrote: > >> [...] > >> +static struct ahash_alg algs_sha256[] = { > >> +{ > >> + .init = s5p_hash_init, > >> + .update = s5p_hash_update, > >> + .final = s5p_hash_final, > >> + .finup =

Re: [RESEND PATCH] prctl: add PR_[GS]ET_PDEATHSIG_PROC

Linus Torvalds writes: > On Tue, Oct 3, 2017 at 9:36 AM, Eric W. Biederman > wrote: >> >> *Scratches head* >> pdeath_signal is cleared during exec if bprm->cap_elevated. > > It's not cleared if we are *releasing* capabilities, which is

Re: [RFC 2/5] fs: freeze on suspend and thaw on resume

On Tue, 2017-10-03 at 11:53 -0700, Luis R. Rodriguez wrote: > +static bool super_allows_freeze(struct super_block *sb) > +{ > + return !!(sb->s_type->fs_flags & FS_FREEZE_ON_SUSPEND); > +} A minor comment: if "!!" would be left out the compiler will perform the conversion from int to bool

Re: [RESEND PATCH] prctl: add PR_[GS]ET_PDEATHSIG_PROC

On Tue, Oct 3, 2017 at 12:30 PM, Eric W. Biederman wrote: > > We never signal the orignal parent. We signal the child that > requested the pdeath_signal when the original parent dies. Yeah, I keep making that mistake, because I always confuse this with the exit_signal

Re: [PATCH] mm/mempolicy: fix NUMA_INTERLEAVE_HIT counter

On Tue, Oct 03, 2017 at 07:47:20PM +0300, Andrey Ryabinin wrote: > Commit 3a321d2a3dde separated NUMA counters from zone counters, but > the NUMA_INTERLEAVE_HIT call site wasn't updated to use the new interface. > So alloc_page_interleave() actually increments NR_ZONE_INACTIVE_FILE > instead of

Re: [PATCH V8 0/8] block/scsi: safe SCSI quiescing

Also Tested-by: Oleksandr Natalenko for whole v8. On úterý 3. října 2017 16:03:58 CEST Ming Lei wrote: > Hi Jens, > > Please consider this patchset for V4.15, and it fixes one > kind of long-term I/O hang issue in either block legacy path > or blk-mq. > > The

Re: [PATCH] serial: imx: Correct comment imx_flush_buffer()

On Fri, Sep 29, 2017 at 10:22:19AM +0100, Martyn Welch wrote: > The comment in imx_flush_buffer() states that the state of 4 registers > are to be saved/restored, then only saves and restores 3 registers. The > missing register (UBRC) is read only and thus can't be restored. > > Update the

Re: [PATCH] vfs: hard-ban creating files with control characters in the name

On Tue, Oct 03, 2017 at 07:32:15PM +0200, Adam Borowski wrote: > > But Al has a good point that if most people were protected, they won't > bother escaping badness anymore -- leaving those whose systems allow control > chars vulnerable if they run a script that doesn't do quoting. If we look at

Re: [PATCH V8 5/8] percpu-refcount: introduce __percpu_ref_tryget_live

On Tue, Oct 03, 2017 at 07:14:59AM -0700, Tejun Heo wrote: > Hello, > > On Tue, Oct 03, 2017 at 10:04:03PM +0800, Ming Lei wrote: > > Block layer need to call this function after holding > > rcu lock in a real hot path, so introduce this helper. > > The patch description is too anemic. It

Re: [PATCH 4.4 00/41] 4.4.90-stable review

On 10/03/2017 06:21 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.90 release. > There are 41 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 know. > > Responses

Re: [PATCHv3] mm: Account pud page tables

On Mon, 2017-10-02 at 11:04 +0300, Kirill A. Shutemov wrote: > On machine with 5-level paging support a process can allocate > significant amount of memory and stay unnoticed by oom-killer and > memory cgroup. The trick is to allocate a lot of PUD page tables. > We don't account PUD page tables,

Re: [RFC 4/5] ext4: add fs freezing support on suspend/hibernation

On Tue, Oct 03, 2017 at 11:53:12AM -0700, Luis R. Rodriguez wrote: > @@ -4926,7 +4926,7 @@ static int ext4_unfreeze(struct super_block *sb) > ext4_set_feature_journal_needs_recovery(sb); > } > > - ext4_commit_super(sb, 1); > + ext4_commit_super(sb, 0); > return

Re: [RFC 0/5] fs: replace kthread freezing with filesystem freeze/thaw

On Wed, Oct 04, 2017 at 03:33:01AM +0800, Ming Lei wrote: > On Tue, Oct 03, 2017 at 11:53:08AM -0700, Luis R. Rodriguez wrote: > > INFO: task kworker/u8:8:1320 blocked for more than 10 seconds. > > Tainted: GE 4.13.0-next-20170907+ #88 > > "echo 0 >

Re: [PATCH v2] ide: add missing hwif->portdev freeing on hwif_init() failure

[+cc linux-pci for real] My plan is to take these two additional fixes via the PCI tree, along with Lorenzo's patch to add a pci_assign_irq() call in ide_scan_pcidev(), since they're all related. On Tue, Oct 03, 2017 at 01:18:47PM +0200, Bartlomiej Zolnierkiewicz wrote: > Recent pci_assign_irq()

Re: [PATCH] ARM: head-common.S: Clear lr before jumping to start_kernel()

On Tue, Oct 3, 2017 at 8:11 PM, Geert Uytterhoeven wrote: > On Tue, Oct 3, 2017 at 5:37 PM, Nicolas Pitre > wrote: >> On Tue, 3 Oct 2017, Geert Uytterhoeven wrote: >> Please send it to RMK's patch system. > > Done (I hope so ;-) Failed. Retrying.

Re: [RESEND PATCH] gpio: omap: Fix lost edge interrupts

On 10/3/2017 9:52 AM, Grygorii Strashko wrote: Hi Santosh, On 10/03/2017 11:41 AM, Santosh Shilimkar wrote: [...] This was one of the concern I was thinking when GPIO IRQ conversion was done. Grygorii since you did that conversion, can you please check since I see now that the irq code is

Re: [PATCH] ARM: head-common.S: Clear lr before jumping to start_kernel()

On Tue, Oct 3, 2017 at 8:15 PM, Geert Uytterhoeven wrote: > On Tue, Oct 3, 2017 at 8:11 PM, Geert Uytterhoeven > wrote: >> On Tue, Oct 3, 2017 at 5:37 PM, Nicolas Pitre >> wrote: >>> On Tue, 3 Oct 2017, Geert Uytterhoeven

Re: [GIT PULL] percpu fixes for v4.14-rc3

Hello, Linus. On Tue, Oct 03, 2017 at 10:27:42AM -0700, Linus Torvalds wrote: > On Tue, Oct 3, 2017 at 6:26 AM, Tejun Heo wrote: > > > > * Mark noticed that the generic implementations of percpu local atomic > > reads aren't properly protected against irqs and there's a (slim)

[PATCH] Makefile: Fix CONFIG_CC_STACKPROTECTOR_AUTO to not enable SSP

There was a think-o in the logic for CONFIG_CC_STACKPROTECTOR_AUTO, which would leave CONFIG_CC_STACKPROTECTOR defined when a compiler didn't support stack-protector. This usually won't cause a problem with a build, but it's not correct, and shouldn't happen. Reported-by: Mark Rutland

Re: [PATCH 3/3] mmc: dw_mmc: Add locking to the CTO timer

Hi, On Wed, Sep 27, 2017 at 1:56 PM, Douglas Anderson wrote: > This attempts to instill a bit of paranoia to the code dealing with > the CTO timer. It's believed that this will make the CTO timer more > robust in the case that we're having very long interrupt latencies. >

Re: [PATCH 4.9 00/64] 4.9.53-stable review

On 10/03/2017 06:22 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.53 release. > There are 64 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 know. > > Responses

Re: [patch V2 22/29] lockup_detector: Make watchdog_nmi_reconfigure() two stage

On Tue, 3 Oct 2017, Thomas Gleixner wrote: > On Tue, 3 Oct 2017, Thomas Gleixner wrote: > > On Tue, 3 Oct 2017, Michael Ellerman wrote: > > > Hmm, I tried that patch, it makes the warning go away. But then I > > > triggered a deliberate hard lockup and got nothing. > > > > > > Then I went back to

[PATCH] nfp: convert nfp_eth_set_bit_config() into a macro

nfp_eth_set_bit_config() is marked as __always_inline to allow gcc to identify the 'mask' parameter as known to be constant at compile time, which is required to use the FIELD_GET() macro. The forced inlining does the trick for gcc, but for kernel builds with clang it results in undefined

Re: [RFC 2/5] fs: freeze on suspend and thaw on resume

On Tue, 3 Oct 2017, Luis R. Rodriguez wrote: > This uses the existing filesystem freeze and thaw callbacks to > freeze each filesystem on suspend/hibernation and thaw upon resume. > > This is needed so that we properly really stop IO in flight without > races after userspace has been frozen.

Re: [RFC 5/5] pm: remove kernel thread freezing

On Tue 2017-10-03 11:53:13, Luis R. Rodriguez wrote: > Now that all filesystems which used to rely on kthread > freezing have been converted to filesystem freeze/thawing > we can remove the kernel kthread freezer. Are you surely-sure? You mentioned other in kernel sources of writes; what about

[PATCH 0/4] ARM-OMAP: Adjustments for three function implementations

From: Markus Elfring Date: Tue, 3 Oct 2017 22:04:22 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Delete an error message for a failed memory allocation in two functions Improve a size

[PATCH 4/4] ARM: OMAP: Fix typos in two comment lines in _omap_dm_timer_request()

From: Markus Elfring Date: Tue, 3 Oct 2017 21:24:00 +0200 Adjust three words in this description. Signed-off-by: Markus Elfring --- arch/arm/plat-omap/dmtimer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [f2fs-dev] [PATCH v4] f2fs: introduce discard_granularity sysfs entry

On 10/04, Ju Hyung Park wrote: > Hi Chao. > > Yep, that patch seems to have fixed it. > Doing "while true; do fstrim -v /; done" while "rm -rf"ing a 2GB > kbuild directory > (with lots of small .o files and stuff) ended flawlessly. > > I hope to see this patch merged with next 4.14 merge cycle.

Re: [RFC 5/5] pm: remove kernel thread freezing

On Tue, 3 Oct 2017, Bart Van Assche wrote: > What about the many drivers outside filesystems that use the > set_freezable() / try_to_freeze() / wait_event_freezable() API? Many/most of them are just completely bogus and pointless. I've killed a lot of those in the past, but the copy/paste

Re: [PATCH 1/6] f2fs: support issuing/waiting discard in range

On 09/19, Chao Yu wrote: > From: Chao Yu > > Fstrim intends to trim invalid blocks of filesystem only with specified > range and granularity, but actually, it will issue all previous cached > discard commands which may be out-of-range and be with unmatched > granularity, it's

Re: [RFC 5/5] pm: remove kernel thread freezing

Hi! > > Can memory management doing background writes be a problem? > > This point I don't understand. What exactly do you mean? Hibernation: We freeze, do system snapshot, unfreeze, and write image to disk. Memory management wakes up (this used to be called bdflush), decides its time to write

Re: [RFC 5/5] pm: remove kernel thread freezing

On Tue, 2017-10-03 at 22:17 +0200, Jiri Kosina wrote: > On Tue, 3 Oct 2017, Bart Van Assche wrote: > > What about the many drivers outside filesystems that use the > > set_freezable() / try_to_freeze() / wait_event_freezable() API? > > Many/most of them are just completely bogus and pointless.

Re: Problems compiling with KCFLAGS="-frecord-gcc-switches"

On Tue, Oct 03, 2017 at 01:00:23PM -0500, Josh Poimboeuf wrote: > On Tue, Oct 03, 2017 at 10:54:57AM -0700, Guenter Roeck wrote: > > Hi Josh, > > > > On Fri, Sep 29, 2017 at 03:46:09PM -0500, Josh Poimboeuf wrote: > > > On Fri, Sep 29, 2017 at 01:00:56PM -0700, Guenter Roeck wrote: > > > > Hi

Re: [RFC 5/5] pm: remove kernel thread freezing

On Tue, Oct 03, 2017 at 08:21:42PM +, Bart Van Assche wrote: > On Tue, 2017-10-03 at 22:17 +0200, Jiri Kosina wrote: > > On Tue, 3 Oct 2017, Bart Van Assche wrote: > > > What about the many drivers outside filesystems that use the > > > set_freezable() / try_to_freeze() /

Re: [PATCH v9 12/12] mm: stop zeroing memory during allocation in vmemmap

Hi Michal, I decided not to merge these two patches, because in addition to sparc optimization move, we have this dependancies: mm: zero reserved and unavailable struct pages must be before mm: stop zeroing memory during allocation in vmemmap. Otherwise, we can end-up with struct pages

[PATCH] Staging: rtl8188eu: core: Use list_for_each_entry_safe

Use list_for_each_entry_safe when the list elements may get deleted during traversal. Done using the following semantic patch by coccinelle. @r@ struct list_head* l; expression e; identifier m, list_del_init, f; type T1; T1* pos; iterator name list_for_each_entry_safe; @@ f(...){ +T1* tmp; ...

RE: [PATCH 02/11] x86: make dma_cache_sync a no-op

On Tue, 3 Oct 2017, David Laight wrote: > From: Christoph Hellwig > > Sent: 03 October 2017 11:43 > > x86 does not implement DMA_ATTR_NON_CONSISTENT allocations, so it doesn't > > make any sense to do any work in dma_cache_sync given that it must be a > > no-op when dma_alloc_attrs returns

Re: [RFC 5/5] pm: remove kernel thread freezing

On Tue, 3 Oct 2017, Pavel Machek wrote: > > This point I don't understand. What exactly do you mean? > > Hibernation: > > We freeze, do system snapshot, unfreeze, and write image to > disk. Where/why do you unfreeze between creating the snapshot and writing it out? Again, I agree that the

Re: [RFC 2/5] fs: freeze on suspend and thaw on resume

On Tue, Oct 03, 2017 at 08:32:39PM +, Bart Van Assche wrote: > On Tue, 2017-10-03 at 22:23 +0200, Luis R. Rodriguez wrote: > > On Tue, Oct 03, 2017 at 08:02:22PM +, Bart Van Assche wrote: > > > On Tue, 2017-10-03 at 11:53 -0700, Luis R. Rodriguez wrote: > > > > +static bool

Re: [RFC 0/5] fs: replace kthread freezing with filesystem freeze/thaw

On Tue, Oct 03, 2017 at 10:05:11PM +0200, Luis R. Rodriguez wrote: > On Wed, Oct 04, 2017 at 03:33:01AM +0800, Ming Lei wrote: > > On Tue, Oct 03, 2017 at 11:53:08AM -0700, Luis R. Rodriguez wrote: > > > INFO: task kworker/u8:8:1320 blocked for more than 10 seconds. > > > Tainted: G

Re: [RFC 5/5] pm: remove kernel thread freezing

On Tue, 3 Oct 2017, Pavel Machek wrote: > > Again, I agree that the (rare) kthreads that are actually "creating" new > > I/O have to be somehow frozen and require special care. > > Agreed. Was any effort made to identify those special kernel threads? I don't think there is any other way than

[PATCH] arm64: Enforce endianness build flags for LD and AS

If LD or AS is specified on the command line using "make LD=", the endianness flag will not be added. Depending on the toolchain used, this can result in endianness mismatch errors, such as aarch64-cros-linux-gnu/binutils-bin/2.27.0/ld.bfd.real: arch/arm64/crypto/.tmp_aes-ce-cipher.o:

Re: [RFC 2/5] fs: freeze on suspend and thaw on resume

On Tue, Oct 03, 2017 at 11:53:10AM -0700, Luis R. Rodriguez wrote: > This uses the existing filesystem freeze and thaw callbacks to > freeze each filesystem on suspend/hibernation and thaw upon resume. > > This is needed so that we properly really stop IO in flight without > races after userspace

Re: [PATCH] arm64: Enforce endianness build flags for LD and AS

Hi, On Tue, Oct 3, 2017 at 1:58 PM, Guenter Roeck wrote: > If LD or AS is specified on the command line using "make LD=", > the endianness flag will not be added. Depending on the toolchain used, > this can result in endianness mismatch errors, such as > >

Re: [PATCH] Documentation: Improve softlockup_panic= description text

On Tue, 3 Oct 2017 22:54:29 +0200 Borislav Petkov wrote: > non-zero yap, I was looking for that version but somehow it evaded > me. Can you change it while applying or should I send a new one? Man that's a lot of work...much easier to just whine about it on the mailing

Re: [RFC 5/5] pm: remove kernel thread freezing

On Tue, Oct 03, 2017 at 03:09:53PM -0600, Shuah Khan wrote: > On Tue, Oct 3, 2017 at 3:00 PM, Jiri Kosina wrote: > > On Tue, 3 Oct 2017, Pavel Machek wrote: > > > >> > Again, I agree that the (rare) kthreads that are actually "creating" new > >> > I/O have to be somehow frozen

Re: [RFC 5/5] pm: remove kernel thread freezing

On Tuesday, October 3, 2017 8:59:00 PM CEST Rafael J. Wysocki wrote: > On Tuesday, October 3, 2017 8:53:13 PM CEST Luis R. Rodriguez wrote: > > Now that all filesystems which used to rely on kthread > > freezing have been converted to filesystem freeze/thawing > > we can remove the kernel kthread

Re: [PATCH v2 2/2] dt-bindings: arm: amlogic: Add Tronsmart Vega S96 binding

On Tue, Oct 03, 2017 at 05:29:45PM +0200, Neil Armstrong wrote: > Cc: supp...@tronsmart.com > Acked-by: Jerome Brunet > Signed-off-by: Oleg Ivanov > Signed-off-by: Neil Armstrong > --- >

Re: [PATCH v9 6/7] dt-bindings: clock: Document qcom,apcs binding

On Thu, Sep 21, 2017 at 07:49:39PM +0300, Georgi Djakov wrote: > Add device-tree binding documentation for the Qualcom APCS clock > controller. This clock controller is a mux and half-integer divider > and provides the clock for the application CPU. > > Signed-off-by: Georgi Djakov

  1   2   3   4   5   6   7   8   9   10   >