Re: [PATCH] pci-error-recover: doc cleanup

I suppose I'm confused, but I recall that link resets are non-fatal. Fatal errors typically require that the the pci adapter be completely reset, any adapter firmware to be reloaded from scratch, the device driver has to kill all device state and start from scratch. Its huge. If the fatal error is

Re: [PATCH v2] watchdog: nic7018_wdt: Add NIC7018 watchdog driver

On Thu, 2016-12-08 at 06:15 -0800, Guenter Roeck wrote: > On 12/08/2016 01:19 AM, Hui Chun Ong wrote: > > > > On Thu, 2016-11-24 at 11:56 -0800, Guenter Roeck wrote: > > > > > > On 11/15/2016 07:21 PM, Hui Chun Ong wrote: > > > > > > > > > > > > Add support for the watchdog timer on PXI

Re: [PATCH] doc: Explain light-handed markup preference a bit better

On Thu, Dec 8, 2016 at 10:10 AM, Mauro Carvalho Chehab wrote: > Em Wed, 7 Dec 2016 12:39:24 -0700 > Jonathan Corbet escreveu: > >> On Wed, 7 Dec 2016 16:42:58 +0100 >> Daniel Vetter wrote: >> >> > We already had a super-short

Re: [RFC 02/10] module: fix memory leak on early load_module() failures

On Thu, Dec 8, 2016 at 1:10 PM, Luis R. Rodriguez wrote: > On Thu, Dec 8, 2016 at 2:30 PM, Kees Cook wrote: >> On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote: >>> While looking for early possible module loading failures I

Re: [RFC 03/10] kmod: add dynamic max concurrent thread count

On Thu, Dec 08, 2016 at 12:28:07PM -0800, Kees Cook wrote: > On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote: > > diff --git a/kernel/kmod.c b/kernel/kmod.c > > index 0277d1216f80..cb6f7ca7b8a5 100644 > > --- a/kernel/kmod.c > > +++ b/kernel/kmod.c > > @@ -44,6 +44,9

Re: [RFC 04/10] kmod: provide wrappers for kmod_concurrent inc/dec

On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote: > kmod_concurrent is used as an atomic counter for enabling > the allowed limit of modprobe calls, provide wrappers for it > to enable this to be expanded on more easily. This will be done > later. > > Signed-off-by:

Re: [RFC 03/10] kmod: add dynamic max concurrent thread count

On Thu, Dec 8, 2016 at 11:48 AM, Luis R. Rodriguez wrote: > We currently statically limit the number of modprobe threads which > we allow to run concurrently to 50. As per Keith Owens, this was a > completely arbitrary value, and it was set in the 2.3.38 days [0] > over 16

[RFC 07/10] kmod: use simplified rate limit printk

Just use the simplified rate limit printk when the max modprobe limit is reached, while at it throw out a bone should the error be triggered. Signed-off-by: Luis R. Rodriguez --- kernel/kmod.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git

[RFC 10/10] kmod: add a sanity check on module loading

kmod has an optimization in place whereby if a some kernel code uses request_module() on a module already loaded we never bother userspace as the module already is loaded. This is not true for get_fs_type() though as it uses aliases. Additionally kmod <= v19 was broken -- it returns 0 to modprobe

[RFC 05/10] kmod: return -EBUSY if modprobe limit is reached

Running out of our modprobe limit is not a memory limit but a system specific established limitation set to avoid a possible recursive issue with modprobe. This gives userspace a better idea of what happened if we can't load a module, it could use this to wait and try again. Signed-off-by: Luis

[RFC 04/10] kmod: provide wrappers for kmod_concurrent inc/dec

kmod_concurrent is used as an atomic counter for enabling the allowed limit of modprobe calls, provide wrappers for it to enable this to be expanded on more easily. This will be done later. Signed-off-by: Luis R. Rodriguez --- kernel/kmod.c | 27 +-- 1

[RFC 00/10] kmod: stress test driver, few fixes and enhancements

for filesystem drivers. These patches are available on my linux-next git-tree on my branch 20161208-kmod-test-driver-try2 [0], which is based on linux-next tag next-20161208. Patches are also available based on v4.9-rc8 [1] for those looking for a bit more stable tree given x86_64 on linux-next is hosed

[RFC 01/10] kmod: add test driver to stress test the module loader

This adds a new stress test driver for kmod: the kernel module loader. The new stress test driver, test_kmod, is only enabled as a module right now. It should be possible to load this as built-in and load tests early (refer to the force_init_test module parameter), however since a lot of test can

Re: [PATCH v3 0/6] net: stmmac: make DMA programmable burst length more configurable

From: Niklas Cassel Date: Wed, 7 Dec 2016 15:20:02 +0100 > Make DMA programmable burst length more configurable in the stmmac driver. > > This is done by adding support for independent pbl for tx/rx through DT. > More fine grained tuning of pbl is possible thanks to a DT

Re: [PATCH v2] watchdog: nic7018_wdt: Add NIC7018 watchdog driver

On 12/08/2016 01:19 AM, Hui Chun Ong wrote: On Thu, 2016-11-24 at 11:56 -0800, Guenter Roeck wrote: On 11/15/2016 07:21 PM, Hui Chun Ong wrote: Add support for the watchdog timer on PXI Embedded Controller. Signed-off-by: Hui Chun Ong --- v1: Remove non-standard

Re: [PATCH] pci-error-recover: doc cleanup

On 12/08/2016 10:05 PM, Jonathan Corbet wrote: > On Thu, 8 Dec 2016 16:16:14 +0800 > Cao jin wrote: > >> The platform resets the link, and then calls the link_reset() callback >> on all affected device drivers. This is a PCI-Express specific state >> -and is done

Re: [PATCH] pci-error-recover: doc cleanup

On Thu, 8 Dec 2016 16:16:14 +0800 Cao jin wrote: > The platform resets the link, and then calls the link_reset() callback > on all affected device drivers. This is a PCI-Express specific state > -and is done whenever a non-fatal error has been detected that can be >

Re: [PATCH v3 6/6] net: smmac: allow configuring lower pbl values

Hi, In subject: s/smmac/stmmac/ Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to

Re: [PATCH 16/18] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32

On Wed, Dec 07, 2016 at 09:40:13PM +0100, Arnd Bergmann wrote: > On Wednesday, December 7, 2016 4:59:13 PM CET Catalin Marinas wrote: > > On Tue, Dec 06, 2016 at 11:55:08AM +0530, Yury Norov wrote: > > > On Mon, Dec 05, 2016 at 04:34:23PM +, Catalin Marinas wrote: > > > > On Fri, Oct 21, 2016

Re: [PATCH v2] watchdog: nic7018_wdt: Add NIC7018 watchdog driver

On Thu, 2016-11-24 at 11:56 -0800, Guenter Roeck wrote: > On 11/15/2016 07:21 PM, Hui Chun Ong wrote: > > > > Add support for the watchdog timer on PXI Embedded Controller. > > > > Signed-off-by: Hui Chun Ong > > --- > > v1: Remove non-standard attributes. > > Change

Re: [PATCH v3 6/6] net: smmac: allow configuring lower pbl values

Hi Niklas, On 12/07/2016 03:20 PM, Niklas Cassel wrote: From: Niklas Cassel The driver currently always sets the PBLx8/PBLx4 bit, which means that the pbl values configured via the pbl/txpbl/rxpbl DT properties are always multiplied by 8/4 in the hardware. In order to

Re: [PATCH v3 5/6] net: stmmac: add support for independent DMA pbl for tx/rx

Hi Niklas On 12/07/2016 03:20 PM, Niklas Cassel wrote: From: Niklas Cassel GMAC and newer supports independent programmable burst lengths for DMA tx/rx. Add new optional devicetree properties representing this. To be backwards compatible, snps,pbl will still be valid,