Re: [v6 PATCH 10/21] x86/insn-eval: Do not use R/EBP as base if mod in ModRM is zero

On Tue, Mar 07, 2017 at 04:32:43PM -0800, Ricardo Neri wrote: > Section 2.2.1.3 of the Intel 64 and IA-32 Architectures Software > Developer's Manual volume 2A states that when the mod part of the ModRM > byte is zero and R/EBP is specified in the R/M part of such bit, the value > of the

[PATCH] exofs: ORE: remove dead dependence

Remove last reference on PNFS_OBJLAYOUT. Signed-off-by: Valentin Rothberg --- fs/exofs/Kconfig.ore | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/exofs/Kconfig.ore b/fs/exofs/Kconfig.ore index 2daf2329c28d..73cab8d92dfd 100644 ---

Re: Review request: draft ioctl_userfaultfd(2) manual page

Hello Michael, On Fri, Apr 21, 2017 at 11:11:18AM +0200, Michael Kerrisk (man-pages) wrote: > Hello Mike, > Hello Andrea (we need your help!), > > On 03/22/2017 02:54 PM, Mike Rapoport wrote: > > Hello Michael, > > > > On Mon, Mar 20, 2017 at 09:11:07PM +0100, Michael Kerrisk (man-pages) wrote:

[PATCH] power: supply: generic-adc-battery: use SIMPLE_DEV_PM_OPS helper macro

Replace ifdefs with SIMPLE_DEV_PM_OPS helper macro. Signed-off-by: Rahul Bedarkar --- drivers/power/supply/generic-adc-battery.c | 17 - 1 file changed, 4 insertions(+), 13 deletions(-) diff --git a/drivers/power/supply/generic-adc-battery.c

Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

On Fri, Apr 21, 2017 at 11:50:18AM +0200, Gerd Hoffmann wrote: > On Fr, 2017-04-21 at 12:25 +0300, Ville Syrjälä wrote: > > On Fri, Apr 21, 2017 at 09:58:24AM +0200, Gerd Hoffmann wrote: > > > While working on graphics support for virtual machines on ppc64 (which > > > exists in both little and

Re: [PATCH] exofs: ORE: remove dead dependence

On Fri, Apr 21, 2017 at 01:00:53PM +0200, Valentin Rothberg wrote: > Remove last reference on PNFS_OBJLAYOUT. > > Signed-off-by: Valentin Rothberg Looks good, Reviewed-by: Christoph Hellwig

Re: [PATCH 03/11] blk: use non-rescuing bioset for q->bio_split.

Looks fine: Reviewed-by: Christoph Hellwig

Re: [PATCH 02/11] blk: make the bioset rescue_workqueue optional.

On Thu, Apr 20, 2017 at 03:38:48PM +1000, NeilBrown wrote: > This patch converts bioset_create() and > bioset_create_nobvec() to not create a workqueue so > alloctions will never trigger punt_bios_to_rescuer(). It > also introduces bioset_create_rescued() and > bioset_create_nobvec_rescued()

Re: [PATCH 09/11] bcache: use kmalloc to allocate bio in bch_data_verify()

On Thu, Apr 20, 2017 at 03:38:50PM +1000, NeilBrown wrote: > This function allocates a bio, then a collection > of pages. It copes with failure. > > It currently uses a mempool() to allocate the bio, > but alloc_page() to allocate the pages. These fail > in different ways, so the usage is

Re: [PATCH 11/11] block: don't check for BIO_MAX_PAGES in blk_bio_segment_split()

On Thu, Apr 20, 2017 at 03:38:50PM +1000, NeilBrown wrote: > blk_bio_segment_split() makes sure bios have no more than > BIO_MAX_PAGES entries in the bi_io_vec. > This was done because bio_clone_bioset() (when given a > mempool bioset) could not handle larger io_vecs. > > No driver uses

Re: [regression v4.11] 617f01211baf ("8139too: use napi_complete_done()")

BTW I've also been getting some lockdep grief from r8169 netpoll stuff recently. Not sure if it might be related to these changes or not, but I don't remember seeing this sort of stuff until quite recently. [ 251.911044] == [ 251.911044] [

Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

On Fri, 21 Apr 2017 14:08:04 +0300 Ville Syrjälä wrote: > On Fri, Apr 21, 2017 at 11:50:18AM +0200, Gerd Hoffmann wrote: > > On Fr, 2017-04-21 at 12:25 +0300, Ville Syrjälä wrote: > > > On Fri, Apr 21, 2017 at 09:58:24AM +0200, Gerd Hoffmann wrote: > > > >

Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

Hi, > > I personally find "native" more intuitive, but at the end of the day I > > don't mind much. If people prefer "host" over "native" I'll change it. > > "native" to me feels more like "native to the GPU" since these things > really are tied to the GPU not the CPU. Ok, then maybe "host"

[PATCH] ARM: at91/at91-pinctrl documentation: fix spelling mistake: "contoller" -> "controller"

From: Colin Ian King trivial fix to spelling mistake in documentation Signed-off-by: Colin Ian King --- Documentation/devicetree/bindings/pinctrl/atmel,at91-pinctrl.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 09/13] mm: __first_valid_page skip over offline pages

From: Michal Hocko __first_valid_page skips over invalid pfns in the range but it might still stumble over offline pages. At least start_isolate_page_range will mark those set_migratetype_isolate. This doesn't represent any immediate AFAICS because alloc_contig_range will fail

[PATCH] scsi: sas: move scsi_remove_host call into sas_remove_host

Move scsi_remove_host call into sas_remove_host and remove it from SAS HBA drivers, so we don't mess up the ordering. This solves an issue with double deleting sysfs entries that was introduced by the change of sysfs behaviour from commit bcdde7e ("sysfs: make __sysfs_remove_dir() recursive").

Re: [PATCH v17 2/3] usb: USB Type-C connector class

Hi, On Thu, Apr 20, 2017 at 12:46:59PM -0700, Badhri Jagan Sridharan wrote: > Thanks for the responses :) > > So seems like we have a plan. > > In Type-C connector class the checks for TYPEC_PWR_MODE_PD > and pd_revision for both the port and the partner will be removed in > power_role_store

[PATCH] scripts/spelling.txt: add several more common spelling mistakes

From: Colin Ian King Here are some of the more common spelling mistakes that I've found while fixing up spelling mistakes in kernel error message text. They probably should be added to this list so we don't keep on seeing them appearing again. Signed-off-by: Colin Ian

Re: [PATCH v3] clk/axs10x: introduce AXS10X pll driver

Hi Vlad, On 21-04-2017 12:45, Vlad Zakharov wrote: > AXS10X boards manages it's clocks using various PLLs. These PLL has same > dividers and corresponding control registers mapped to different addresses. > So we add one common driver for such PLLs. > > Each PLL on AXS10X board consist of three

Re: fsl_ifc_nand: are blank pages protected by ECC?

Pavel, Am 21.04.2017 um 12:08 schrieb Pavel Machek: > (BTW, switching to ecc.mode = ECC_SOFT will cause compatibility > problems but should make the problem go away, right?) Yes and it is slow. So, fixing the driver is the way to go. :-) Thanks, //richard

Re: [PATCH 3.18 000/124] 3.18.50-stable review

On Fri, Apr 21, 2017 at 09:17:51AM +0200, Greg Kroah-Hartman wrote: > On Thu, Apr 20, 2017 at 01:37:56PM -0700, kernelci.org bot wrote: > > stable-rc/linux-3.18.y boot: 283 boots: 3 failed, 262 passed with 18 > > offline (v3.18.49-125-g7379419992fb) > Yeah, thanks for adding 3.18 back to the

Re: [PATCH v3] Staging: most: use __func__ instead of the function name

On Fri, 2017-04-21 at 00:40 -0700, Chandra Annamaneni wrote: > Third Reminder. Please review. Patience. > On Sun, 9 Apr 2017, chandrasekhar annamaneni wrote: > > Second reminder, please review. [] > > On Fri, Mar 17, 2017 at 12:49 PM, Chandra Annamaneni > > wrote: > > > >

Re: [PATCH 1/2 v3 resend] video: fbdev: imxfb: support AUS mode

Thus wrote Bartlomiej Zolnierkiewicz (b.zolnier...@samsung.com): > It hadn't been lost, I've been waiting on v4, please see: > https://lkml.org/lkml/2017/3/15/709 > [ Rob has requested rename of the property to "fsl,aus-mode". ] Sorry, I didn't notice that Rob wanted me to rename the property.

Re: [PATCH 3/4] nfs: remove the objlayout driver

On Fri, Apr 21, 2017 at 09:27:11AM +0200, Valentin Rothberg wrote: > Hi Christoph, > > I just came across this patch in linux-next commit 6d22323b2e9f. > scripts/checkkconfigsymbols.py reports that there is a leftover > reference on PNFS_OBJLAYOUT in fs/exofs/Kconfig.ore line 10 (depends > on

RE: [PATCH 0/5] v2: block subsystem refcounter conversions

> Hi Elena, > > On Thu, Apr 20, 2017 at 04:10:16PM +, Reshetova, Elena wrote: > > > > > All the objections from DaveM on the amount of cycles spent on the > > > new refcount_t apply to the block layer fast path operations as well. > > > > Ok, could you please indicate the correct way to

Re: [PATCH 0/5] v2: block subsystem refcounter conversions

On Thu, Apr 20, 2017 at 11:33:19AM -0700, Eric Biggers wrote: > Like I suggested months ago, how about doing an efficient implementation of > refcount_t which doesn't use the bloated cmpxchg loop? Then there would be no > need for endless performance arguments. In fact, in PaX there are already

[GIT PULL] ACPI fix for final v4.11

Hi Linus, Please pull from the tag git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.11-final with top-most commit fe8c470ab87d90e4b5115902dd94eced7e3305c3 ACPI / power: Avoid maybe-uninitialized warning on top of commit 4f7d029b9bf009fbee76bb10c0c4351a1870d2f3

Re: [PATCH v6 2/3] v4l: Add 10/16-bits per channel YUV pixel formats

On 04/18/2017 03:33 AM, Mauro Carvalho Chehab wrote: Em Sun, 5 Mar 2017 18:00:32 +0800 Randy Li escreveu: The formats added by this patch are: V4L2_PIX_FMT_P010 V4L2_PIX_FMT_P010M V4L2_PIX_FMT_P016 V4L2_PIX_FMT_P016M Currently, none of

Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

On Fri, Apr 21, 2017 at 11:50:18AM +0200, Gerd Hoffmann wrote: > On Fr, 2017-04-21 at 12:25 +0300, Ville Syrjälä wrote: > > On Fri, Apr 21, 2017 at 09:58:24AM +0200, Gerd Hoffmann wrote: > > > While working on graphics support for virtual machines on ppc64 (which > > > exists in both little and

Re: Review request: draft userfaultfd(2) manual page

On Fri, Apr 21, 2017 at 08:30:55AM +0200, Michael Kerrisk (man-pages) wrote: > Hello Mike, > > On 03/21/2017 03:01 PM, Mike Rapoport wrote: > > Hello Michael, > > > > On Mon, Mar 20, 2017 at 09:08:05PM +0100, Michael Kerrisk (man-pages) wrote: > >> Hello Andrea, Mike, and all, > >> > >> Mike:

Re: [PATCH v2 0/5] Re-order scsi_remove_host and sas_remove_host in SAS HBA LLDDs

On Fri, Apr 21, 2017 at 10:04:45AM +0200, Johannes Thumshirn wrote: > This series re-orders the calls to scsi_remove_host() and sas_remove_host() in > all SAS HBA drivers (apart from mpt3sas which is doing it correctly). This is > for two reasons: > 1) After the change to recursive removal

Re: [PATCH v2 0/5] Re-order scsi_remove_host and sas_remove_host in SAS HBA LLDDs

On Fri, Apr 21, 2017 at 09:57:37AM +0100, John Garry wrote: > On 21/04/2017 09:39, Johannes Thumshirn wrote: >>> wangyijing already sent an RFC for fixing this issue (mentioned above), >>> > which was a signifiagnt rewrite of some of libsas. >>> > I am hoping that he would retry, and that

Re: Review request: draft userfaultfd(2) manual page

Hello Mike, On 04/21/2017 01:06 PM, Mike Rapoport wrote: > On Fri, Apr 21, 2017 at 08:30:55AM +0200, Michael Kerrisk (man-pages) wrote: >> Hello Mike, >> >> On 03/21/2017 03:01 PM, Mike Rapoport wrote: >>> Hello Michael, >>> >>> On Mon, Mar 20, 2017 at 09:08:05PM +0100, Michael Kerrisk

Re: [PATCH 05/11] rbd: use bio_clone_fast() instead of bio_clone()

Looks fine, Reviewed-by: Christoph Hellwig

Re: [PATCH 09/11] bcache: use kmalloc to allocate bio in bch_data_verify()

Looks fine, Reviewed-by: Christoph Hellwig

Re: [PATCH 06/11] drbd: use bio_clone_fast() instead of bio_clone()

On Thu, Apr 20, 2017 at 03:38:49PM +1000, NeilBrown wrote: > drbd does not modify the bi_io_vec of the cloned bio, > so there is no need to clone that part. So bio_clone_fast() > is the better choice. > For bio_clone_fast() we need to specify a bio_set. > We could use fs_bio_set, which

Re: [PATCH 08/11] xen-blkfront: remove bio splitting.

Btw, I really don't understand why this code even looks at bios over just requeueing the request. Can someone explain that bit to me?

[PATCH 03/13] mm: drop page_initialized check from get_nid_for_pfn

From: Michal Hocko c04fc586c1a4 ("mm: show node to memory section relationship with symlinks in sysfs") has added means to export memblock<->node association into the sysfs. It has also introduced get_nid_for_pfn which is a rather confusing counterpart of pfn_to_nid which checks

[PATCH 02/13] mm, memory_hotplug: use node instead of zone in can_online_high_movable

From: Michal Hocko the primary purpose of this helper is to query the node state so use the node id directly. This is a preparatory patch for later changes. This shouldn't introduce any functional change Acked-by: Vlastimil Babka Reviewed-by: Yasuaki Ishimatsu

[PATCH 01/13] mm: remove return value from init_currently_empty_zone

From: Michal Hocko init_currently_empty_zone doesn't have any error to return yet it is still an int and callers try to be defensive and try to handle potential error. Remove this nonsense and simplify all callers. This patch shouldn't have any visible effect Acked-by: Balbir

[PATCH -v3 0/13] mm: make movable onlining suck less

Hi, The last version of this series has been posted here [1]. It has seen some more testing (thanks to Reza Arbab and Igor Mammedov[2]), Jerome's and Vlastimil's review resulted in few fixes mostly folded in their respected patches. There are 4 more patches (patch 6+ in this series). I have

[PATCH 04/13] mm, memory_hotplug: get rid of is_zone_device_section

From: Michal Hocko device memory hotplug hooks into regular memory hotplug only half way. It needs memory sections to track struct pages but there is no need/desire to associate those sections with memory blocks and export them to the userspace via sysfs because they cannot be

[PATCH 07/13] mm: consider zone which is not fully populated to have holes

From: Michal Hocko __pageblock_pfn_to_page has two users currently, set_zone_contiguous which checks whether the given zone contains holes and pageblock_pfn_to_page which then carefully returns a first valid page from the given pfn range for the given zone. This doesn't handle

[PATCH 08/13] mm, compaction: skip over holes in __reset_isolation_suitable

From: Michal Hocko __reset_isolation_suitable walks the whole zone pfn range and it tries to jump over holes by checking the zone for each page. It might still stumble over offline pages, though. Skip those by checking PageReserved. Signed-off-by: Michal Hocko

Re: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI

On Fri 2017-04-21 10:57:25, Sergey Senozhatsky wrote: > On (04/20/17 15:11), Petr Mladek wrote: > [..] > > void printk_nmi_enter(void) > > { > > - this_cpu_or(printk_context, PRINTK_NMI_CONTEXT_MASK); > > + /* > > +* The size of the extra per-CPU buffer is limited. Use it > > +* only

[PATCH 06/13] mm, memory_hotplug: consider offline memblocks removable

From: Michal Hocko is_pageblock_removable_nolock relies on having zone association to examine all the page blocks to check whether they are movable or free. This is just wasting of cycles when the memblock is offline. Later patch in the series will also change the time when the

[PATCH 05/13] mm, memory_hotplug: split up register_one_node

From: Michal Hocko Memory hotplug (add_memory_resource) has to reinitialize node infrastructure if the node is offline (one which went through the complete add_memory(); remove_memory() cycle). That involves node registration to the kobj infrastructure (register_node), the

[PATCH v2] tools/iio: Use include/uapi with __EXPORTED_HEADERS__

Use the local uapi headers to keep in sync with "recently" added enum values like IIO_UVINDEX. Build tested using: $ make -C tools/iio $ make -C /tools iio $ make -C /tools/iio This follows a strategy similar to that used by tools/hv, tools/net and tools/leds among others. Cc: Randy Dunlap

[PATCH v4 3/7] kprobes: validate the symbol name provided during probe registration

When a kprobe is being registered, we use the symbol_name field to lookup the address where the probe should be placed. Since this is a user-provided field, let's ensure that the length of the string is within expected limits. Signed-off-by: Naveen N. Rao ---

[PATCH v4 4/7] powerpc/kprobes: Use safer string functions in kprobe_lookup_name()

Convert usage of strchr()/strncpy()/strncat() to strnchr()/memcpy()/strlcat() for simpler and safer string manipulation. Reported-by: David Laight Signed-off-by: Naveen N. Rao --- Changes: Additionally convert the strchr().

Re: Unchecked flags in statx(2) [Should be fixed before 4.11-final?]

David Howells wrote: > > Similarly, there appears to be no check for invalid flags in the > > 'flags' argument of statx(). Why is there also not such a check > > there? > > Like this? > > if (mask & STATX__RESERVED) > return -EINVAL; Sorry, I misread.

Re: [PATCH v2 08/17] fs: retrofit old error reporting API onto new infrastructure

On Tue, 2017-04-18 at 08:56 +1000, NeilBrown wrote: > On Wed, Apr 12 2017, Jeff Layton wrote: > > > On Thu, 2017-04-13 at 08:14 +1000, NeilBrown wrote: > > > > > > I suspect that the filemap_check_wb_error() will need to be moved > > > into some parent of the current call site, which is

[PATCH 1/2] gpio: move tca9554 from pcf857x to pca953x

The TCA9554 doesn't work with the pcf857x driver, trying to change the direction gives a NAK bailout error. TCA9554 is similar to the PCA9554, thus change the driver. Signed-off-by: Anders Darander --- drivers/gpio/Kconfig| 2 +- drivers/gpio/gpio-pca953x.c | 1 +

[PATCH 2/2] gpio: DT bindings, move tca9554 from pcf857x to pca953x

The TCA9554 is similar to the PCA9554. Update the DT binding docs. Signed-off-by: Anders Darander --- Documentation/devicetree/bindings/gpio/gpio-pca953x.txt | 1 + Documentation/devicetree/bindings/gpio/gpio-pcf857x.txt | 1 - 2 files changed, 1 insertion(+), 1

Re: [stable 3.18 PATCH] clk: at91: usb: fix determine_rate prototype again

On Fri, 21 Apr 2017 14:45:23 +0200 Arnd Bergmann wrote: > We had an incorrect backport of > 4591243102fa ("clk: at91: usb: propagate rate modification to the parent clk") > that was fixed incorrectly in linux-3.18.y by > 76723e7ed589 ("clk: at91: usb: fix determine_rate

Re: [PATCH 10/13] mm, memory_hotplug: do not associate hotadded memory to zones until online

In case you were wondering about the weird sorting. git send-email has failed while at patch10 so I had to repost it and so the patch is out of order. It should be still applied as 10th patch. -- Michal Hocko SUSE Labs

[PATCH] usb: dwc3: gadget: Fix ISO transfer performance

Commit 08a36b543803 ("usb: dwc3: gadget: simplify __dwc3_gadget_ep_queue()") caused a small change in the way ISO transfer is handled in the case when XferInProgress event happens on Isoc EP with an active transfer. This caused a performance degradation of 50%. e.g. using g_webcam on DUT and

[PATCH 2/5] extcon: Add FUSB302 USB TYPE-C controller support

Add support for USB TYPE-C cable detection on systems using a FUSB302 USB TYPE-C controller. Signed-off-by: Hans de Goede --- drivers/extcon/Kconfig | 8 + drivers/extcon/Makefile | 1 + drivers/extcon/extcon-fusb302.c | 782

[PATCH 4/5] extcon: intel-cht-wc: Add new cht_wc_extcon_set_state helper

This allows a nice cleanup of cht_wc_extcon_pwrsrc_event, getting rid of all the gotos in there. This also is a preparation patch for adding USB Type-C controller monitoring. Signed-off-by: Hans de Goede --- drivers/extcon/extcon-intel-cht-wc.c | 54

[PATCH 5/5] extcon: intel-cht-wc: Add support for monitoring external USB Type-C controller

On some boards the Whiskey Cove PMIC is combined with an external USB Type-C controller, in this case extcon consumers should use the Type-C extcon state, except when the USB Type-C controller detects a current limit of 500 mA which may indicate USB-C to USB-A cable at which point the extcon

[PATCH 3/5] extcon: intel-cht-wc: Default to SDP on regmap io errors

In the theoretical case of regmap_read failing get_charger would return an error and we would continue with EXTCON_NONE. Since we've already seen Vbus at this point, we should really set some other cable value to avoid other drivers enabling the 5V boost converter on the OTG port, even though

[PATCH v2 2/3] powerpc/mm: Fix kernel RAM protection after freeing unused memory on PPC32

As seen below, allthough the init sections have been freed, the associated memory area is still marked as executable in the page tables. ~ dmesg [5.860093] Freeing unused kernel memory: 592K (c057 - c0604000) ~ cat /sys/kernel/debug/kernel_page_tables ---[ Start of kernel VM ]---

[PATCH 1/5] extcon: Allow extcon drivers to specify the extcon name

The parent device name is not necessarily always useful, e.g. with i2c devices it may simply be e.g.: "0-0022" and it also depends on the i2c-bus number which depends on probe ordering. This commit allows drivers to set their own, more useful name, avoiding the problems with some i2c-device

[PATCH v2 0/3] powerpc/mm: Fix kernel protection and implement CONFIG_DEBUG_RODATA on PPC32

This patch set implements CONFIG_DEBUG_RODATA on Powerpc32 after fixing a few issues related to kernel code page protection. Changes in v2: Instead of making the entire kernel RW to patch code in ftrace, we now only change the rights on the page to be modified Christophe Leroy (3):

[PATCH 1/2] ASoC: codec: wm9860: avoid maybe-uninitialized warning

The new PLL configuration code triggers a harmless warning: sound/soc/codecs/wm8960.c: In function 'wm8960_configure_clocking': sound/soc/codecs/wm8960.c:735:3: error: 'best_freq_out' may be used uninitialized in this function [-Werror=maybe-uninitialized] wm8960_set_pll(codec, freq_in,

[PATCH 0/2] Relax bitclk computation when using PLL

Using strict bitclk requirements we cannot support all promised rates and formats. For this reason we relax bitclk computation by choosing the best available bitclk. First patch in the series is based on Arnd's patch: http://mailman.alsa-project.org/pipermail/alsa-devel/2017-April/119899.html

[PATCH 2/2] ASoC: codec: wm8960: Relax bit clock computation when using PLL

Bitclk is derived from sysclk using bclk_divs. Sysclk can be derived in two ways: (1) directly from MLCK (2) MCLK via PLL Commit 3c01b9ee2ab9d0d ("ASoC: codec: wm8960: Relax bit clock computation") relaxed bitclk computation when sysclk is directly derived from MCLK. Lets do the

[PATCH v4 net-next] mdio_bus: Issue GPIO RESET to PHYs.

Some boards [1] leave the PHYs at an invalid state during system power-up or reset thus causing unreliability issues with the PHY which manifests as PHY not being detected or link not functional. To fix this, these PHYs need to be RESET via a GPIO connected to the PHY's RESET pin. Some boards

Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

Adding Harry to this mail thread as well, cause is one of the people really affected by this. Christian. Am 21.04.2017 um 15:21 schrieb Christian König: Am 21.04.2017 um 15:12 schrieb Gerd Hoffmann: Hi, "native" to me feels more like "native to the GPU" since these things really are

Re: [PATCH] kvm: pass the virtual SEI syndrome to guest OS

Hi all/Laszlo, sorry, I have a question to consult with you. On 2017/4/7 2:55, Laszlo Ersek wrote: > On 04/06/17 14:35, gengdongjiu wrote: >> Dear, Laszlo >>Thanks for your detailed explanation. >> >> On 2017/3/29 19:58, Laszlo Ersek wrote: >>> (This ought to be one of the longest address

Re: [PATCH v4 4/7] powerpc/kprobes: Use safer string functions in kprobe_lookup_name()

On 04/21/2017 07:33 AM, Naveen N. Rao wrote: > Convert usage of strchr()/strncpy()/strncat() to > strnchr()/memcpy()/strlcat() for simpler and safer string manipulation. > > Reported-by: David Laight > Signed-off-by: Naveen N. Rao > ---

Re: [PATCH v2 3/3] powerpc/mm: Implement CONFIG_DEBUG_RODATA on PPC32

Excerpts from Christophe Leroy's message of April 21, 2017 18:32: This patch implements CONFIG_DEBUG_RODATA on PPC32. As for CONFIG_DEBUG_PAGEALLOC, it deactivates BAT and LTLB mappings in order to allow page protection setup at the level of each page. As BAT/LTLB mappings are deactivated,

Re: [PATCH] sched/deadline: fix switching to -deadline

On Fri, 21 Apr 2017 11:54:21 +0200 luca abeni wrote: > On Fri, 21 Apr 2017 11:42:40 +0200 > luca abeni wrote: > [...] > > > > diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c > > > > index a2ce590..ec53d24 100644 > > > > ---

Re: fsl_ifc_nand: are blank pages protected by ECC?

On Fri, 21 Apr 2017 15:37:21 +0200 Pavel Machek wrote: > Hi! > > > (Added driver author to the cc list, maybe he can help). > > > > > UBIFS complains: > > > > > > > > UBIFS error (pid 931): ubifs_scan: corrupt empty space at LEB 282:252630 > > > > UBIFS error (pid 931):

Re: [RFC][PATCH] selftests: ftrace: Allow some tests to be run in a tracing instance

On Fri, 21 Apr 2017 19:00:25 +0900 Masami Hiramatsu wrote: > On Fri, 21 Apr 2017 18:36:17 +0900 > Masami Hiramatsu wrote: > > > On Thu, 20 Apr 2017 13:30:34 -0400 > > Steven Rostedt wrote: > > > > > > An tracing instance has

[PATCH 1/2] nohz: Fix again collision between tick and other hrtimers

(This restores commit 24b91e360ef521a2808771633d76ebc68bd5604b that got reverted by commit 558e8e27e73f53f8a512485be538b07115fe5f3c due to a regression where CPUs spuriously stopped ticking. The issue happened when a tick fired too early past its expected expiration: on IRQ exit the tick was

[PATCH 2/2] tick: Make sure tick timer is active when bypassing reprogramming

So far we have run into too much troubles with the optimization path that skips reprogramming the clock on IRQ exit when the expiration deadline hasn't changed. If by accident the cached deadline happens to be out of sync with the hardware deadline, the buggy result and its cause are hard to

[PATCH 0/2] nohz: Deal with clock reprogram skipping issues v2

As suggested by Thomas Gleixner, the second patch now integrates a fix in case the sanity check fails and the clockevent isn't programmed as expected. Frederic Weisbecker (2): nohz: Fix again collision between tick and other hrtimers tick: Make sure tick timer is active when bypassing

[RFC PATCH 07/14] cgroup: Move debug cgroup to its own file

The debug cgroup currently resides within cgroup-v1.c and is enabled only for v1 cgroup. To enable the debug cgroup also for v2, it makes sense to put the code into its own file as it will no longer be v1 specific. The only change in this patch is the expansion of cgroup_task_count() within the

[RFC PATCH 08/14] cgroup: Keep accurate count of tasks in each css_set

The reference count in the css_set data structure was used as a proxy of the number of tasks attached to that css_set. However, that count is actually not an accurate measure especially with thread mode support. So a new variable task_count is added to the css_set to keep track of the actual task

[RFC PATCH 10/14] cgroup: Implement new thread mode semantics

The current thread mode semantics aren't sufficient to fully support threaded controllers like cpu. The main problem is that when thread mode is enabled at root (mainly for performance reason), all the non-threaded controllers cannot be supported at all. To alleviate this problem, the roles of

[RFC PATCH 02/14] cgroup: add @flags to css_task_iter_start() and implement CSS_TASK_ITER_PROCS

From: Tejun Heo css_task_iter currently always walks all tasks. With the scheduled cgroup v2 thread support, the iterator would need to handle multiple types of iteration. As a preparation, add @flags to css_task_iter_start() and implement CSS_TASK_ITER_PROCS. If the flag is

[RFC PATCH 12/14] sched: Implement interface for cgroup unified hierarchy

From: Tejun Heo While the cpu controller doesn't have any functional problems, there are a couple interface issues which can be addressed in the v2 interface. * cpuacct being a separate controller. This separation is artificial and rather pointless as demonstrated by most

[RFC PATCH 13/14] sched: Make cpu/cpuacct threaded controllers

Make cpu and cpuacct cgroup controllers usable within a threaded cgroup. Signed-off-by: Waiman Long --- kernel/sched/core.c| 1 + kernel/sched/cpuacct.c | 1 + 2 files changed, 2 insertions(+) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 78dfcaa..9d8beda

[RFC PATCH 01/14] cgroup: reorganize cgroup.procs / task write path

From: Tejun Heo Currently, writes "cgroup.procs" and "cgroup.tasks" files are all handled by __cgroup_procs_write() on both v1 and v2. This patch reoragnizes the write path so that there are common helper functions that different write paths use. While this somewhat increases

Re: mtip32xx: add a status field to struct mtip_cmd

On 04/21/2017 08:06 AM, Colin Ian King wrote: > Hi, > > CoverityScan found an issue with the following part of the patch: > > - if (likely(!reserv)) > - blk_mq_complete_request(rq, -ENODEV); > - else if (test_bit(MTIP_PF_IC_ACTIVE_BIT, >port->flags)) { > + if

[PATCH v3 17/29] x86: head, annotate data appropriatelly

Use the new SYM_DATA_SIMPLE and SYM_DATA_END in both 32 and 64 bit heads. In the 64-bit version, define also SYM_DATA_START_PAGE_ALIGNED locally using the new SYM_START. It is used in the code instead of NEXT_PAGE() which was defined in this file and has been using the obsolete macro GLOBAL().

[PATCH] nfs/filelayout: fix NULL pointer dereference in fl_pnfs_update_layout()

Calling pnfs_put_lset on an IS_ERR pointer results in a NULL pointer dereference like the one below. fl_pnfs_update_layout()'s output is checked after each call so it doesn't seem that it should try to handle these errors on it's own. [ 3000.636161] BUG: unable to handle kernel NULL pointer

Re: [PATCH v13 03/10] mux: minimal mux subsystem and gpio-based mux controller

Hi Peter, On Thu, 2017-04-13 at 18:43 +0200, Peter Rosin wrote: [...] > +int mux_control_select(struct mux_control *mux, int state) state could be unsigned int for the consumer facing API. > +{ > + int ret; And mux_control_select should check that (0 <= state < mux->states). regards

Re: [PATCH] scsi: sas: move scsi_remove_host call into sas_remove_host

Looks good: Reviewed-by: Christoph Hellwig

Re: Unchecked flags in statx(2) [Should be fixed before 4.11-final?]

Michael Kerrisk (man-pages) wrote: > I was reading your statx(2) man page, and noticed this text: > >Do not simply set mask to UINT_MAX as one or more bits may, in the >future, be used to specify an extension to the buffer. > > (Here' 'mask' is the

Re: [PATCH 2/5] mtd: nand: gpmi: add i.MX 7 SoC support

On 04/21/2017 05:15 AM, Stefan Agner wrote: > On 2017-04-20 19:03, Marek Vasut wrote: >> On 04/21/2017 03:07 AM, Stefan Agner wrote: >>> Add support for i.MX 7 SoC. The i.MX 7 has a slightly different >>> clock architecture requiring only two clocks to be referenced. >>> The IP is slightly

Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

Hi, > > "native" to me feels more like "native to the GPU" since these things > > really are tied to the GPU not the CPU. That's also why I went with the > > explicit endianness originally so that the driver could properly declare > > what the GPU supports. > And to be honest I would really

Re: [PATCH 1/2] n2rng: Use devm_kcalloc() in n2rng_probe()

On Wed, Apr 19, 2017 at 11:10:07AM +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 19 Apr 2017 10:30:47 +0200 > > * A multiplication for the size determination of a memory allocation > indicated that an array data structure should be

Re: [PATCH v2 0/2] hwrng: mtk: add support for hardware random generator on MT7623 SoC

On Fri, Apr 21, 2017 at 12:24:24AM +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > This patchset introduces support for Mediatek hardware random generator (RNG) > Currently, the driver is already tested successfully with rng-tools on MT7623 > SoC. And it should

Re: [PATCH v2 0/3] uapi glibc compat: fix musl libc compatibility

On Fri, 2017-04-21 at 15:14 +0200, Hauke Mehrtens wrote: > > On 04/20/2017 10:36 PM, David Miller wrote: > > > > From: David Woodhouse > > Date: Thu, 20 Apr 2017 21:14:37 +0100 > > > > > > > > I agree, except I don't think you're going far enough. Those > > > "standard >

Re: [PATCH 3/4] nfs: remove the objlayout driver

On 04/20/2017 11:18 PM, Trond Myklebust wrote: <> > > OK. I'm applying this patch for the 4.12 merge window. That is understandable this code was not tested for a long while > If, as Boaz > suggests, there is still an interest in exofs, then I suggest we put > that to the test by moving it

Re: [PATCH v5 0/2] crypto: hw_random - Add new Exynos RNG driver

On Tue, Apr 11, 2017 at 08:08:33PM +0200, Krzysztof Kozlowski wrote: > Hi, > > This is a follow up of my questions around exynos-rng [1]. > > Changes since v4: > = > 1. Patch 2/2: Use "stdrng" name, as suggested by Herbert. > 2. Patch 2/2: Add Bartlomiej's reviewed-by. All

Re: [regression v4.11] 617f01211baf ("8139too: use napi_complete_done()")

On Fri, 2017-04-21 at 14:40 +0300, Ville Syrjälä wrote: > BTW I've also been getting some lockdep grief from r8169 netpoll stuff > recently. Not sure if it might be related to these changes or not, but > I don't remember seeing this sort of stuff until quite recently. > > [ 251.911044]

net/rose: null-ptr-deref in rose_route_frame

Hi, I've got the following error report while fuzzing the kernel with syzkaller. On commit 4f7d029b9bf009fbee76bb10c0c4351a1870d2f3 (4.11-rc7). rose_xmit calls rose_route_frame(skb, ax25 = NULL), and rose_route_frame then dereferences ax25 when doing ax25cmp(>dest_addr, _neigh->callsign).

<    1   2   3   4   5   6   7   8   9   10   >