[PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-11-07 Thread Jan Kara
Hello, This is the next iteration of my printk patchset. Since v5 I've made the limit for printing configurable via kernel parameter and let it default to 0. So unless user sets printk.offload_chars on kernel command line, there will be no difference to current printk behavior. Summary: Thes

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-09-22 Thread Jan Kara
On Thu 19-09-13 14:26:27, Andrew Morton wrote: > On Thu, 5 Sep 2013 17:46:12 +0200 Jan Kara wrote: > > On Fri 23-08-13 12:58:22, Andrew Morton wrote: > > > On Fri, 23 Aug 2013 21:48:36 +0200 (CEST) Jiri Kosina > > > wrote: > > > > > > > > > We have customers (quite a few of them actually) whi

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-09-19 Thread Andrew Morton
On Thu, 5 Sep 2013 17:46:12 +0200 Jan Kara wrote: > Sorry for a delayed reply. I was on vacation... > > On Fri 23-08-13 12:58:22, Andrew Morton wrote: > > On Fri, 23 Aug 2013 21:48:36 +0200 (CEST) Jiri Kosina > > wrote: > > > > > > > We have customers (quite a few of them actually) which

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-09-05 Thread Jan Kara
Sorry for a delayed reply. I was on vacation... On Fri 23-08-13 12:58:22, Andrew Morton wrote: > On Fri, 23 Aug 2013 21:48:36 +0200 (CEST) Jiri Kosina wrote: > > > > > We have customers (quite a few of them actually) which have machines > > > > with > > > > lots of SCSI disks attached (due

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-26 Thread Jiri Kosina
On Fri, 23 Aug 2013, Andrew Morton wrote: > > > > We have customers (quite a few of them actually) which have machines > > > > with > > > > lots of SCSI disks attached (due to multipath etc.) and during boot when > > > > these disks are discovered and partitions set up quite some printing > > >

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-23 Thread Andrew Morton
On Fri, 23 Aug 2013 21:48:36 +0200 (CEST) Jiri Kosina wrote: > > > We have customers (quite a few of them actually) which have machines > > > with > > > lots of SCSI disks attached (due to multipath etc.) and during boot when > > > these disks are discovered and partitions set up quite some pr

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-23 Thread Jiri Kosina
On Thu, 22 Aug 2013, Andrew Morton wrote: > Years of hard experience have taught me: don't muck with printk. It > needs to be robust, simple and to have minimum dependency on both the > calling environment and on correctly functioning kernel components. > printk and NMI are the harshest environm

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-23 Thread Jiri Kosina
On Thu, 22 Aug 2013, Andrew Morton wrote: > > We have customers (quite a few of them actually) which have machines with > > lots of SCSI disks attached (due to multipath etc.) and during boot when > > these disks are discovered and partitions set up quite some printing > > happens - multiplied b

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-22 Thread Andrew Morton
On Thu, 22 Aug 2013 23:57:42 +0200 Jan Kara wrote: > On Thu 22-08-13 12:49:13, Andrew Morton wrote: > > Desperately seeking alternatives... > > > > I suppose there's some reason why we can't just make those drivers shut > > up? If the messages are in the log buffer but aren't displayed, > > the

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-22 Thread Jan Kara
On Thu 22-08-13 12:49:13, Andrew Morton wrote: > On Thu, 22 Aug 2013 00:59:15 +0200 Jan Kara wrote: > > > On Wed 21-08-13 14:27:23, Andrew Morton wrote: > > > On Wed, 21 Aug 2013 10:08:28 +0200 Jan Kara wrote: > > > > > > > These patches avoid softlockups when a CPU gets caught in > > > > cons

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-22 Thread Andrew Morton
On Thu, 22 Aug 2013 00:59:15 +0200 Jan Kara wrote: > On Wed 21-08-13 14:27:23, Andrew Morton wrote: > > On Wed, 21 Aug 2013 10:08:28 +0200 Jan Kara wrote: > > > > > These patches avoid softlockups when a CPU gets caught in > > > console_unlock() for > > > a long time during heavy printing from

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-21 Thread Jan Kara
On Wed 21-08-13 14:27:23, Andrew Morton wrote: > On Wed, 21 Aug 2013 10:08:28 +0200 Jan Kara wrote: > > > These patches avoid softlockups when a CPU gets caught in console_unlock() > > for > > a long time during heavy printing from other CPU. As is discussed in patch > > 3/4 > > it isn't enough

Re: [PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-21 Thread Andrew Morton
On Wed, 21 Aug 2013 10:08:28 +0200 Jan Kara wrote: > These patches avoid softlockups when a CPU gets caught in console_unlock() for > a long time during heavy printing from other CPU. As is discussed in patch 3/4 > it isn't enough to just silence the watchdog because if CPU spends too long in > c

[PATCH 0/4 v6] Avoid softlockups in console_unlock()

2013-08-21 Thread Jan Kara
Hello, This is the next iteration of my printk patchset. Since v5 I've made the limit for printing configurable via sysfs. Summary: These patches avoid softlockups when a CPU gets caught in console_unlock() for a long time during heavy printing from other CPU. As is discussed in patch 3/4 it