Hi Sean,
On 04/12/2017 11:03 PM, Sean Paul wrote:
On Wed, Apr 12, 2017 at 04:56:21PM +0800, Jeffy Chen wrote:
After unbinding drm, the user space may still owns the drm dev fd, and
may still be able to call drm ioctl.
We're using an unplugged state to prevent something like that, so let's
reus
After unbinding drm, the user space may still owns the drm dev fd, and
may still be able to call drm ioctl.
We're using an unplugged state to prevent something like that, so let's
reuse it here.
Also drop drm_unplug_dev, because it would be unused after other changes.
Verified on rk3399 chromebo
On Thu, Apr 13, 2017 at 2:08 AM, Len Brown wrote:
> Hi Rafael,
>
> Please pull these turbostat patches.
>
> thanks!
> Len Brown, Intel Open Source Technology Center
>
> The following changes since commit e3942ed8c66bcff496abee5182422cd542962d9e:
>
> tools/power turbostat: version 17.02.24 (2017-
On Wed, Apr 12, 2017 at 7:21 AM, Wolfgang Bumiller
wrote:
> Commit 1045ba77a ("net sched actions: Add support for user cookies")
> added code to net/sched/act_api.c's tcf_action_init_1 using the `tb`
> nlattr array unconditionally, while it was otherwise used as well as
> initialized only when `na
Eric Anholt writes:
> Until now, we've had to limit Raspberry Pi to 256MB of CMA memory to
> keep from triggering the hardware addressing bug between of the tile
> binner of the tile alloc memory (where the top 4 bits come from the
> tile state data array's address).
>
> To work around that and a
> On 13 Apr 2017, at 2:31 AM, Christoph Hellwig wrote:
>
> On Wed, Apr 12, 2017 at 08:42:08PM +0900, Hoeun Ryu wrote:
>>
>>> On Apr 12, 2017, at 3:02 PM, Christoph Hellwig wrote:
>>>
On Wed, Apr 12, 2017 at 02:01:59PM +0900, Hoeun Ryu wrote:
vm_area_add_early/vm_area_register_early(
Hi Kishon,
Could you please review these patches?
On 2017년 03월 28일 13:38, Chanwoo Choi wrote:
> This patch uses the resource-managed extcon API for extcon_register_notifier()
> and replaces the deprecated extcon API as following:
> - (deprecated) extcon_get_cable_state_() -> extcon_get_state()
>
On Wed, Apr 12, 2017 at 09:56:37PM +, Moore, Robert wrote:
>
>
> > -Original Message-
> > From: Guenter Roeck [mailto:li...@roeck-us.net]
> > Sent: Wednesday, April 12, 2017 2:23 PM
> > To: Moore, Robert
> > Cc: Zheng, Lv ; Wysocki, Rafael J
> > ; Len Brown ; linux-
> > a...@vger.ker
On Wed, Apr 12, 2017 at 08:40:00PM -0400, Steven Rostedt wrote:
> On Wed, 12 Apr 2017 16:48:59 -0700
> "Paul E. McKenney" wrote:
> >
> > I don't understand why schedule_idle() needs a loop given that
> > schedule_preempt_disabled() doesn't have one, but other than
>
> But it does:
>
> void __sc
Stm32f769I & stm32f746 are MCUs of stm32f7 family. Here are the major
specs of the two boards:
stm32f769I discovery board:
- Cortex-M7 core @216MHz
- 2MB mcu internal flash
- 512KB internal sram
- 16MB sdram memory
- 64MB qspi flash memory
- 4 inch w
This patch adds a call to imx_media_fill_empty_mbus_fields() in the
*_try_fmt() functions at the sink pads, to set empty field order and
colorimetry parameters.
If the field order is set to ANY, choose the currently set field order
at the sink pad. If the colorspace is set to DEFAULT, choose the
c
On Wed, 12 Apr 2017 16:48:59 -0700
"Paul E. McKenney" wrote:
>
> I don't understand why schedule_idle() needs a loop given that
> schedule_preempt_disabled() doesn't have one, but other than
But it does:
void __sched schedule_preempt_disabled(void)
{
sched_preempt_enable_no_resched();
On Wed, Apr 12, 2017 at 8:02 AM, Andrey Konovalov wrote:
> Hi,
>
> I've got the following error report while fuzzing the kernel with syzkaller.
>
> On commit 39da7c509acff13fc8cb12ec1bb20337c988ed36 (4.11-rc6).
>
> A reproducer and .config are attached.
>
> When subtracting rq->sadb_x_ipsecrequest
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/cpusallowed
head: 4ba98c7ec4094a9123d0d6aabb4497290207b518
commit: 283c753d4892b65301a831ef434b988e97269dae [6/13] sparc/sysfs: Use work
instead of affinity games
config: sparc64-allyesconfig (attached as .config)
com
On 04/06/2017 08:25 AM, Philipp Zabel wrote:
On Thu, 2017-04-06 at 16:10 +0100, Russell King - ARM Linux wrote:
On Thu, Apr 06, 2017 at 05:01:52PM +0200, Philipp Zabel wrote:
On Thu, 2017-04-06 at 15:05 +0100, Russell King - ARM Linux wrote:
On Thu, Apr 06, 2017 at 03:55:29PM +0200, Philipp
SECTION_SIZE is defined twice in the same file; also it is already
used by arch specific headers, which leads to:
mm/hmm.c:34:0: warning: "SECTION_SIZE" redefined [enabled by default]
#define SECTION_SIZE (1UL << PA_SECTION_SHIFT)
^
arch/arm64/include/asm/pgtable-hwdef.h:87:0: note: this is the
The use of "select" like this will most likely cause new
randconfig warnings and failures because the child categories
get chosen, and force select the parent, even though the parent
dependencies are not met. For further details, see "select"
in Documentation/kbuild/kconfig-language.txt file.
But
On sparc64, we see:
mm/hmm.c: In function 'hmm_vma_walk_pmd':
mm/hmm.c:371:53: error: macro "pte_index" requires 2 arguments, but only 1
given
mm/hmm.c:371:39: error: 'pte_index' undeclared (first use in this function)
...and on MIPS 64, we see:
mm/hmm.c:57:22: error: field 'mmu_notifie
The Kconfig currently controlling compilation of this code is:
mm/Kconfig:config HMM
mm/Kconfig: bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driver there is no doubt it is buil
My build coverage for non-modules adding dead modular code
tripped on this recently new addition. After removing that and
rebuilding, I saw the driver still had warnings that were independent
of the "demodular" change, which the 2nd commit fixes.
Then there was "select" usage that was bound to ca
This adds a driver for the Nokia H4+ protocol, which is used
at least on the Nokia N9, N900 & N950.
Signed-off-by: Sebastian Reichel
---
Changes since PATCHv1:
* replace __u8 and uint8_t with u8
* replace __u16 and uint16_t with u16
* drop BT_BAUDRATE_DIVIDER and use btdev->sysclk_speed * 10 i
Add binding document for serial bluetooth chips using
Nokia H4+ protocol.
Acked-by: Rob Herring
Signed-off-by: Sebastian Reichel
---
Changes since PATCHv1:
* change compatible strings
* mention active high/low state for GPIOs
---
.../devicetree/bindings/net/nokia-bluetooth.txt| 51 +++
Hi,
Here is the fourth revision of the nokia bluetooth patchset. Compared
to the previous one the following things have changed:
* Drop patch 1-8 (applied by Marcel) and update Cc/To for patchset
* Order includes in the driver alphabetically
* Explicitly include in the nokia bluetooth driver
Hi Marcel,
On Wed, Apr 12, 2017 at 10:19:21PM +0200, Marcel Holtmann wrote:
> Hi Sebastian,
>
> Here is PATCHv3 for the Nokia bluetooth patchset. I addressed all
> comments from
> Rob and Pavel regarding the serdev patches and dropped the *.dts
> patches, sin
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF will always match a legacy I2C device ID and
that the MODALIAS reported will always be of the form i2c:.
But this could c
The I2C device ID entries set a .driver_data but this data is never
looked up by the driver. So don't set it and also remove the enum.
Signed-off-by: Javier Martinez Canillas
---
Changes in v2:
- Use the correct driver in subject line.
drivers/hwmon/lm87.c | 6 ++
1 file changed, 2 insert
On Thu, Mar 30, 2017 at 1:18 AM, Christoph Hellwig wrote:
> On Wed, Mar 29, 2017 at 01:55:09PM -0700, Kees Cook wrote:
>> Prepare to mark sensitive kernel structures for randomization by making
>> sure they're using designated initializers. These were identified during
>> allyesconfig builds of x8
The copy_page is optimized memcpy for page-alinged address.
If it is used with non-page aligned address, it can corrupt memory which
means system corruption. With zram, it can happen with
1. 64K architecture
2. partial IO
3. slub debug
Partial IO need to allocate a page and zram allocates it via
Now 64K page system, zsamlloc has 257 classes so 8 class bit
is not enough. With that, it corrupts the system when zsmalloc
stores 65536byte data(ie, index number 256) so that this patch
increases class bit for simple fix for stable backport.
We should clean up this mess soon.
index size
0
In zram_rw_page, the logic to get offset is wrong by operator precedence
(i.e., "<<" is higher than "&"). With wrong offset, zram can corrupt the
user's data. This patch fixes it.
Fixes: 8c7f01025 ("zram: implement rw_page operation of zram")
Cc: sta...@vger.kernel.org
Signed-off-by: Minchan Kim
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF will always match a legacy I2C device ID and
that the MODALIAS reported will always be of the form i2c:.
But this could c
The I2C device ID entries set a .driver_data but this data is never
looked up by the driver. So don't set it and also remove the enum.
Signed-off-by: Javier Martinez Canillas
---
drivers/hwmon/lm87.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/hwmon/lm87.c
On 4/12/2017 9:33 AM, Stephen Smalley wrote:
> On Wed, 2017-04-12 at 17:19 +0200, Sebastien Buisson wrote:
>> 2017-04-12 15:58 GMT+02:00 Stephen Smalley :
>>> Even your usage of selinux_is_enabled() looks suspect; that should
>>> probably go away. Only other user of it seems to be some cred
>>> va
Stm32f769I & stm32f746 are MCUs of stm32f7 family. Here are the major
specs of the two boards:
stm32f769I discovery board:
- Cortex-M7 core @216MHz
- 2MB mcu internal flash
- 512KB internal sram
- 16MB sdram memory
- 64MB qspi flash memory
- 4 inch w
From: Len Brown
Syntax only.
The HWP CAPABILTIES and REQUEST ratios are more easily
viewed in decimal -- just multiply by 100 and you get MHz...
new:
cpu0: MSR_HWP_CAPABILITIES: 0x010c1b23 (high 35 guar 27 eff 12 low 1)
cpu0: MSR_HWP_REQUEST: 0x80002301 (min 1 max 35 des 0 epp 0x80 window 0x0 p
From: Len Brown
turbostat displays a GFXMHz column, which comes from reading
/sys/class/graphics/fb0/device/drm/card0/gt_cur_freq_mhz
But GFXMHz was not changing, even when a manual
cat /sys/class/graphics/fb0/device/drm/card0/gt_cur_freq_mhz
showed a new value.
It turns out that a rewind() on
From: Len Brown
Signed-off-by: Len Brown
---
tools/power/x86/turbostat/turbostat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/power/x86/turbostat/turbostat.c
b/tools/power/x86/turbostat/turbostat.c
index 0ad966114e58..b11294730771 100644
--- a/tools/power/x86/tur
From: Doug Smythies
Add GFX%rc6 and GFXMHz to the column descriptions section
of the turbostat man page.
Signed-off-by: Doug Smythies
Signed-off-by: Len Brown
---
tools/power/x86/turbostat/turbostat.8 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/power/x86/turbostat/turbostat.8
From: Len Brown
Most CPUs do not have a hardware c1 counter,
and so turbostat derives c1 residency:
c1 = TSC - MPERF - other_core_cstate_counters
As it is not possible to atomically read these coutners,
measurement jitter can case this calcuation to "go negative"
when very close to 0. Turbosta
From: Len Brown
cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x00641400 (100 C)
cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x884b0800 (25 C)
cpu0: MSR_IA32_PACKAGE_THERM_INTERRUPT: 0x0003 (100 C, 100 C)
Enable the same per-core output, but hide it behind --debug
because it is too verbose on big systems.
Si
From: Len Brown
While the current SDM is silent on the matter, the Core and GFX
RAPL power meters on SKL and KBL appear to work -- so show them.
Reported-by: Yaroslav Isakov
Signed-off-by: Len Brown
---
tools/power/x86/turbostat/turbostat.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletio
Hi Rafael,
Please pull these turbostat patches.
thanks!
Len Brown, Intel Open Source Technology Center
The following changes since commit e3942ed8c66bcff496abee5182422cd542962d9e:
tools/power turbostat: version 17.02.24 (2017-03-01 00:14:26 -0500)
are available in the git repository at:
g
Hi Alex,
> -Original Message-
> From: Alexandre TORGUE
> Sent: Tuesday, April 11, 2017 12:51 AM
> To: Vikas MANOCHA ; Patrice CHOTARD
>
> Cc: open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
> ; moderated list:ARM PORT
> ; open list
> ; Mark Rutland ; Maxime
> Coquelin ; Rob
On 04/12/2017 03:10 PM, Andrew Lunn wrote:
> To give some more background and rational for this change.
>
> On a platform where we have a parent MDIO bus, backed by the
> mdio-bcm-unimac.c driver, we also register a slave MII bus (through
> net/dsa/dsa2.c) which is parented to t
On Wed, Apr 12, 2017 at 02:27:44PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> I finally got around to creating trampolines for dynamically allocated
> ftrace_ops with using synchronize_rcu_tasks(). For users of the ftrace
> function hook callbacks, like perf, that allocate t
On Wed, Apr 12, 2017 at 03:42:32PM -0700, Paul E. McKenney wrote:
> On Wed, Apr 12, 2017 at 11:50:45PM +0200, Thomas Gleixner wrote:
> > On Wed, 12 Apr 2017, Borislav Petkov wrote:
> >
> > > On Wed, Apr 12, 2017 at 08:27:05PM +, Verma, Vishal L wrote:
> > > > But isn't the atomic notifier call
On Wed, 12 Apr 2017, Shivappa Vikas wrote:
> This series has minor changes with respect to V3 addressing all your comments.
> Was wondering if there was any feedback or if we still have a chance for 4.12.
It's on my radar and should make it, unless there is some major hickup.
Thanks,
tgl
On Wed, Apr 12, 2017 at 6:25 PM, Willem de Bruijn
wrote:
> On Wed, Apr 12, 2017 at 4:47 PM, Eric Dumazet wrote:
>> On Wed, 2017-04-12 at 13:07 -0700, Cong Wang wrote:
>>> On Wed, Apr 12, 2017 at 8:39 AM, Willem de Bruijn
>>> wrote:
>>> > ===
>>> >> BUG: KASAN: use-after-free in i
On 04/12/2017 05:37 PM, Aaro Koskinen wrote:
>
> Please rather post a new version that also works with OCTEON. I don't
> think a partial driver should be merged; originally this driver was
> working fine with OCTEON so there should be no issue supporting that?!
>
Hey Aaro.
The difference is that
Since we're already using values from struct load_info, just pass this
pointer in directly and use what's needed as we need it. This allows us
to access future fields in struct load_info too.
Signed-off-by: Kees Cook
---
kernel/module.c | 22 ++
1 file changed, 10 insertions(
Accessing the mod structure (e.g. for mod->name) prior to having completed
check_modstruct_version() can result in writing garbage to the error logs
if the layout of the mod structure loaded from disk doesn't match the
running kernel's mod structure layout. This kind of mismatch will become
much mo
The mod structure is accessed for the "name" field prior to validating
sanity in check_modstruct_version(). This becomes very obvious once
struct layout randomization is happening, so instead add the module
name to modinfo and use that until the mod struct has been sanity-checked.
-Kees
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/cpusallowed
head: 4ba98c7ec4094a9123d0d6aabb4497290207b518
commit: ca631e2b69f859a8d51855b32dd45a65e78f2bfc [4/13] ia64/sn/hwperf: Use
work_on_cpu_safe()
config: ia64-allyesconfig (attached as .config)
compiler: ia64-
On Wed, Apr 12, 2017 at 09:40:38AM +0200, Linus Walleij wrote:
> On Wed, Apr 12, 2017 at 12:13 AM, Eric Anholt wrote:
> > Oh, one last thing I think we need to figure out: I'm using TIM2_CLKSEL,
> > which seems to be necessary on this platform. My understanding is that
> > this means that the pix
Hi All,
There are a few parallel efforts involving the Windows Management
Instrumentation (WMI)[1] and dependent/related drivers. I'd like to have a
round of
discussion among those of you that have been involved in this space before we
decide on a direction.
The WMI support in the kernel today f
Paolo Bonzini writes:
> - Original Message -
>> From: "Bandan Das"
>> To: "Paolo Bonzini"
>> Cc: linux-kernel@vger.kernel.org, k...@vger.kernel.org, da...@redhat.com
>> Sent: Wednesday, April 12, 2017 7:35:16 AM
>> Subject: Re: [PATCH 4/6] kvm: nVMX: support EPT accessed/dirty bits
>>
On Thu, 2017-04-13 at 07:55 +1000, NeilBrown wrote:
> On Wed, Apr 12 2017, Jeff Layton wrote:
>
>
> > +void __filemap_set_wb_error(struct address_space *mapping, int err)
>
> I was really hoping that this would be
>
> void __set_wb_error(wb_err_t *wb_err, int err)
>
> so
>
> Then nfs_contex
Hello Thomas,
This series has minor changes with respect to V3 addressing all your comments.
Was wondering if there was any feedback or if we still have a chance for 4.12.
Thanks,
Vikas
On Fri, 7 Apr 2017, Vikas Shivappa wrote:
Sending another version of MBA patch series with changes to V3
On 04/12/17 at 11:54pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> On Wed, Apr 12, 2017 at 09:40:56AM +0800, Baoquan He wrote:
> > Do you plan to merge this one as urgent?
> >
> > There's bug created about this issue on rhel, it would be great if it
> > can be put in next or merged so that we can back
On Thu, 2017-04-13 at 07:36 +1000, NeilBrown wrote:
> On Wed, Apr 12 2017, Jeff Layton wrote:
>
> > On Wed, 2017-04-12 at 07:38 -0700, Matthew Wilcox wrote:
> > > On Wed, Apr 12, 2017 at 09:01:34AM -0400, Jeff Layton wrote:
> > > > On Wed, 2017-04-12 at 08:06 -0400, Jeff Layton wrote:
> > > > > No
Now the command:
ethtool --phy-statistics eth0
will cause system crash with meassage "Unable to handle kernel NULL pointer
dereference at virtual address 0010" from:
(kszphy_get_stats) from [] (ethtool_get_phy_stats+0xd8/0x210)
(ethtool_get_phy_stats) from [] (dev_ethtool+0x5b8/0x228
On Wed, Apr 12, 2017 at 4:26 PM, Viresh Kumar wrote:
> On 11-04-17, 16:00, Rafael J. Wysocki wrote:
>> On Tue, Apr 11, 2017 at 12:35 PM, Viresh Kumar
>> wrote:
>> > On 29-03-17, 23:28, Rafael J. Wysocki wrote:
>> >> On Thursday, March 09, 2017 05:15:15 PM Viresh Kumar wrote:
>> >> > @@ -216,7 +2
From: Bodong Wang
Sometimes it is not desirable to probe the virtual functions after
SRIOV is enabled. This can save host side resource usage by VF
instances which would be eventually probed to VMs.
Add a new PCI sysfs interface "sriov_drivers_autoprobe" to control
that from the PF, all current
On Tue, Apr 11, 2017 at 02:00:21PM -0700, Eric Anholt wrote:
> Russell King - ARM Linux writes:
>
> > On Tue, Apr 11, 2017 at 09:06:31AM -0700, Eric Anholt wrote:
> >> Russell King - ARM Linux writes:
> >>
> >> > On Mon, Apr 10, 2017 at 06:18:01PM -0700, Eric Anholt wrote:
> >> >> v5: Move regi
On Wed, Apr 12, 2017 at 04:38:12PM -0400, Aaron Conole wrote:
> The sync_refresh_period variable is unsigned, so it can never be < 0.
>
> Signed-off-by: Aaron Conole
Thanks Aaron,
I have applied this to ipvs-next after updating the prefix to "ipvs:".
On Wed, Apr 12, 2017 at 10:28:08PM +0200, luca abeni wrote:
> On Wed, 12 Apr 2017 16:28:02 +0100
> Juri Lelli wrote:
>
> > Hi Paul,
> >
> > On 12/04/17 08:15, Paul E. McKenney wrote:
> > > Hello!
> > >
> > > On the unlikely off-chance that this is new news...
> > >
> >
> > It is actually ne
On Wed, Apr 12, 2017 at 11:50:45PM +0200, Thomas Gleixner wrote:
> On Wed, 12 Apr 2017, Borislav Petkov wrote:
>
> > On Wed, Apr 12, 2017 at 08:27:05PM +, Verma, Vishal L wrote:
> > > But isn't the atomic notifier call chain always called in atomic
> > > context?
> >
> > No, it isn't. We're c
On Thu, 2017-04-13 at 08:14 +1000, NeilBrown wrote:
> On Wed, Apr 12 2017, Jeff Layton wrote:
>
> > Now that we have a better way to store and report errors that occur
> > during writeback, we need to convert the existing codebase to use it. We
> > could just adapt all of the filesystem code and r
This makes it easier for job control to become optional and/or usable
independently from tty_io.c, as well as providing a nice purpose
separation. No logical changes from this patch.
Signed-off-by: Nicolas Pitre
---
drivers/tty/Makefile | 2 +-
drivers/tty/tty_io.c | 547 +---
All the console driver handling code lives in printk.c.
Move console_init() there as well so console support can still be used
when the TTY code is configured out. No logical changes from this patch.
Signed-off-by: Nicolas Pitre
---
drivers/tty/tty_io.c| 24
include/
To allow reuse without the rest of the tty_ioctl code.
No logical changes from this patch.
Signed-off-by: Nicolas Pitre
---
drivers/tty/Makefile | 3 +-
drivers/tty/tty_baudrate.c | 232 +
drivers/tty/tty_ioctl.c| 222 --
Move 21285 entry down alongside other UART drivers to be more consistent
with the rest of the file. It is kept before 8250 though, to preserve the
existing link ordering between those two.
Signed-off-by: Nicolas Pitre
---
drivers/tty/serial/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 de
Those are, I hope, fairly uncontrovertial patches that should require very
little review as they mostly do code movement providing nice cleanups.
No logical changes are introduced by those patches.
My minitty patch series is based on top of this, and given the timing,
I don't expect it to go upstr
Hi,
On Thu, Mar 30, 2017 at 05:31:22PM +0200, Jan Glauber wrote:
> Hi Ulf,
>
> we have a bug on some Octeon plattforms so I removed the Octeon driver for now
> (but kept the DT bindings for it). We'll submit the Octeon driver later when
> we've fixed the issue.
Please rather post a new version t
Commit-ID: 84bbabc3a452e8085cfbd745ff0bff2b89074417
Gitweb: http://git.kernel.org/tip/84bbabc3a452e8085cfbd745ff0bff2b89074417
Author: Juergen Gross
AuthorDate: Wed, 12 Apr 2017 16:36:34 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 13 Apr 2017 00:26:30 +0200
x86/mm: Fix dump paget
On Wed, Apr 12, 2017 at 03:26:19PM -0700, Luck, Tony wrote:
> We can futz with that and have them specify which chain (or both)
> that they want to be added to.
Well, I didn't want the atomic chain to be a notifier because we can
keep it simple and non-blocking. Only the process context one will b
Since commit c3f0d0bc5b01 ("kbuild, LLVMLinux: Add -Werror to
cc-option to support clang"), cc-option and friends work correctly
for clang.
However, the combination of -Werror and -Wno-unknown-warning-option
makes clang happy with any unknown warning options.
Once -Wno-unknown-warning-option is a
On Wed, Apr 12, 2017 at 4:47 PM, Eric Dumazet wrote:
> On Wed, 2017-04-12 at 13:07 -0700, Cong Wang wrote:
>> On Wed, Apr 12, 2017 at 8:39 AM, Willem de Bruijn
>> wrote:
>> > ===
>> >> BUG: KASAN: use-after-free in ipv4_datagram_support_cmsg
>> >> net/ipv4/ip_sockglue.c:500 [inlin
On Thu, Apr 13, 2017 at 12:16:39AM +0200, Borislav Petkov wrote:
> ... and it is midnight here so I could be talking crap but we probably
> should really split the reporting "chain" into two:
This shouldn't be too painful. Users ask to be put on the chain via
the wrapper:
void mce_register_decode
On Wed, Apr 12, 2017 at 11:47:49PM +0200, Borislav Petkov wrote:
> so we need to think about something better to handle events down the
> whole chain. Maybe route events from the atomic path to the blocking
> path where the sleeping notifier callbacks can sleep as much as they
> want to...
... and
On Wed, Apr 12 2017, Jeff Layton wrote:
> Now that we have a better way to store and report errors that occur
> during writeback, we need to convert the existing codebase to use it. We
> could just adapt all of the filesystem code and related infrastructure
> to the new API, but that's a lot of ch
> >>> To give some more background and rational for this change.
> >>>
> >>> On a platform where we have a parent MDIO bus, backed by the
> >>> mdio-bcm-unimac.c driver, we also register a slave MII bus (through
> >>> net/dsa/dsa2.c) which is parented to this UniMAC MDIO bus through an
> >>> assign
On Wed, 2017-04-12 at 11:09 -0600, Logan Gunthorpe wrote:
>
> > Do you handle funky address translation too ? IE. the fact that the PCI
> > addresses aren't the same as the CPU physical addresses for a BAR ?
>
> No, we use the CPU physical address of the BAR. If it's not mapped that
> way we can'
> -Original Message-
> From: Guenter Roeck [mailto:li...@roeck-us.net]
> Sent: Wednesday, April 12, 2017 2:23 PM
> To: Moore, Robert
> Cc: Zheng, Lv ; Wysocki, Rafael J
> ; Len Brown ; linux-
> a...@vger.kernel.org; de...@acpica.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] AC
On Wed, Apr 12 2017, Jeff Layton wrote:
> +void __filemap_set_wb_error(struct address_space *mapping, int err)
I was really hoping that this would be
void __set_wb_error(wb_err_t *wb_err, int err)
so
Then nfs_context_set_write_error could become
static void nfs_context_set_write_error(stru
On Wed, 12 Apr 2017, Tony Luck wrote:
> On Wed, Apr 12, 2017 at 5:26 AM, David Woodhouse wrote:
> > From: David Woodhouse
> >
> > Now that we eliminated the different behaviour in separately-reviewable
> > commits, we can switch IA64 to the generic implementation.
> >
> > Signed-off-by: David Wo
Hi Baoquan,
On Wed, Apr 12, 2017 at 09:40:56AM +0800, Baoquan He wrote:
> Do you plan to merge this one as urgent?
>
> There's bug created about this issue on rhel, it would be great if it
> can be put in next or merged so that we can back port it.
No, I am not sending this for v4.11, because th
On Wed, 12 Apr 2017, Borislav Petkov wrote:
> On Wed, Apr 12, 2017 at 08:27:05PM +, Verma, Vishal L wrote:
> > But isn't the atomic notifier call chain always called in atomic
> > context?
>
> No, it isn't. We're calling it in normal process context in
> mce_gen_pool_process() too.
>
> So th
Hi Paolo,
[auto build test ERROR on block/for-next]
[also build test ERROR on v4.11-rc6 next-20170412]
[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/commits/Paolo-Valente/Introduce-the-BFQ-I-O
> -Original Message-
> From: Paul Menzel [mailto:pmen...@molgen.mpg.de]
> Sent: Wednesday, April 12, 2017 2:27 PM
> To: Moore, Robert
> Cc: Jarkko Sakkinen ; Maciej S.
> Szmigiero ; linux-kernel@vger.kernel.org;
> Arthur Heymans ; tpmdd-de...@lists.sourceforge.net;
> gnu...@no-log.org; Z
On 04/11/2017 04:23 PM, Florian Fainelli wrote:
> On 04/11/2017 04:14 PM, Andrew Lunn wrote:
>>> To give some more background and rational for this change.
>>>
>>> On a platform where we have a parent MDIO bus, backed by the
>>> mdio-bcm-unimac.c driver, we also register a slave MII bus (through
>>
On Wed, Apr 12, 2017 at 02:19:32PM -0700, Luck, Tony wrote:
> On Wed, Apr 12, 2017 at 11:12:21PM +0200, Thomas Gleixner wrote:
> > There is another solution:
> >
> > Convert the notifier to a blocking notifier and in the panic case, ignore
> > the locking and invoke the notifier chain directly. Th
On Wed, Apr 12, 2017 at 5:26 AM, David Woodhouse wrote:
> From: David Woodhouse
>
> Now that we eliminated the different behaviour in separately-reviewable
> commits, we can switch IA64 to the generic implementation.
>
> Signed-off-by: David Woodhouse
Well it builds and boots on my last remaini
On Wed, Apr 12 2017, Jeff Layton wrote:
> On Wed, 2017-04-12 at 07:38 -0700, Matthew Wilcox wrote:
>> On Wed, Apr 12, 2017 at 09:01:34AM -0400, Jeff Layton wrote:
>> > On Wed, 2017-04-12 at 08:06 -0400, Jeff Layton wrote:
>> > > Not sure what to do here just yet.
>> > >
>> > > Signed-off-by: Jeff
Dear Robert,
Thank you for looking into this.
On 2017-04-12 17:54, Moore, Robert wrote:
And probably the dmesg if error messages appear in there.
Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please
find the output of `sudo acpidump` attached.
[…]
Kind regards,
Pau
On Tue, 11 Apr 2017, Vlastimil Babka wrote:
> > The fallback was only intended for a cpuset on which boundaries are not
> > enforced
> > in critical conditions (softwall). A hardwall cpuset (CS_MEM_HARDWALL)
> > should fail the allocation.
>
> Hmm just to clarify - I'm talking about ignoring the
On Wed, Apr 12, 2017 at 03:29:55PM +, Moore, Robert wrote:
> The ACPICA mutex functions are based on the host OS functions, so they don't
> really buy you anything. You should just use the native Linux functions.
>
You mean they don't really acquire the requested ACPI mutex,
and the underlyi
Otherwise, we can see stale fsync/dentry mark given by previous calls, resulting
in giving up roll-forward recovery due to wrong dentry mark.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/node.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index 9422dd252813..a
We'd better allocate atomic writes to hot_data zone.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 4731eb587e06..0ac833dd2634 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -1531,6 +1531,7 @@ static in
If all the threads are waiting for checkpoint, we have no chance to flush
required dirty pages.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
index 9db92990f193..800be94f8cb3 100644
--- a/fs/
101 - 200 of 953 matches
Mail list logo
