Re: [PATCH v3 13/16] mtd: rawnand: qcom: minor code reorganization for bad block check

On 2018-05-28 12:33, Miquel Raynal wrote: Hi Abhishek, >> /* implements ecc->read_page() */ >> static int qcom_nandc_read_page(struct mtd_info *mtd, struct >> nand_chip *chip, >>uint8_t *buf, int oob_required, int page) >> @@ -2118,6 +2083,7 @@ static int

Re: [PATCH v3 13/16] mtd: rawnand: qcom: minor code reorganization for bad block check

On 2018-05-28 12:33, Miquel Raynal wrote: Hi Abhishek, >> /* implements ecc->read_page() */ >> static int qcom_nandc_read_page(struct mtd_info *mtd, struct >> nand_chip *chip, >>uint8_t *buf, int oob_required, int page) >> @@ -2118,6 +2083,7 @@ static int

Re: [PATCH 4.4 000/268] 4.4.134-stable review

On Mon, May 28, 2018 at 11:59:34AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.134 release. > There are 268 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

Re: [PATCH 4.4 000/268] 4.4.134-stable review

On Mon, May 28, 2018 at 11:59:34AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.134 release. > There are 268 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

[PATCH 3.18 120/185] btrfs: Fix possible softlock on single core machines

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Borisov [ Upstream commit 1e1c50a929bc9e49bc3f9935b92450d9e69f8158 ] do_chunk_alloc implements a loop checking whether there is a pending chunk allocation and if so

[PATCH 3.18 120/185] btrfs: Fix possible softlock on single core machines

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Borisov [ Upstream commit 1e1c50a929bc9e49bc3f9935b92450d9e69f8158 ] do_chunk_alloc implements a loop checking whether there is a pending chunk allocation and if so causes the caller

[PATCH 3.18 125/185] Btrfs: fix copy_items() return value when logging an inode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana [ Upstream commit 8434ec46c6e3232cebc25a910363b29f5c617820 ] When logging an inode, at tree-log.c:copy_items(), if we call btrfs_next_leaf() at the loop which

[PATCH 3.18 125/185] Btrfs: fix copy_items() return value when logging an inode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana [ Upstream commit 8434ec46c6e3232cebc25a910363b29f5c617820 ] When logging an inode, at tree-log.c:copy_items(), if we call btrfs_next_leaf() at the loop which checks for the

[PATCH 3.18 128/185] ACPI: acpi_pad: Fix memory leak in power saving threads

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lenny Szubowicz [ Upstream commit 8b29d29abc484d638213dd79a18a95ae7e5bb402 ] Fix once per second (round_robin_time) memory leak of about 1 KB in each acpi_pad kernel

[PATCH 3.18 129/185] powerpc/mpic: Check if cpu_possible() in mpic_physmask()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman [ Upstream commit 0834d627fbea00c1444075eb3e448e1974da452d ] In mpic_physmask() we loop over all CPUs up to 32, then get the hard SMP processor id of

[PATCH 3.18 128/185] ACPI: acpi_pad: Fix memory leak in power saving threads

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lenny Szubowicz [ Upstream commit 8b29d29abc484d638213dd79a18a95ae7e5bb402 ] Fix once per second (round_robin_time) memory leak of about 1 KB in each acpi_pad kernel idling thread that is

[PATCH 3.18 129/185] powerpc/mpic: Check if cpu_possible() in mpic_physmask()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman [ Upstream commit 0834d627fbea00c1444075eb3e448e1974da452d ] In mpic_physmask() we loop over all CPUs up to 32, then get the hard SMP processor id of that CPU. Currently

[PATCH 3.18 132/185] hwmon: (nct6775) Fix writing pwmX_mode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck [ Upstream commit 415eb2a1aaa4881cf85bd86c683356fdd8094a23 ] pwmX_mode is defined in the ABI as 0=DC mode, 1=pwm mode. The chip register bit is set to 1 for

[PATCH 3.18 131/185] parisc/pci: Switch LBA PCI bus from Hard Fail to Soft Fail mode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller [ Upstream commit b845f66f78bf42a4ce98e5cfe0e94fab41dd0742 ] Carlo Pisani noticed that his C3600 workstation behaved unstable during heavy I/O on the PCI bus with

[PATCH 3.18 132/185] hwmon: (nct6775) Fix writing pwmX_mode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck [ Upstream commit 415eb2a1aaa4881cf85bd86c683356fdd8094a23 ] pwmX_mode is defined in the ABI as 0=DC mode, 1=pwm mode. The chip register bit is set to 1 for DC mode. This got

[PATCH 3.18 131/185] parisc/pci: Switch LBA PCI bus from Hard Fail to Soft Fail mode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Helge Deller [ Upstream commit b845f66f78bf42a4ce98e5cfe0e94fab41dd0742 ] Carlo Pisani noticed that his C3600 workstation behaved unstable during heavy I/O on the PCI bus with a VIA VT6421

[PATCH 3.18 133/185] powerpc/perf: Prevent kernel address leak to userspace via BHRB buffer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan [ Upstream commit bb19af816025d495376bd76bf6fbcf4244f9a06d ] The current Branch History Rolling Buffer (BHRB) code does not check for any

[PATCH 3.18 133/185] powerpc/perf: Prevent kernel address leak to userspace via BHRB buffer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan [ Upstream commit bb19af816025d495376bd76bf6fbcf4244f9a06d ] The current Branch History Rolling Buffer (BHRB) code does not check for any privilege levels before updating

[PATCH 3.18 106/185] llc: properly handle dev_queue_xmit() return value

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit b85ab56c3f81c5a24b5a5213374f549df06430da ] llc_conn_send_pdu() pushes the skb into write queue and calls llc_conn_send_pdus() to flush

[PATCH 3.18 106/185] llc: properly handle dev_queue_xmit() return value

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit b85ab56c3f81c5a24b5a5213374f549df06430da ] llc_conn_send_pdu() pushes the skb into write queue and calls llc_conn_send_pdus() to flush them out. However, the

[PATCH 3.18 134/185] powerpc/perf: Fix kernel address leak via sampling registers

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman [ Upstream commit e1ebd0e5b9d0a10ba65e63a3514b6da8c6a5a819 ] Current code in power_pmu_disable() does not clear the sampling registers like Sampling

[PATCH 3.18 134/185] powerpc/perf: Fix kernel address leak via sampling registers

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman [ Upstream commit e1ebd0e5b9d0a10ba65e63a3514b6da8c6a5a819 ] Current code in power_pmu_disable() does not clear the sampling registers like Sampling Instruction Address

[PATCH 3.18 107/185] net: Fix untag for vlan packets without ethernet header

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Toshiaki Makita [ Upstream commit ae4745730cf8e693d354ccd4dbaf59ea440c09a9 ] In some situation vlan packets do not have ethernet headers. One example is packets

[PATCH 3.18 107/185] net: Fix untag for vlan packets without ethernet header

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Toshiaki Makita [ Upstream commit ae4745730cf8e693d354ccd4dbaf59ea440c09a9 ] In some situation vlan packets do not have ethernet headers. One example is packets from tun devices. Users can

[PATCH 3.18 108/185] net: mvneta: fix enable of all initialized RXQs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Yelena Krivosheev [ Upstream commit e81b5e01c14add8395dfba7130f8829206bb507d ] In mvneta_port_up() we enable relevant RX and TX port queues by write queues bit map to an

[PATCH 3.18 108/185] net: mvneta: fix enable of all initialized RXQs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Yelena Krivosheev [ Upstream commit e81b5e01c14add8395dfba7130f8829206bb507d ] In mvneta_port_up() we enable relevant RX and TX port queues by write queues bit map to an appropriate register.

[PATCH 3.18 100/185] selftests: ftrace: Add a testcase for string type with kprobe_event

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu [ Upstream commit 5fbdbed797b6d12d043a5121fdbc8d8b49d10e80 ] Add a testcase for string type with kprobe event. This tests good/bad syntax combinations

[PATCH 3.18 100/185] selftests: ftrace: Add a testcase for string type with kprobe_event

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu [ Upstream commit 5fbdbed797b6d12d043a5121fdbc8d8b49d10e80 ] Add a testcase for string type with kprobe event. This tests good/bad syntax combinations and also the traced

[PATCH 3.18 146/185] i2c: mv64xxx: Apply errata delay only in standard mode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Gregory CLEMENT [ Upstream commit 31184d8c6ea49ea0676d100cdd7e1f102ad025b5 ] The errata FE-8471889 description has been updated. There is still a timing violation

[PATCH 3.18 146/185] i2c: mv64xxx: Apply errata delay only in standard mode

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Gregory CLEMENT [ Upstream commit 31184d8c6ea49ea0676d100cdd7e1f102ad025b5 ] The errata FE-8471889 description has been updated. There is still a timing violation for repeated start. But the

[PATCH 3.18 136/185] net/mlx5: Protect from command bit overflow

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit 957f6ba8adc7be401a74ccff427e4cfd88d3bfcb ] The system with CONFIG_UBSAN enabled on produces the following error during driver

[PATCH 3.18 136/185] net/mlx5: Protect from command bit overflow

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit 957f6ba8adc7be401a74ccff427e4cfd88d3bfcb ] The system with CONFIG_UBSAN enabled on produces the following error during driver initialization. The reason to

[PATCH 3.18 151/185] usb: gadget: ffs: Let setup() return USB_GADGET_DELAYED_STATUS

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen [ Upstream commit 946ef68ad4e45aa048a5fb41ce8823ed29da866a ] Some UDC drivers (like the DWC3) expect that the response to a setup() request is queued from

[PATCH 3.18 151/185] usb: gadget: ffs: Let setup() return USB_GADGET_DELAYED_STATUS

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen [ Upstream commit 946ef68ad4e45aa048a5fb41ce8823ed29da866a ] Some UDC drivers (like the DWC3) expect that the response to a setup() request is queued from within the setup

[PATCH 3.18 149/185] PCI: Restore config space on runtime resume despite being unbound

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "Rafael J. Wysocki" [ Upstream commit 5775b843a619b3c93f946e2b55a208d9f0f48b59 ] We leave PCI devices not bound to a driver in D0 during runtime suspend. But they may have

[PATCH 3.18 149/185] PCI: Restore config space on runtime resume despite being unbound

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "Rafael J. Wysocki" [ Upstream commit 5775b843a619b3c93f946e2b55a208d9f0f48b59 ] We leave PCI devices not bound to a driver in D0 during runtime suspend. But they may have a parent which is

[PATCH 3.18 150/185] usb: dwc2: Fix interval type issue

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Grigor Tovmasyan [ Upstream commit 12814a3f8f9b247531d7863170cc82b3fe4218fd ] The maximum value that unsigned char can hold is 255, meanwhile the maximum value

[PATCH 3.18 150/185] usb: dwc2: Fix interval type issue

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Grigor Tovmasyan [ Upstream commit 12814a3f8f9b247531d7863170cc82b3fe4218fd ] The maximum value that unsigned char can hold is 255, meanwhile the maximum value of interval is

Re: [PATCH] powerpc/Makefile: fix build failure by disabling attribute-alias warning

On Mon, May 28, 2018 at 5:07 PM, Segher Boessenkool wrote: > On Mon, May 28, 2018 at 02:39:37PM +, Christophe Leroy wrote: >> In file included from arch/powerpc/kernel/syscalls.c:24: >> ./include/linux/syscalls.h:233:18: warning: 'sys_mmap2' alias between >>

[PATCH 3.18 153/185] perf/core: Fix perf_output_read_group()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra [ Upstream commit 9e5b127d6f33468143d90c8a45ca12410e4c3fa7 ] Mark reported his arm64 perf fuzzer runs sometimes splat like:

[PATCH 3.18 153/185] perf/core: Fix perf_output_read_group()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra [ Upstream commit 9e5b127d6f33468143d90c8a45ca12410e4c3fa7 ] Mark reported his arm64 perf fuzzer runs sometimes splat like: armv8pmu_read_counter+0x1e8/0x2d8

Re: [PATCH] powerpc/Makefile: fix build failure by disabling attribute-alias warning

On Mon, May 28, 2018 at 5:07 PM, Segher Boessenkool wrote: > On Mon, May 28, 2018 at 02:39:37PM +, Christophe Leroy wrote: >> In file included from arch/powerpc/kernel/syscalls.c:24: >> ./include/linux/syscalls.h:233:18: warning: 'sys_mmap2' alias between >> functions of incompatible types

[PATCH 3.18 137/185] ath10k: Fix kernel panic while using worker (ath10k_sta_rc_update_wk)

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Karthikeyan Periyasamy [ Upstream commit 8b2d93dd22615cb7f3046a5a2083a6f8bb8052ed ] When attempt to run worker (ath10k_sta_rc_update_wk) after the station object

[PATCH 3.18 137/185] ath10k: Fix kernel panic while using worker (ath10k_sta_rc_update_wk)

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Karthikeyan Periyasamy [ Upstream commit 8b2d93dd22615cb7f3046a5a2083a6f8bb8052ed ] When attempt to run worker (ath10k_sta_rc_update_wk) after the station object (ieee80211_sta) delete will

[PATCH 3.18 159/185] ALSA: vmaster: Propagate slave error

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai [ Upstream commit 2e2c177ca84aff092c3c96714b0f6a12900f3946 ] In slave_update() of vmaster code ignores the error from the slave get() callback and copies the

[PATCH 3.18 159/185] ALSA: vmaster: Propagate slave error

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai [ Upstream commit 2e2c177ca84aff092c3c96714b0f6a12900f3946 ] In slave_update() of vmaster code ignores the error from the slave get() callback and copies the values. It's not

[PATCH 3.18 155/185] hwmon: (pmbus/adm1275) Accept negative page register values

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck [ Upstream commit ecb29abd4cb0670c616fb563a078f25d777ce530 ] A negative page register value means that no page needs to be selected. This is used by status

[PATCH 3.18 155/185] hwmon: (pmbus/adm1275) Accept negative page register values

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck [ Upstream commit ecb29abd4cb0670c616fb563a078f25d777ce530 ] A negative page register value means that no page needs to be selected. This is used by status register read

[PATCH 3.18 162/185] media: s3c-camif: fix out-of-bounds array access

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit a398e043637a4819a0e96467bfecaabf3224dd62 ] While experimenting with older compiler versions, I ran into a warning that no longer shows up on

Re: [PATCH v5 05/10] cpufreq/schedutil: get max utilization

Hi Vincent, On 25/05/18 15:12, Vincent Guittot wrote: > Now that we have both the dl class bandwidth requirement and the dl class > utilization, we can use the max of the 2 values when agregating the > utilization of the CPU. > > Signed-off-by: Vincent Guittot > ---

[PATCH 3.18 162/185] media: s3c-camif: fix out-of-bounds array access

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit a398e043637a4819a0e96467bfecaabf3224dd62 ] While experimenting with older compiler versions, I ran into a warning that no longer shows up on gcc-4.8 or newer:

Re: [PATCH v5 05/10] cpufreq/schedutil: get max utilization

Hi Vincent, On 25/05/18 15:12, Vincent Guittot wrote: > Now that we have both the dl class bandwidth requirement and the dl class > utilization, we can use the max of the 2 values when agregating the > utilization of the CPU. > > Signed-off-by: Vincent Guittot > --- > kernel/sched/sched.h | 6

[PATCH 3.18 160/185] media: cx23885: Override 888 ImpactVCBe crystal frequency

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Brad Love [ Upstream commit 779c79d4b833ec646b0aed878da38edb45bbe156 ] Hauppauge produced a revision of ImpactVCBe using an 888, with a 25MHz crystal, instead of using

[PATCH 3.18 160/185] media: cx23885: Override 888 ImpactVCBe crystal frequency

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Brad Love [ Upstream commit 779c79d4b833ec646b0aed878da38edb45bbe156 ] Hauppauge produced a revision of ImpactVCBe using an 888, with a 25MHz crystal, instead of using the default third

[PATCH 3.18 161/185] media: cx23885: Set subdev host data to clk_freq pointer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Brad Love [ Upstream commit 5ceade1d97fc6687e050c44c257382c192f56276 ] Currently clk_freq is ignored entirely, because the cx235840 driver configures the xtal at the

[PATCH 3.18 161/185] media: cx23885: Set subdev host data to clk_freq pointer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Brad Love [ Upstream commit 5ceade1d97fc6687e050c44c257382c192f56276 ] Currently clk_freq is ignored entirely, because the cx235840 driver configures the xtal at the chip defaults. This is an

[PATCH 3.18 163/185] dmaengine: pl330: fix a race condition in case of threaded irqs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Qi Hou [ Upstream commit a3ca831249ca8c4c226e4ceafee04e280152e59d ] When booting up with "threadirqs" in command line, all irq handlers of the DMA controller pl330 will

[PATCH 3.18 166/185] rtc: tx4939: avoid unintended sign extension on a 24 bit shift

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit 347876ad47b9923ce26e686173bbf46581802ffa ] The shifting of buf[5] by 24 bits to the left will be promoted to a 32 bit signed int and

[PATCH 3.18 163/185] dmaengine: pl330: fix a race condition in case of threaded irqs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Qi Hou [ Upstream commit a3ca831249ca8c4c226e4ceafee04e280152e59d ] When booting up with "threadirqs" in command line, all irq handlers of the DMA controller pl330 will be threaded forcedly.

[PATCH 3.18 166/185] rtc: tx4939: avoid unintended sign extension on a 24 bit shift

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit 347876ad47b9923ce26e686173bbf46581802ffa ] The shifting of buf[5] by 24 bits to the left will be promoted to a 32 bit signed int and then sign-extended to an

[PATCH 3.18 165/185] staging: rtl8192u: return -ENOMEM on failed allocation of priv->oldaddr

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit e1a7418529e33bc4efc346324557251a16a3e79b ] Currently the allocation of priv->oldaddr is not null checked which will lead to

[PATCH 3.18 165/185] staging: rtl8192u: return -ENOMEM on failed allocation of priv->oldaddr

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit e1a7418529e33bc4efc346324557251a16a3e79b ] Currently the allocation of priv->oldaddr is not null checked which will lead to subsequent errors when accessing

Re: [PATCH 4.16 231/272] fanotify: Avoid lost events due to ENOMEM for unlimited queues

On Mon 28-05-18 15:39:04, Amir Goldstein wrote: > On Mon, May 28, 2018 at 1:04 PM, Greg Kroah-Hartman > wrote: > > 4.16-stable review patch. If anyone has any objections, please let me know. > > > > I do not have objections for applying this patch to stable, but

Re: [PATCH 4.16 231/272] fanotify: Avoid lost events due to ENOMEM for unlimited queues

On Mon 28-05-18 15:39:04, Amir Goldstein wrote: > On Mon, May 28, 2018 at 1:04 PM, Greg Kroah-Hartman > wrote: > > 4.16-stable review patch. If anyone has any objections, please let me know. > > > > I do not have objections for applying this patch to stable, but AFAIK > it is a correctness

Re: general protection fault in wb_workfn (2)

On Sun 27-05-18 09:47:54, Tetsuo Handa wrote: > Forwarding > http://lkml.kernel.org/r/201805251915.fgh64517.hvfjoolffmq...@i-love.sakura.ne.jp > . > > Jan Kara wrote: > > > void delayed_work_timer_fn(struct timer_list *t) > > > { > > > struct delayed_work *dwork = from_timer(dwork, t, timer);

Re: general protection fault in wb_workfn (2)

On Sun 27-05-18 09:47:54, Tetsuo Handa wrote: > Forwarding > http://lkml.kernel.org/r/201805251915.fgh64517.hvfjoolffmq...@i-love.sakura.ne.jp > . > > Jan Kara wrote: > > > void delayed_work_timer_fn(struct timer_list *t) > > > { > > > struct delayed_work *dwork = from_timer(dwork, t, timer);

Re: [External] Re: [RFC PATCH v2 00/12] get rid of GFP_ZONE_TABLE/BAD

On Fri 25-05-18 09:43:09, Huaisheng HS1 Ye wrote: > From: Michal Hocko [mailto:mho...@kernel.org] > Sent: Thursday, May 24, 2018 8:19 PM> > > > Let me try to reply your questions. > > > Exactly, GFP_ZONE_TABLE is too complicated. I think there are two > > > advantages > > > from the series of

Re: [External] Re: [RFC PATCH v2 00/12] get rid of GFP_ZONE_TABLE/BAD

On Fri 25-05-18 09:43:09, Huaisheng HS1 Ye wrote: > From: Michal Hocko [mailto:mho...@kernel.org] > Sent: Thursday, May 24, 2018 8:19 PM> > > > Let me try to reply your questions. > > > Exactly, GFP_ZONE_TABLE is too complicated. I think there are two > > > advantages > > > from the series of

Re: [PATCH] doc: document scope NOFS, NOIO APIs

On 05/28/2018 02:21 AM, Michal Hocko wrote: > On Sun 27-05-18 15:47:22, Mike Rapoport wrote: >> On Fri, May 25, 2018 at 10:16:24AM +0200, Michal Hocko wrote: >>> On Fri 25-05-18 08:17:15, Dave Chinner wrote: On Thu, May 24, 2018 at 01:43:41PM +0200, Michal Hocko wrote: >>> [...] > +FS/IO

[PATCH 3.18 144/185] ACPICA: Events: add a return on failure from acpi_hw_register_read

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Erik Schmauss [ Upstream commit b4c0de312613ca676db5bd7e696a44b56795612a ] This ensures that acpi_ev_fixed_event_detect() does not use fixed_status and and

Re: [PATCH] fs/affs: fix potential memory leak in option parsing

On Tue, May 22, 2018 at 12:24:25PM +0800, Chengguang Xu wrote: > When specifying option 'prefix' multiple times, > current option parsing will cause memory leak. > Hence, call kfree for previous one in this case. > > Signed-off-by: Chengguang Xu Thanks, the patch and others

[PATCH 3.18 167/185] serial: xuartps: Fix out-of-bounds access through DT alias

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit e7d75e18d0fc3f7193b65282b651f980c778d935 ] The cdns_uart_port[] array is indexed using a value derived from the "serialN" alias

[PATCH 3.18 139/185] virtio-net: Fix operstate for virtio when no VIRTIO_NET_F_STATUS

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jay Vosburgh [ Upstream commit bda7fab54828bbef2164bb23c0f6b1a7d05cc718 ] The operstate update logic will leave an interface in the default UNKNOWN operstate if

[PATCH 3.18 167/185] serial: xuartps: Fix out-of-bounds access through DT alias

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit e7d75e18d0fc3f7193b65282b651f980c778d935 ] The cdns_uart_port[] array is indexed using a value derived from the "serialN" alias in DT, which may lead to

Re: [PATCH] doc: document scope NOFS, NOIO APIs

On 05/28/2018 02:21 AM, Michal Hocko wrote: > On Sun 27-05-18 15:47:22, Mike Rapoport wrote: >> On Fri, May 25, 2018 at 10:16:24AM +0200, Michal Hocko wrote: >>> On Fri 25-05-18 08:17:15, Dave Chinner wrote: On Thu, May 24, 2018 at 01:43:41PM +0200, Michal Hocko wrote: >>> [...] > +FS/IO

[PATCH 3.18 144/185] ACPICA: Events: add a return on failure from acpi_hw_register_read

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Erik Schmauss [ Upstream commit b4c0de312613ca676db5bd7e696a44b56795612a ] This ensures that acpi_ev_fixed_event_detect() does not use fixed_status and and fixed_enable as uninitialized

Re: [PATCH] fs/affs: fix potential memory leak in option parsing

On Tue, May 22, 2018 at 12:24:25PM +0800, Chengguang Xu wrote: > When specifying option 'prefix' multiple times, > current option parsing will cause memory leak. > Hence, call kfree for previous one in this case. > > Signed-off-by: Chengguang Xu Thanks, the patch and others that may queue up

[PATCH 3.18 139/185] virtio-net: Fix operstate for virtio when no VIRTIO_NET_F_STATUS

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jay Vosburgh [ Upstream commit bda7fab54828bbef2164bb23c0f6b1a7d05cc718 ] The operstate update logic will leave an interface in the default UNKNOWN operstate if the interface carrier state

[PATCH 3.18 142/185] zorro: Set up z->dev.dma_mask for the DMA API

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Schmitz [ Upstream commit 55496d3fe2acd1a365c43cbd613a20ecd4d74395 ] The generic DMA API uses dev->dma_mask to check the DMA addressable memory bitmask, and

[PATCH 3.18 142/185] zorro: Set up z->dev.dma_mask for the DMA API

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Schmitz [ Upstream commit 55496d3fe2acd1a365c43cbd613a20ecd4d74395 ] The generic DMA API uses dev->dma_mask to check the DMA addressable memory bitmask, and warns if no mask is set or

[PATCH 3.18 141/185] usb: dwc3: Update DWC_usb31 GTXFIFOSIZ reg fields

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Thinh Nguyen [ Upstream commit 0cab8d26d6e5e053b2bed3356992aaa71dc93628 ] Update two GTXFIFOSIZ bit fields for the DWC_usb31 controller. TXFDEP is a 15-bit value

[PATCH 3.18 141/185] usb: dwc3: Update DWC_usb31 GTXFIFOSIZ reg fields

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Thinh Nguyen [ Upstream commit 0cab8d26d6e5e053b2bed3356992aaa71dc93628 ] Update two GTXFIFOSIZ bit fields for the DWC_usb31 controller. TXFDEP is a 15-bit value instead of 16-bit value, and

[PATCH 3.18 164/185] media: em28xx: USB bulk packet size fix

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Brad Love [ Upstream commit c7c7e8d7803406daa21e96d00c357de8b77b6764 ] Hauppauge em28xx bulk devices exhibit continuity errors and corrupted packets, when run in VMWare

[PATCH 3.18 164/185] media: em28xx: USB bulk packet size fix

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Brad Love [ Upstream commit c7c7e8d7803406daa21e96d00c357de8b77b6764 ] Hauppauge em28xx bulk devices exhibit continuity errors and corrupted packets, when run in VMWare virtual machines.

[PATCH 3.18 171/185] serial: arc_uart: Fix out-of-bounds access through DT alias

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit f9f5786987e81d166c60833edcb7d1836aa16944 ] The arc_uart_ports[] array is indexed using a value derived from the "serialN" alias

Re: [PATCH] mtd: nand: raw: atmel: add module param to avoid using dma

On 28/05/2018 at 17:52, Peter Rosin wrote: On 2018-05-28 16:27, Boris Brezillon wrote: [..] Could it just be that you're reaching the DDR bus limit. As I said previously, when you go through the CPU, and assuming you're consuming the data directly, you have: 1/ NFC SRAM -> CPU 2/ CPU -> L1

[PATCH 3.18 180/185] netlabel: If PF_INET6, check sk_buff ip header version

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Haines [ Upstream commit 213d7f94775322ba44e0bbb55ec6946e9de88cea ] When resolving a fallback label, check the sk_buff version as it is possible (e.g.

Re: [PATCH 1/2] sched: Make select_task_rq() require cpu_active() for user tasks

Hi Peter, On Mon, May 28, 2018 at 05:53:06PM +0200, Peter Zijlstra wrote: > On Mon, May 28, 2018 at 08:45:16AM -0700, Paul Burton wrote: > > > --- a/kernel/sched/core.c > > > +++ b/kernel/sched/core.c > > > @@ -1562,7 +1562,7 @@ int select_task_rq(struct task_struct *p > > >* not worry

[PATCH 3.18 171/185] serial: arc_uart: Fix out-of-bounds access through DT alias

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit f9f5786987e81d166c60833edcb7d1836aa16944 ] The arc_uart_ports[] array is indexed using a value derived from the "serialN" alias in DT, which may lead to

Re: [PATCH] mtd: nand: raw: atmel: add module param to avoid using dma

On 28/05/2018 at 17:52, Peter Rosin wrote: On 2018-05-28 16:27, Boris Brezillon wrote: [..] Could it just be that you're reaching the DDR bus limit. As I said previously, when you go through the CPU, and assuming you're consuming the data directly, you have: 1/ NFC SRAM -> CPU 2/ CPU -> L1

[PATCH 3.18 180/185] netlabel: If PF_INET6, check sk_buff ip header version

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Richard Haines [ Upstream commit 213d7f94775322ba44e0bbb55ec6946e9de88cea ] When resolving a fallback label, check the sk_buff version as it is possible (e.g. SCTP) to have family = PF_INET6

Re: [PATCH 1/2] sched: Make select_task_rq() require cpu_active() for user tasks

Hi Peter, On Mon, May 28, 2018 at 05:53:06PM +0200, Peter Zijlstra wrote: > On Mon, May 28, 2018 at 08:45:16AM -0700, Paul Burton wrote: > > > --- a/kernel/sched/core.c > > > +++ b/kernel/sched/core.c > > > @@ -1562,7 +1562,7 @@ int select_task_rq(struct task_struct *p > > >* not worry

[PATCH 3.18 182/185] scsi: lpfc: Fix soft lockup in lpfc worker thread during LIP testing

3.18-stable review patch. If anyone has any objections, please let me know. -- From: James Smart [ Upstream commit 161df4f09987ae2e9f0f97f0b38eee298b4a39ff ] During link bounce testing in a point-to-point topology, the host may enter a soft lockup on the

[PATCH 3.18 182/185] scsi: lpfc: Fix soft lockup in lpfc worker thread during LIP testing

3.18-stable review patch. If anyone has any objections, please let me know. -- From: James Smart [ Upstream commit 161df4f09987ae2e9f0f97f0b38eee298b4a39ff ] During link bounce testing in a point-to-point topology, the host may enter a soft lockup on the lpfc_worker thread:

[PATCH 3.18 135/185] tools/thermal: tmon: fix for segfault

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Frank Asseg [ Upstream commit 6c59f64b7ecf2bccbe73931d7d573d66ed13b537 ] Fixes a segfault occurring when e.g. is pressed multiple times in the ncurses tmon

[PATCH 3.18 135/185] tools/thermal: tmon: fix for segfault

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Frank Asseg [ Upstream commit 6c59f64b7ecf2bccbe73931d7d573d66ed13b537 ] Fixes a segfault occurring when e.g. is pressed multiple times in the ncurses tmon application. The segfault is

[PATCH 3.18 184/185] regulator: of: Add a missing of_node_put() in an error handling path of of_regulator_match()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 30966861a7a2051457be8c49466887d78cc47e97 ] If an unlikely failure in 'of_get_regulator_init_data()' occurs, we must release

[PATCH 3.18 172/185] PCI: Add function 1 DMA alias quirk for Marvell 88SE9220

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Vincent-Cross [ Upstream commit 832e4e1f76b8a84991e9db56fdcef1ebce839b8b ] Add Marvell 88SE9220 DMA quirk as found and tested on bug 42679. Link:

[PATCH 3.18 185/185] kdb: make "mdr" command repeat

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit 1e0ce03bf142454f38a5fc050bf4fd698d2d36d8 ] The "mdr" command should repeat (continue) when only Enter/Return is pressed, so make it do

[PATCH 3.18 184/185] regulator: of: Add a missing of_node_put() in an error handling path of of_regulator_match()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 30966861a7a2051457be8c49466887d78cc47e97 ] If an unlikely failure in 'of_get_regulator_init_data()' occurs, we must release the reference on the current

<    3   4   5   6   7   8   9   10   11   12   >