[PATCH for 4.16] Documentation: Allow comments in arch features files

The list-arch.sh script considers lines beginning with "#" as match for the feature table. Given that those tables are never in lines beginning with "#", add a reverse grep on "^#" when matching the "ok/TODO" state of the architecture. This allows adding comments within the feature files, for ins

Re: update spectre v2 microcodes blacklist

I didn't fully match the updated revision guidance and spectre_bad_microcodes I compared these lists and it seems that the only difference is about skylakes. Everything else is covered by less-or-equal criteria on revision version. Both desktop and mobile skylakes are stated to be unaffected

[PATCH] HID: corsair: Add support for the GLAIVE RGB gaming mouse

This mouse sold by Corsair as the GLAIVE RGB gaming mouse has the same problem with its HID reports as the Scimitar PRO RGB, so reuse the same fix for the GLAIVE RGB. Signed-off-by: Guus Sliepen --- drivers/hid/hid-corsair.c | 16 ++-- drivers/hid/hid-ids.h | 1 + drivers/hid/hi

Re: [PATCH] MAINTAINERS: auxdisplay: remove obsolete webpages

On 02/10/2018 01:56 AM, Miguel Ojeda wrote: > Cc: Randy Dunlap > Signed-off-by: Miguel Ojeda Acked-by: Randy Dunlap Are you merging this directly to Linus? or what? Thanks. > --- > MAINTAINERS | 8 > 1 file changed, 8 deletions(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > inde

Re: [PATCH] staging: vc04_services: merge vchiq_kern_lib.c into vchiq_arm.c

> Arnd Bergmann hat am 2. Februar 2018 um 16:01 geschrieben: > > > There are two incompatible definitions of 'vchiq_instance_struct', so > passing them through vchiq_initialise(), vchiq_connect() or another > such interface is broken, as shown by building the driver with link-time > optimization

Re: [PATCH] x86/Kconfig: Further simplify the NR_CPUS config

On 02/10/2018 03:38 AM, Ingo Molnar wrote: > >> Cc: Linus Torvalds >> Signed-off-by: Ingo Molnar >> --- >> arch/x86/Kconfig | 66 >> +-- >> 1 file changed, 40 insertions(+), 26 deletions(-) > > Here is a full combo patch of your patch and

Re: Software evolution around “checkpatch.pl”?

On Sat, 2018-02-10 at 15:57 +, Jonathan Cameron wrote: > On Sat, 10 Feb 2018 06:59:43 -0800 > Joe Perches wrote: > > > On Sat, 2018-02-10 at 14:53 +, Jonathan Cameron wrote: > > > While it would be great to improve checkpatches false > > > positive rate, it's very nature as a string match

Re: [PATCH] p9caps: add Plan9 capability devices

Hi, On 02/10/2018 08:58 AM, Enrico Weigelt, metux IT consult wrote: > From: "Enrico Weigelt, metux IT consult" > > This driver implements the Plan9 capability devices, used for > switching user id via capability tokens. > > https://9p.io/sys/doc/auth.html > --- > drivers/staging/Kconfig

Re: [PATCH] p9caps: add Plan9 capability devices

On Sat, Feb 10, 2018 at 04:58:45PM +, Enrico Weigelt, metux IT consult wrote: > From: "Enrico Weigelt, metux IT consult" > +MODULE_LICENSE("GPLv3"); ... which is incompatible with GPLv2. I'm not even going to look at that thing - same as with proprietary code. You CAN'T combine any deriva

Re: [PATCH] seq_file: remove redundant assignment of index to m->index

On Sat, 2018-02-10 at 23:59 +0800, Donglin Peng wrote: > There are two redundant assignments in the traverse() function, because > the while loop will break after these two assignments, and after that > the variable index will be assigned to m->index again. [] > diff --git a/fs/seq_file.c b/fs/seq_

Re: [RFC PATCH 4/7] kconfig: support new special property shell=

On 02/10/2018 12:55 AM, Ulf Magnusson wrote: > How many compilers don't support -fno-stack-protector by the way? > > config CC_HAS_STACKPROTECTOR_STRONG > bool > option shell="$CC -Werror -fstack-protector-strong -c -x c > /dev/null" > > config CC_HA

[PATCH] lib/scatterlist: Make sg_page_count() accessible to other modules

Currently, sg_page_count() may be used only inside the scatterlist.c file. However, the same calculation is done outside of scatterlist.c file causing to code duplication. To fix this, we move the sg_page_count() to the scatterlist.h file, making it accessible to other modules. Signed-off-by: Al

[GIT PULL] PCI fixes for v4.16

PCI fixes: - fix POWER9/powernv INTx regression from the merge window (Alexey Kardashevskiy) The following changes since commit ab8c609356fbe8dbcd44df11e884ce8cddf3739e: Merge branch 'pci/spdx' into next (2018-02-01 11:40:07 -0600) are available in the Git repository at: ssh://g...@

[PATCH] PM / runtime: Update links_count also if !CONFIG_SRCU

Commit baa8809f6097 ("PM / runtime: Optimize the use of device links") added an invocation of pm_runtime_drop_link() to __device_link_del(). However there are two variants of that function, one for CONFIG_SRCU and another for !CONFIG_SRCU, and the commit only modified the former. Fixes: baa8809f60

[PATCH] drm/edid: drop the dcc probe before drm_do_get_edid

Now that drm_do_get_edid() handles override and firmware EDIDs it makes no sense to conditionalize it with a DCC probe. On the contrary -- the overrides are useful specifically when DCC is not functioning. drm_do_get_edid() already bails out when DCC fails, there's no need for an extra check. It s

[RFC PATCH] driver core: Count repeated addition of same device link

If device_link_add() is invoked multiple times with the same supplier and consumer combo, it will create the link on first addition and return a pointer to the already existing link on all subsequent additions. The semantics for device_link_del() are quite different, it deletes the link unconditio

Re: Software evolution around “checkpatch.pl”?

>> So I think checkpatch is striking the right balance here in >> how it warns. Obviously if it could assess the text >> and come to an informed decision that would be great but >> we are some way from that ;) > > The 'informed' bit is difficult as it is mostly a political problem. I find such a

Re: [PATCH 1/3] auxdisplay: charlcd: fix hex literal ranges for graphics command

On Sat, Feb 10, 2018 at 9:58 AM, Miguel Ojeda wrote: > On Sat, Feb 10, 2018 at 12:50 AM, Robert Abel wrote: >> The graphics command expects 16 hexadecimal literals, but would allow >> characters in range [0-9a-zA-Z] instead of [0-9a-fA-F]. >> >> Signed-off-by: Robert Abel Reviewed-by: Geert Uy

Re: [PATCH 1/3] auxdisplay: charlcd: fix hex literal ranges for graphics command

On Sat, Feb 10, 2018 at 07:31:54PM +0100, Geert Uytterhoeven wrote: > The redefinition feature definitely works with hex characters. > I've used it in the past, cfr. the picture on my Google+ profile ;-) > https://plus.google.com/u/0/+GeertUytterhoeven I've used it as well which is why I never not

Re: scsi: sg: assorted memory corruptions

On Sun, Feb 04, 2018 at 12:10:58PM +0100, Dmitry Vyukov wrote: > > > > To get memory corruption it's actually sufficient just to submit "1-byte" > > reads; > > there's no need for the SG_NEXT_CMD_LEN ioctl or anything: > > > > #include > > #include > > > > int main() > >

Re: [PATCH 4.9 46/92] x86/alternative: Print unadorned pointers

On Fri, Feb 9, 2018 at 11:23 PM, Greg Kroah-Hartman wrote: > On Fri, Feb 09, 2018 at 02:01:32PM -0800, Kees Cook wrote: >> On Fri, Feb 9, 2018 at 5:39 AM, Greg Kroah-Hartman >> wrote: >> > 4.9-stable review patch. If anyone has any objections, please let me know. >> > >> > -- >>

Re: [PATCH 4.9 46/92] x86/alternative: Print unadorned pointers

On Sat, Feb 10, 2018 at 11:14:18AM -0800, Kees Cook wrote: > I would just revert this commit from kernels earlier than 4.15; this > %p usage is in debugging, so %pK doesn't make much sense here. Yes, just drop it. That's only for debugging alternatives and not really needed in stable. -- Regards

Re: [RFC PATCH 4/7] kconfig: support new special property shell=

On Sat, Feb 10, 2018 at 12:55 AM, Ulf Magnusson wrote: > Here's a complete updated example, with some stuff from Masahiro added. > > Turns out warnings inside choices get cut off easily in menuconfig, so I > went with just a single warning instead (which should be enough anyway). > > With this ver

[git pull] poll annotations - second round

Preparations to solving the problems you've mentioned in the original poll series. After this series, run for V in IN OUT PRI ERR RDNORM RDBAND WRNORM WRBAND HUP RDHUP NVAL MSG; do L=`git grep -l -w POLL$V | grep -v '^t' | grep -v /um/ | grep -v '^sa' | grep -v '/poll.h$'|grep -v '^

Re: [PATCH] x86/decoder: Update UD0 to have operands

Hi Masami, I love your patch! Perhaps something to improve: [auto build test WARNING on tip/auto-latest] [also build test WARNING on v4.15 next-20180209] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/

Re: [PATCH V4 1/2] ptr_ring: fail early if queue occupies more than KMALLOC_MAX_SIZE

Hi Jason, On Fri, Feb 09, 2018 at 05:45:49PM +0800, Jason Wang wrote: > To avoid slab to warn about exceeded size, fail early if queue > occupies more than KMALLOC_MAX_SIZE. > > Reported-by: syzbot+e4d4f9ddd42955397...@syzkaller.appspotmail.com > Fixes: 2e0ab8ca83c12 ("ptr_ring: array based FIFO

[GIT PULL] platform-drivers-x86 for 4.16-3

Hi Linus, This series can wait for the RC cycle if you prefer. It's ready now and it simplifies branch management a bit on our end to merge it now. It is isolated to the Mellanox hotplug and platform drivers, and is mostly data for new system types with a correction and an uninitialized variable f

Re: [PATCH 1/3] dt-bindings: phy: phy-rockchip-typec: add usb3 otg reset

Hi Wulf, Am Montag, 22. Januar 2018, 12:33:05 CET schrieb wlf: > 在 2018年01月20日 05:49, Rob Herring 写道: > > On Thu, Jan 18, 2018 at 09:47:50AM -0800, Brian Norris wrote: > >> On Thu, Jan 18, 2018 at 06:20:09PM +0100, Enric Balletbo Serra wrote: > >>> As Brian said commit 06c47e6286d5 'usb: dwc3: of-

Re: [RFC PATCH 4/7] kconfig: support new special property shell=

On Sat, Feb 10, 2018 at 11:23 AM, Kees Cook wrote: > > So, if this could do something like this: > > config CC_HAS_STACKPROTECTOR_STRONG > bool > option > shell="scripts/gcc-${ARCH}_${BITS}-has-stack-protector.sh $CC > $KBUILD_CPPFLAGS" Guys, this is not th

Re: [PATCH v2 5/7] watchdog: mtk: allow setting timeout in devicetree

Hello Sean, On Sat, Feb 10, 2018 at 01:43:28PM +0100, Marcus Folkesson wrote: > Hello Sean, > > On Sat, Feb 10, 2018 at 07:10:02PM +0800, Sean Wang wrote: > > > > Hi, Marcus > > > > The changes you made for dt-bindings and driver should be put into > > separate patches. > > I actually thought

Re: [PATCH 09/31] x86/entry/32: Leave the kernel via trampoline stack

On Sat, Feb 10, 2018 at 7:26 AM, David Laight wrote: > > The alignment doesn't matter, 'rep movsl' will still work. .. no it won't. It might not copy the last two bytes or whatever, because the shift of the count will have ignored the low bits. But since an unaligned stack pointer really shouldn

Re: [PATCH 00/31 v2] PTI support for x86_32

On Sat, Feb 10, 2018 at 1:15 AM, Adam Borowski wrote: > > Alas, we got some data: > https://popcon.debian.org/ says 20% of x86 users have i386 as their main ABI > (current; people with popcon installed). One of the issues I've seen is that people often simply move a disk (or copy an installation)

[PATCH] staging: ade7759: Fix open parenthesis alignment

This patch fixes the CHECKs reported by checkpatch.pl for "alignment should match open parenthesis" Signed-off-by: rodrigosiqueira --- drivers/staging/iio/meter/ade7759.c | 80 ++--- 1 file changed, 38 insertions(+), 42 deletions(-) diff --git a/drivers/staging/i

[PATCH 0/2] GPIO-Timberdale: Adjustments for timbgpio_probe()

From: Markus Elfring Date: Sat, 10 Feb 2018 21:28:29 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation Improve a size determination drivers/gpio/gpio-timberdale.c | 7 +++ 1

[PATCH 1/2] gpio: timberdale: Delete an error message for a failed memory allocation in timbgpio_probe()

From: Markus Elfring Date: Sat, 10 Feb 2018 21:09:08 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/gpio/gpio-timberdale.c | 5 ++--- 1 file changed, 2 insertions

[PATCH 2/2] gpio: timberdale: Improve a size determination in timbgpio_probe()

From: Markus Elfring Date: Sat, 10 Feb 2018 21:13:28 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was det

[PATCH 2/4] watchdog: omap_wdt: change order for setting default timeout

watchdog_init_timeout() will preserve wdd->timeout value if no parameter nor timeout-secs dt property is set. Signed-off-by: Marcus Folkesson --- drivers/watchdog/omap_wdt.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/watchdog/omap_wdt.c b/drivers/watchdog/oma

[PATCH 4/4] watchdog: lpc18xx: remove assignment of unused ret-value

Signed-off-by: Marcus Folkesson --- drivers/watchdog/lpc18xx_wdt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/watchdog/lpc18xx_wdt.c b/drivers/watchdog/lpc18xx_wdt.c index b4221f43cd94..331cadb459ac 100644 --- a/drivers/watchdog/lpc18xx_wdt.c +++ b/drivers/watchdo

[PATCH 3/4] watchdog: gpio: change order for setting default timeout

watchdog_init_timeout() will preserve wdd->timeout value if no parameter nor timeout-secs dt property is set. Signed-off-by: Marcus Folkesson --- drivers/watchdog/gpio_wdt.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/watchdog/gpio_wdt.c b/drivers/watchdog/gpi

[PATCH 1/4] watchdog: uniphier: change order for setting default timeout

watchdog_init_timeout() will preserve wdd->timeout value if no parameter nor timeout-secs dt property is set. Signed-off-by: Marcus Folkesson --- drivers/watchdog/uniphier_wdt.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/watchdog/uniphier_wdt.c b/drivers/wat

Re: [lustre-devel] [PATCH 41/80] staging: lustre: lmv: separate master object with master stripe

> > On Feb 8, 2018, at 10:10 PM, NeilBrown wrote: > > > > On Thu, Feb 08 2018, Oleg Drokin wrote: > > > >>> On Feb 8, 2018, at 8:39 PM, NeilBrown wrote: > >>> > >>> On Tue, Aug 16 2016, James Simmons wrote: > >> > >> my that’s an old patch > >> > >>> > > ... > >>> > >>> Whoever converted

Re: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators

Hey Sergey, Thanks for mentioning, but I think the problem has nothing to do with those patches. I tested them with the v4.15.0 Kernel since this is the last stable release and we are right now in the merging window. I tested the latest mainline, without those patches and the kernel is not b

[PATCH 0/2] GPIO-OMAP: Adjustments for omap_gpio_probe()

From: Markus Elfring Date: Sat, 10 Feb 2018 21:56:54 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation Improve a size determination drivers/gpio/gpio-omap.c | 6 ++ 1 file ch

[PATCH 1/2] gpio: omap: Delete an error message for a failed memory allocation in omap_gpio_probe()

From: Markus Elfring Date: Sat, 10 Feb 2018 21:46:30 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/gpio/gpio-omap.c | 4 +--- 1 file changed, 1 insertion(+), 3 d

[PATCH 2/2] gpio: omap: Improve a size determination in omap_gpio_probe()

From: Markus Elfring Date: Sat, 10 Feb 2018 21:49:22 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was det

[PATCH] kstrtox: make kstrtobool_from_user() very strict

Once upon a time module parameter parsing code accepted 0, 1, y, n, Y and N for boolean values. Gratituous but contained to module code and thus tolerable. Commit ef951599074ba4fad2d0efa0a977129b41e6d203 ("lib: move strtobool() to kstrtobool()") promoted that ugly wart to kstrtobool() and, more im

Re: [PATCH] x86_64: clobber flags in clear_page()

On Sat, Jan 13, 2018 at 09:50:48PM +0300, Alexey Dobriyan wrote: > All clear_page() implementations use XOR which resets flags. > > Judging by allyesconfig disassembly no code is affected. > > Signed-off-by: Alexey Dobriyan > --- > > arch/x86/include/asm/page_64.h |2 +- > 1 file changed,

Re: [PATCH] x86_64: trim clear_page.S includes

On Sat, Jan 13, 2018 at 10:06:48PM +0300, Alexey Dobriyan wrote: > After alternatives were shifted to the call site, only 2 headers are > necessary. > > Signed-off-by: Alexey Dobriyan > --- > > arch/x86/lib/clear_page_64.S |2 -- > 1 file changed, 2 deletions(-) > > --- a/arch/x86/lib/clea

[PATCH] gpio-ml-ioh: Delete an error message for a failed memory allocation in ioh_gpio_probe()

From: Markus Elfring Date: Sat, 10 Feb 2018 22:27:15 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/gpio/gpio-ml-ioh.c | 1 - 1 file changed, 1 deletion(-) diff

Re: [PATCH] MAINTAINERS: auxdisplay: remove obsolete webpages

On Sat, 2018-02-10 at 09:32 -0800, Randy Dunlap wrote: > On 02/10/2018 01:56 AM, Miguel Ojeda wrote: > > Cc: Randy Dunlap > > Signed-off-by: Miguel Ojeda > > Acked-by: Randy Dunlap > > Are you merging this directly to Linus? or what? A generic negative of these removals, even for ancient dri

Re: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators

On 02/11/2018 12:01 AM, Philipp Rossak wrote: Hey Sergey, Thanks for mentioning, but I think the problem has nothing to do with those patches. I tested them with the v4.15.0 Kernel since this is the last stable release and we are right now in the merging window. I tested the latest mainline,

Re: [PATCH 0/3] Fix broken bananapi m2 devicetree/regulators

On 10.02.2018 22:08, Sergey Suloev wrote: On 02/11/2018 12:01 AM, Philipp Rossak wrote: Hey Sergey, Thanks for mentioning, but I think the problem has nothing to do with those patches. I tested them with the v4.15.0 Kernel since this is the last stable release and we are right now in the me

Re: [PATCH 41/80] staging: lustre: lmv: separate master object with master stripe

> > +static inline bool > > +lsm_md_eq(const struct lmv_stripe_md *lsm1, const struct lmv_stripe_md > > *lsm2) > > +{ > > + int idx; > > + > > + if (lsm1->lsm_md_magic != lsm2->lsm_md_magic || > > + lsm1->lsm_md_stripe_count != lsm2->lsm_md_stripe_count || > > + lsm1->lsm_md_maste

Re: [PATCH] x86/Kconfig: Further simplify the NR_CPUS config

Looks good to me. At the risk of bike-shedding, we could remove all the default1 if !SMP from the BEGIN/END/DEFAULT things, and perhaps just keep that part in NR_CPUS. I didn't check, but I *think* it would work to just do config NR_CPUS int "Maximum number of CPUs" if SMP

Re: [PATCH 2/6] genalloc: selftest

On 05/02/18 00:19, Randy Dunlap wrote: > On 02/04/2018 08:47 AM, Igor Stoppa wrote: [...] > Please use kernel multi-line comment style. ok for all of them [...] >> +BUG_ON(!locations[action->location]); >> +print_first_chunk_bitmap(pool); >> +BUG_ON(compare_bitmaps(pool, action->pa

[PATCH v2 3/6] KVM: x86: Reduce retpoline performance impact in slot_handle_level_range()

With retpoline, tight loops of "call this function for every XXX" are very much pessimised by taking a prediction miss *every* time. This one is by far the biggest contributor to the guest launch time with retpoline. By marking the iterator slot_handle_…() functions always_inline, we can ensure th

[PATCH v2 5/6] KVM/nVMX: Set the CPU_BASED_USE_MSR_BITMAPS if we have a valid L02 MSR bitmap

From: KarimAllah Ahmed We either clear the CPU_BASED_USE_MSR_BITMAPS and end up intercepting all MSR accesses or create a valid L02 MSR bitmap and use that. This decision has to be made every time we evaluate whether we are going to generate the L02 MSR bitmap. Before commit 086e7d4118cc ("KVM:

[PATCH v2 6/6] x86/speculation: Use IBRS if available before calling into firmware

Retpoline means the kernel is safe because it has no indirect branches. But firmware isn't, so use IBRS for firmware calls if it's available. Signed-off-by: David Woodhouse --- arch/x86/include/asm/apm.h | 6 ++ arch/x86/include/asm/cpufeatures.h | 1 + arch/x86/include/asm/efi

[PATCH v2 4/6] X86/nVMX: Properly set spec_ctrl and pred_cmd before merging MSRs

From: KarimAllah Ahmed These two variables should check whether SPEC_CTRL and PRED_CMD are supposed to be passed through to L2 guests or not. While msr_write_intercepted_l01 would return 'true' if it is not passed through. So just invert the result of msr_write_intercepted_l01 to implement the c

[PATCH v2 0/6] Spectre v2 updates

Using retpoline ensures the kernel is safe because it doesn't contain any indirect branches, but firmware still can — and we make calls into firmware at runtime. Where the IBRS microcode support is available, use that before calling into firmware. While doing that, I noticed that we were calling C

[PATCH v2 1/6] x86/speculation: Update Speculation Control microcode blacklist

Intel have retroactively blessed the 0xc2 microcode on Skylake mobile and desktop parts, and the Gemini Lake 0x22 microcode is apparently fine too. We blacklisted the latter purely because it was present with all the other problematic ones in the 2018-01-08 release, but now it's explicitly listed a

[PATCH v2 2/6] Revert "x86/speculation: Simplify indirect_branch_prediction_barrier()"

This reverts commit 64e16720ea0879f8ab4547e3b9758936d483909b. We cannot call C functions like that, without marking all the call-clobbered registers as, well, clobbered. We might have got away with it for now because the __ibp_barrier() function was *fairly* unlikely to actually use any other regi

are you fine ?

We want to introduce our business we are sure that you will benefit from this business our association works in the mines we have golden dust for sale at very interesting prices very low price (27.000$ one kg) We are looking for partners if you are interested contact us give us your phone con

Re: [PATCH 4/6] Protectable Memory

On 05/02/18 00:06, Randy Dunlap wrote: > On 02/04/2018 08:47 AM, Igor Stoppa wrote: [...] >> + * pmalloc_create_pool - create a new protectable memory pool - > > Drop trailing " -". yes >> + * @name: the name of the pool, must be unique > > Is that enforced? Will return NULL if @name is dupl

Re: [PATCH 2/2] xen: xenbus: WARN_ON XS_TRANSACTION_{START,END} misuse

Boris Ostrovsky: > On 02/07/2018 05:22 PM, Simon Gaiser wrote: >> +users_old = xs_state_users; >> xs_state_users--; >> if ((req->type == XS_TRANSACTION_START && req->msg.type == XS_ERROR) || >> req->type == XS_TRANSACTION_END) >> xs_state_users--; >> +if (WAR

Re: [PATCH 5/6] Pmalloc: self-test

On 07/02/18 19:18, kbuild test robot wrote: > Hi Igor, > > Thank you for the patch! Yet something to improve: > > [auto build test ERROR on kees/for-next/pstore] > [also build test ERROR on v4.15] > [cannot apply to linus/master mmotm/master next-20180207] > [if your patch is applied to the wro

RE: [PATCH] cpufreq: imx6q: support frequencies >528MHz for i.MX6UL/ULL

Anson Huang Best Regards! > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: Sunday, February 11, 2018 12:26 AM > To: Stefan Agner ; Anson Huang > Cc: r...@rjwysocki.net; viresh kumar ; > linux...@vger.kernel.org; Marcel Ziswiler ; > max.oss...@gmail.com; li

Re: [PATCH] x86/Kconfig: Further simplify the NR_CPUS config

On 02/10/2018 02:19 PM, Linus Torvalds wrote: > Looks good to me. > > At the risk of bike-shedding, we could remove all the > > default1 if !SMP > > from the BEGIN/END/DEFAULT things, and perhaps just keep that part in NR_CPUS. > > I didn't check, but I *think* it would work to just

Re: [PATCH v2 5/7] watchdog: mtk: allow setting timeout in devicetree

On 02/10/2018 12:12 PM, Marcus Folkesson wrote: Hello Sean, On Sat, Feb 10, 2018 at 01:43:28PM +0100, Marcus Folkesson wrote: Hello Sean, On Sat, Feb 10, 2018 at 07:10:02PM +0800, Sean Wang wrote: Hi, Marcus The changes you made for dt-bindings and driver should be put into separate patches

tmpfs and brickability (size=50% default considered naieve).

If you have two default tmpfs instances on your box (hi buildroot!) and they're world writeable and a normal user goes "cat /dev/zero > /run/fillit; cat /dev/zero > /tmp/fillit" the system then goes "sh: can't fork" trying to call rm on those files, because they each default to 50% of total system

Re: [PATCH] Input: gpio_keys: Add level trigger support for GPIO keys

On 9 February 2018 at 23:03, Andy Shevchenko wrote: > On Fri, Feb 9, 2018 at 11:23 AM, Baolin Wang wrote: >> On 9 February 2018 at 14:39, Dmitry Torokhov >> wrote: >>> On Thu, Feb 8, 2018 at 10:08 PM, Baolin Wang wrote: On some platforms (such as Spreadtrum platform), the GPIO keys can on

Re: [RFC PATCH 4/7] kconfig: support new special property shell=

On Sat, Feb 10, 2018 at 10:05:12AM -0800, Randy Dunlap wrote: > On 02/10/2018 12:55 AM, Ulf Magnusson wrote: > > How many compilers don't support -fno-stack-protector by the way? > > > > config CC_HAS_STACKPROTECTOR_STRONG > > bool > > option shell="$CC -Werror -fstack-

Re: [PATCH 2/6] genalloc: selftest

On 07/02/18 22:25, kbuild test robot wrote: [...] >>> lib/genalloc-selftest.c:17:10: fatal error: asm/set_memory.h: No such file >>> or directory > #include This header is unnecessary and will be removed. -- igor

[PATCH v3] KVM: VMX: Don't halt vcpu when L1 is injecting events to L2

Although L2 is in halt state, it will be in the active state after VM entry if the VM entry is vectoring according to SDM 26.6.2 Activity State. Halting the vcpu here means the event won't be injected to L2 and this decision isn't reported to L1. Thus L0 drops an event that should be injected to L2

Re: [PATCH] seq_file: remove redundant assignment of index to m->index

On Sat, Feb 10, 2018 at 10:04:23AM -0800, Joe Perches wrote: > > @@ -120,14 +120,12 @@ static int traverse(struct seq_file *m, loff_t offset) > > if (pos + m->count > offset) { > > m->from = offset - pos; > > m->count -= m->from; > > -m->index = index;

Re: [V9fs-developer] [RFC] we should solve create-unlink-getattr idiom

On 2018/2/9 19:33, Greg Kurz wrote: > On Fri, 9 Feb 2018 15:10:46 +0800 > jiangyiwen wrote: > >> Hi Eric and Greg, >> >> I encountered the similar problem with create-unlink-getattr idiom. >> I use the testcase that create-unlink-setattr idiom, and I see the >> bug is reported at https://bugs.lau

[BUG]: A83T - AC100 gets the wrong number of parents

Hey, When I boot my A83T I get the following bootlog [1]. After some debugging, I found out that the function call: clk_hw_get_num_parents() returns 2. After a look in the devicetree I found out that this value should be 1, since we only have one parent clock [3]. Setting the variable num_parents

Re: [PATCH V4 2/2] ptr_ring: try vmalloc() when kmalloc() fails

On 2018年02月09日 23:53, Michael S. Tsirkin wrote: On Fri, Feb 09, 2018 at 05:45:50PM +0800, Jason Wang wrote: This patch switch to use kvmalloc_array() for using a vmalloc() fallback to help in case kmalloc() fails. Above isn't really saying anything about the motivation, it just explains what

Re: [PATCH V4 1/2] ptr_ring: fail early if queue occupies more than KMALLOC_MAX_SIZE

On 2018年02月11日 03:32, Eric Biggers wrote: Hi Jason, On Fri, Feb 09, 2018 at 05:45:49PM +0800, Jason Wang wrote: To avoid slab to warn about exceeded size, fail early if queue occupies more than KMALLOC_MAX_SIZE. Reported-by: syzbot+e4d4f9ddd42955397...@syzkaller.appspotmail.com Fixes: 2e0ab8

[PATCH] PCI/portdrv: Remove "pcie_hp=nomsi" kernel parameter

From: Bjorn Helgaas 7570a333d8b0 ("PCI: Add pcie_hp=nomsi to disable MSI/MSI-X for pciehp driver") added the "pcie_hp=nomsi" kernel parameter to work around this error on shutdown: irq 16: nobody cared (try booting with the "irqpoll" option) Pid: 1081, comm: reboot Not tainted 3.2.0 #1 ...

Re: [Qemu-devel] [RFC PATCH] vfio/pci: Add ioeventfd support

On Fri, Feb 09, 2018 at 02:45:41PM -0700, Alex Williamson wrote: > On Fri, 9 Feb 2018 15:05:11 +0800 > Peter Xu wrote: > > > On Tue, Feb 06, 2018 at 05:08:14PM -0700, Alex Williamson wrote: > > > > [...] > > > > > +long vfio_pci_ioeventfd(struct vfio_pci_device *vdev, loff_t offset, > > > +

Re: [PATCH V2 0/6]nvme-pci: fixes on nvme_timeout and nvme_dev_disable

On 02/10/2018 10:32 AM, jianchao.wang wrote: > Hi Keith > > Thanks for your kindly response here. > That's really appreciated. > > On 02/10/2018 01:12 AM, Keith Busch wrote: >> On Fri, Feb 09, 2018 at 09:50:58AM +0800, jianchao.wang wrote: >>> >>> if we set NVME_REQ_CANCELLED and return BLK_EH_

[RFC PATCH v15 0/6] mm: security: ro protection for dynamic data

This patch-set introduces the possibility of protecting memory that has been allocated dynamically. The memory is managed in pools: when a memory pool is turned into R/O, all the memory that is part of it, will become R/O. A R/O pool can be destroyed, to recover its memory, but it cannot be turne

[PATCH 1/6] genalloc: track beginning of allocations

The genalloc library is only capable of tracking if a certain unit of allocation is in use or not. It is not capable of discerning where the memory associated to an allocation request begins and where it ends. The reason is that units of allocations are tracked by using a bitmap, where each bit r

Re: [PATCH] KVM: X86: Fix SMRAM accessing even if VM is shutdown

On 02/09/2018 08:42 PM, Paolo Bonzini wrote: On 09/02/2018 04:22, Xiao Guangrong wrote: That is a good question... :) This case (with KVM_MEMSLOT_INVALID is set) can be easily constructed, userspace should avoid this case by itself (avoiding vCPU accessing the memslot which is being update

[PATCH 3/6] struct page: add field for vm_struct

When a page is used for virtual memory, it is often necessary to obtian a handler to the corresponding vm_struct, which refers to the virtually continuous area generated when invoking vmalloc. The struct page has a "mapping" field, which can be re-used, to store a pointer to the parent area. This

[PATCH 2/6] genalloc: selftest

Introduce a set of macros for writing concise test cases for genalloc. The test cases are meant to provide regression testing, when working on new functionality for genalloc. Primarily they are meant to confirm that the various allocation strategy will continue to work as expected. The execution

[PATCH 5/6] Pmalloc: self-test

Add basic self-test functionality for pmalloc. Signed-off-by: Igor Stoppa --- mm/Kconfig| 9 mm/Makefile | 1 + mm/pmalloc-selftest.c | 63 +++ mm/pmalloc-selftest.h | 24 mm/pmalloc.c

[PATCH 4/6] Protectable Memory

The MMU available in many systems running Linux can often provide R/O protection to the memory pages it handles. However, the MMU-based protection works efficiently only when said pages contain exclusively data that will not need further modifications. Statically allocated variables can be segreg

[PATCH 6/6] Documentation for Pmalloc

Detailed documentation about the protectable memory allocator. Signed-off-by: Igor Stoppa --- Documentation/core-api/index.rst | 1 + Documentation/core-api/pmalloc.rst | 114 + 2 files changed, 115 insertions(+) create mode 100644 Documentation/core-api/

[PATCH net] ptr_ring: prevent integer overflow when calculating size

Switch to use dividing to prevent integer overflow when size is too big to calculate allocation size properly. Reported-by: Eric Biggers Fixes: 6e6e41c31122 ("ptr_ring: fail early if queue occupies more than KMALLOC_MAX_SIZE") Signed-off-by: Jason Wang --- include/linux/ptr_ring.h | 2 +- 1 fi

[PATCH v3 0/3] KVM: Introduce dedicated vCPUs hint KVM_HINTS_DEDICATED

This patchset introduces dedicated vCPUs hint KVM_HINTS_DEDICATED, it has two users now: 1) Waiman Long mentioned that: Generally speaking, unfair lock performs well for VMs with a small number of vCPUs. Native qspinlock may perform better than pvqspinlock if there is vCPU pinning an

[PATCH v3 3/3] KVM: X86: Don't use PV TLB flush with dedicated vCPUs and steal time disabled

From: Wanpeng Li vCPUs are very unlikely to get preempted when they are the only task running on a CPU. PV TLB flush is slower that the native flush in that case. In addition, avoid traversing all the cpus for pv tlb flush when steal time is disabled since pv tlb flush depends on the field in s

[PATCH v3 2/3] KVM: X86: Choose qspinlock when dedicated vCPUs available

From: Wanpeng Li Waiman Long mentioned that: Generally speaking, unfair lock performs well for VMs with a small number of vCPUs. Native qspinlock may perform better than pvqspinlock if there is vCPU pinning and there is no vCPU over-commitment. This patch uses a KVM_HINTS_DEDICATED performan

[PATCH v3 1/3] KVM: Introduce dedicated vCPUs hint KVM_HINTS_DEDICATED

From: Wanpeng Li This patch introduces dedicated vCPUs hint KVM_HINTS_DEDICATED, guest checks this feature bit to determine if they run on dedicated vCPUs, allowing optimizations. Cc: Paolo Bonzini Cc: Radim Krčmář Cc: Eduardo Habkost Signed-off-by: Wanpeng Li --- Documentation/virtual/kv

Re: [PATCH] f2fs: set_code_data in move_data_block

Ping... move_data_block misses set_cold_data, then the F2FS_WB_CP_DATA will lack these data pages in move_data_block, and write_checkpoint can not make sure this pages committed to the flash. On 2018/2/8 20:33, Yunlong Song wrote: Signed-off-by: Yunlong Song --- fs/f2fs/gc.c | 1 + 1 file c

Kconfig:12: can't open file "arch/powerpc64/Kconfig"

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d48fcbd864a008802a90c58a9ceddd9436d11a49 commit: 9e3e10c725360b9d07018cfcd5b7b6b7d325fae5 kconfig: send error messages to stderr date: 2 days ago config: powerpc64-defconfig compiler: powerpc64-linux-gcc (

Re: [PATCH] f2fs: set_code_data in move_data_block

On 2018/2/11 11:34, Yunlong Song wrote: > Ping... > > move_data_block misses set_cold_data, then the F2FS_WB_CP_DATA will > lack these data pages in move_data_block, and write_checkpoint can > not make sure this pages committed to the flash. Hmm.. data block migration is running based on meta ino

RE: [PATCH] f2fs: set_code_data in move_data_block

>-Original Message- >From: Songyunlong (Euler) >Sent: Sunday, February 11, 2018 11:35 AM >To: jaeg...@kernel.org; c...@kernel.org; Yuchao (T); yunlong.s...@icloud.com >Cc: miaoxie (A); Wangbintian; shengyong (A); heyunlei; >linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kernel

Re: [PATCH 1/4] watchdog: uniphier: change order for setting default timeout

On 02/10/2018 12:36 PM, Marcus Folkesson wrote: watchdog_init_timeout() will preserve wdd->timeout value if no parameter nor timeout-secs dt property is set. Signed-off-by: Marcus Folkesson Reviewed-by: Guenter Roeck --- drivers/watchdog/uniphier_wdt.c | 5 ++--- 1 file changed, 2 inser

<    1   2   3   4   5   >