* linux-next: build failure after merge of the drm-intel tree
From: Stephen Rothwell @ 2016-05-23 2:24 UTC (permalink / raw)
To: Daniel Vetter, intel-gfx, dri-devel; +Cc: linux-next, linux-kernel
Hi all,
After merging the drm-intel tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/gpu/drm/i915/i915_trace.h:10:0,
from drivers/gpu/drm/i915/i915_drv.h:2735,
from drivers/gpu/drm/i915/i915_drv.c:34:
drivers/gpu/drm/i915/intel_drv.h:36:41: fatal error: drm/drm_dp_dual_mode_helper.h: No such file or directory
Caused by commit
8d87410a019f ("drm/i915: Respect DP++ adaptor TMDS clock limit")
I have used the drm-intel tree from next-20160520 for today.
--
Cheers,
Stephen Rothwell
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply
* Re: Crashes in -next due to 'phy: add support for a reset-gpio specification'
From: Guenter Roeck @ 2016-05-23 1:06 UTC (permalink / raw)
To: Uwe Kleine-König
Cc: linux-next@vger.kernel.org, Network Development,
linux-kernel@vger.kernel.org, David S. Miller, Linus Walleij,
linux-gpio
In-Reply-To: <20160522182112.GC23704@pengutronix.de>
On 05/22/2016 11:21 AM, Uwe Kleine-König wrote:
> Hello Guenter,
>
> [extending Cc: a bit]
>
> On Sun, May 22, 2016 at 08:41:23AM -0700, Guenter Roeck wrote:
>> On 05/22/2016 03:10 AM, Uwe Kleine-König wrote:
>>> On Tue, May 17, 2016 at 09:37:11PM -0700, Guenter Roeck wrote:
>>>> [ 9.366256] libphy: ethoc-mdio: probed
>>>> [ 9.367389] (null): could not attach to PHY
>>>> [ 9.368555] (null): failed to probe MDIO bus
>>>> [ 9.371540] Unable to handle kernel paging request at virtual address 0000001c
>>>> [ 9.371540] pc = d0320926, ra = 903209d1
>>>> [ 9.375358] Oops: sig: 11 [#1]
>>>> [ 9.376081] PREEMPT
>>>> [ 9.377080] CPU: 0 PID: 1 Comm: swapper Not tainted 4.6.0-next-20160517 #1
>>>> [ 9.378397] task: d7c2c000 ti: d7c30000 task.ti: d7c30000
>>>> [ 9.379394] a00: 903209d1 d7c31bd0 d7fb5810 00000001 00000000 00000000 d7f45c00 d7c31bd0
>>>> [ 9.382298] a08: 00000000 00000000 00000000 00000000 00060100 d04b0c10 d7f45dfc d7c31bb0
>>>> [ 9.385732] pc: d0320926, ps: 00060110, depc: 00000018, excvaddr: 0000001c
>>>> [ 9.387061] lbeg: d0322e35, lend: d0322e57 lcount: 00000000, sar: 00000011
>>>> [ 9.388173]
>>>> Stack: d7c31be0 00060700 d7f45c00 d7c31bd0 9021d509 d7c31c30 d7f45c00 00000000
>>>> d0485dcc d0485dcc d7fb5810 d7c2c000 00000000 d7c31c30 d7f45c00 d025befc
>>>> d0485dcc d7c30000 d7f45c34 d7c31bf0 9021c985 d7c31c50 d7f45c00 d7f45c34
>>>> [ 9.396652] Call Trace:
>>>> [ 9.397469] [<d021d4d9>] __device_release_driver+0x7d/0x98
>>>> [ 9.398869] [<d021d509>] device_release_driver+0x15/0x20
>>>> [ 9.400247] [<d021c985>] bus_remove_device+0xc1/0xd4
>>>> [ 9.401569] [<d021a935>] device_del+0x109/0x15c
>>>> [ 9.402794] [<d025c3f9>] phy_mdio_device_remove+0xd/0x18
>>>> [ 9.404124] [<d025d264>] mdiobus_unregister+0x40/0x5c
>>>> [ 9.405444] [<d025ff44>] ethoc_probe+0x534/0x5b8
>>>> [ 9.406742] [<d021e2e0>] platform_drv_probe+0x28/0x48
>>>> [ 9.408122] [<d021d1e5>] driver_probe_device+0x101/0x234
>>>> [ 9.409499] [<d021d395>] __driver_attach+0x7d/0x98
>>>> [ 9.410809] [<d021bd80>] bus_for_each_dev+0x30/0x5c
>>>> [ 9.412104] [<d021cdf0>] driver_attach+0x14/0x18
>>>> [ 9.413385] [<d021ca61>] bus_add_driver+0xc9/0x198
>>>> [ 9.414686] [<d021d7d4>] driver_register+0x70/0xa0
>>>> [ 9.416001] [<d021e2b4>] __platform_driver_register+0x24/0x28
>>>> [ 9.417463] [<d04a1d34>] ethoc_driver_init+0x10/0x14
>>>> [ 9.418824] [<d00032c8>] do_one_initcall+0x80/0x1ac
>>>> [ 9.420083] [<d049386d>] kernel_init_freeable+0x131/0x198
>>>> [ 9.421504] [<d03236e8>] kernel_init+0xc/0xb0
>>>> [ 9.422693] [<d000482c>] ret_from_kernel_thread+0x8/0xc
>>>
>>> Guenter, can you please test if the following patch fixes your setup:
>>>
>>> diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
>>> index 307f72a0f2e2..efa85fb31574 100644
>>> --- a/drivers/net/phy/phy_device.c
>>> +++ b/drivers/net/phy/phy_device.c
>>> @@ -1573,14 +1573,14 @@ static int phy_probe(struct device *dev)
>>> int err = 0;
>>> struct gpio_descs *reset_gpios;
>>>
>>> - phydev->drv = phydrv;
>>> -
>>> /* take phy out of reset */
>>> reset_gpios = devm_gpiod_get_array_optional(dev, "reset",
>>> GPIOD_OUT_LOW);
>>> if (IS_ERR(reset_gpios))
>>> return PTR_ERR(reset_gpios);
>>>
>>> + phydev->drv = phydrv;
>>> +
>>> /* Disable the interrupt if the PHY doesn't support it
>>> * but the interrupt is still a valid one
>>> */
>>>
>>> This doesn't make your ethernet work, but at least the driver should
>>> fail in a clean way.
>>>
>> I tried, but it still fails with exactly the same error, meaning
>> it still crashes with the same traceback.
>
> This is strange. If probe fails the device should stay unbound and it
> shouldn't enter the if block in __device_release_driver at all.
>
>>> Together with enabling GPIOLIB this should put ethernet in a working
>>> state again.
>>>
>>
>> I am not exactly in favor of forcing GPIOLIB to be enabled for every
>> system with Ethernet support, just because a few of them may require
>> a gpio based phy reset. The same is true, really, for every other
>> driver using _optional gpiolib functions.
>>
>> Personally, I think that the _optional functions in gpiolib _should_
>> return no error if gpiolib is not configured. After all, those
>> gpio pins _are_ supposed to be optional. gpiolib should be enabled
>> for affected configurations, ie on systems with gpio support which
>> do need the optional gpio pins. Forcing gpiolib to be enabled even
>> in systems with no gpio support seems to be a bit heavy-handed.
>> It just bloats the kernel on such systems with no added benefit.
>
> That's wrong. The usage of gpio_get_optional and friends means that the
> gpio is optional for the *driver*, that is there are devices that make
> use of said gpio and others don't. For the devices where the gpio is
> specified its usage is not optional. So it must not be ignored e.g. by
> GPIOLIB=n configurations. IMHO the best would be to unconditionally
Hi Uwe,
I understand what you are saying, I just have a different perspective.
From your point of view, you consider it unacceptable if optional GPIO
pins are made unavailable by changing the configuration to GPIOLIB=n.
Ok, but that position has number of drawbacks.
Playing the system this way only works if the optional GPIO pins
are the only GPIO pins in use by the system. In almost all cases, this
will not be the case. Disabling GPIOLIB in systems really needing it
is simply not a realistic option.
As such, disabling GPIOLIB to "disable" optional GPIO pins is in most cases
quite heavy-handed. Whoever wants to "disable" those optional pins can simply
disable them by removing the respective lines from the devicetree file,
or from the ACPI DSDT. Much easier to do, with less side effects.
So, in summary, the current approach of mandating that GPIOLIB=y to be able
to use drivers with optional GPIO pins only has the effect of unnecessarily
increasing the code size for platforms with no GPIO support. Nothing else.
It doesn't prevent users from "disabling" optional GPIO pins. There are other
means to do that, from manipulating the devicetree file to manipulating
the DSDT to disabling ACPI (yes, that works too).
On top of all that, why would anyone want to play the game of "disabling"
optional GPIO pins in the first place ? The only reason I can think of is
to reduce the code size by disabling GPIOLIB, but as already mentioned
that would in almost all cases result in failures all over the place -
systems using GPIO don't usually just use drivers with optional GPIO pins.
Plus, even if that is the intended use case, its use is inconsistent.
Users can still disable ACPI, and gpiolib is perfectly happy with it, even
if the system technically supports ACPI and its DSDT has entries for optional
GPIO pins.
> enable that part of GPIOLIB such that the _optional variants do the
> following with GPIOLIB=n:
>
> if a GPIO is specified:
> return -ENOSYS
> else:
> return NULL
>
Sure. I thought about it, and had a brief look into the gpiolib code. It would
require a substantial part of the gpiolib code to be enabled, and as mentioned
it would still be inconsistent as it really only applies to devicetree and
lookup table based configurations, but not to ACPI.
The potential gain of ensuring that GPIOLIB is not accidentally disabled
just doesn't seem to be worth the effort and the cost, at least not to me.
Any platform which needs GPIOLIB should just have and keep it enabled,
and I don't really see it as such a big deal to expect users to keep that
in mind.
On the other side, I do dislike the notion of enforcing GPIOLIB=y just because
some driver(s) used by a platform use optional gpio pins.
I understand that the current approach is what it is. I just don't agree with it,
and I don't think it is particularly useful or beneficial. But it isn't really
worth arguing about either, so let's just agree to disagree.
Thanks,
Guenter
^ permalink raw reply
* Re: Crashes in -next due to 'phy: add support for a reset-gpio specification'
From: Uwe Kleine-König @ 2016-05-22 18:21 UTC (permalink / raw)
To: Guenter Roeck
Cc: linux-next@vger.kernel.org, Network Development,
linux-kernel@vger.kernel.org, David S. Miller, Linus Walleij,
linux-gpio
In-Reply-To: <5741D323.8010509@roeck-us.net>
Hello Guenter,
[extending Cc: a bit]
On Sun, May 22, 2016 at 08:41:23AM -0700, Guenter Roeck wrote:
> On 05/22/2016 03:10 AM, Uwe Kleine-König wrote:
> >On Tue, May 17, 2016 at 09:37:11PM -0700, Guenter Roeck wrote:
> >>[ 9.366256] libphy: ethoc-mdio: probed
> >>[ 9.367389] (null): could not attach to PHY
> >>[ 9.368555] (null): failed to probe MDIO bus
> >>[ 9.371540] Unable to handle kernel paging request at virtual address 0000001c
> >>[ 9.371540] pc = d0320926, ra = 903209d1
> >>[ 9.375358] Oops: sig: 11 [#1]
> >>[ 9.376081] PREEMPT
> >>[ 9.377080] CPU: 0 PID: 1 Comm: swapper Not tainted 4.6.0-next-20160517 #1
> >>[ 9.378397] task: d7c2c000 ti: d7c30000 task.ti: d7c30000
> >>[ 9.379394] a00: 903209d1 d7c31bd0 d7fb5810 00000001 00000000 00000000 d7f45c00 d7c31bd0
> >>[ 9.382298] a08: 00000000 00000000 00000000 00000000 00060100 d04b0c10 d7f45dfc d7c31bb0
> >>[ 9.385732] pc: d0320926, ps: 00060110, depc: 00000018, excvaddr: 0000001c
> >>[ 9.387061] lbeg: d0322e35, lend: d0322e57 lcount: 00000000, sar: 00000011
> >>[ 9.388173]
> >>Stack: d7c31be0 00060700 d7f45c00 d7c31bd0 9021d509 d7c31c30 d7f45c00 00000000
> >> d0485dcc d0485dcc d7fb5810 d7c2c000 00000000 d7c31c30 d7f45c00 d025befc
> >> d0485dcc d7c30000 d7f45c34 d7c31bf0 9021c985 d7c31c50 d7f45c00 d7f45c34
> >>[ 9.396652] Call Trace:
> >>[ 9.397469] [<d021d4d9>] __device_release_driver+0x7d/0x98
> >>[ 9.398869] [<d021d509>] device_release_driver+0x15/0x20
> >>[ 9.400247] [<d021c985>] bus_remove_device+0xc1/0xd4
> >>[ 9.401569] [<d021a935>] device_del+0x109/0x15c
> >>[ 9.402794] [<d025c3f9>] phy_mdio_device_remove+0xd/0x18
> >>[ 9.404124] [<d025d264>] mdiobus_unregister+0x40/0x5c
> >>[ 9.405444] [<d025ff44>] ethoc_probe+0x534/0x5b8
> >>[ 9.406742] [<d021e2e0>] platform_drv_probe+0x28/0x48
> >>[ 9.408122] [<d021d1e5>] driver_probe_device+0x101/0x234
> >>[ 9.409499] [<d021d395>] __driver_attach+0x7d/0x98
> >>[ 9.410809] [<d021bd80>] bus_for_each_dev+0x30/0x5c
> >>[ 9.412104] [<d021cdf0>] driver_attach+0x14/0x18
> >>[ 9.413385] [<d021ca61>] bus_add_driver+0xc9/0x198
> >>[ 9.414686] [<d021d7d4>] driver_register+0x70/0xa0
> >>[ 9.416001] [<d021e2b4>] __platform_driver_register+0x24/0x28
> >>[ 9.417463] [<d04a1d34>] ethoc_driver_init+0x10/0x14
> >>[ 9.418824] [<d00032c8>] do_one_initcall+0x80/0x1ac
> >>[ 9.420083] [<d049386d>] kernel_init_freeable+0x131/0x198
> >>[ 9.421504] [<d03236e8>] kernel_init+0xc/0xb0
> >>[ 9.422693] [<d000482c>] ret_from_kernel_thread+0x8/0xc
> >
> >Guenter, can you please test if the following patch fixes your setup:
> >
> >diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
> >index 307f72a0f2e2..efa85fb31574 100644
> >--- a/drivers/net/phy/phy_device.c
> >+++ b/drivers/net/phy/phy_device.c
> >@@ -1573,14 +1573,14 @@ static int phy_probe(struct device *dev)
> > int err = 0;
> > struct gpio_descs *reset_gpios;
> >
> >- phydev->drv = phydrv;
> >-
> > /* take phy out of reset */
> > reset_gpios = devm_gpiod_get_array_optional(dev, "reset",
> > GPIOD_OUT_LOW);
> > if (IS_ERR(reset_gpios))
> > return PTR_ERR(reset_gpios);
> >
> >+ phydev->drv = phydrv;
> >+
> > /* Disable the interrupt if the PHY doesn't support it
> > * but the interrupt is still a valid one
> > */
> >
> >This doesn't make your ethernet work, but at least the driver should
> >fail in a clean way.
> >
> I tried, but it still fails with exactly the same error, meaning
> it still crashes with the same traceback.
This is strange. If probe fails the device should stay unbound and it
shouldn't enter the if block in __device_release_driver at all.
> >Together with enabling GPIOLIB this should put ethernet in a working
> >state again.
> >
>
> I am not exactly in favor of forcing GPIOLIB to be enabled for every
> system with Ethernet support, just because a few of them may require
> a gpio based phy reset. The same is true, really, for every other
> driver using _optional gpiolib functions.
>
> Personally, I think that the _optional functions in gpiolib _should_
> return no error if gpiolib is not configured. After all, those
> gpio pins _are_ supposed to be optional. gpiolib should be enabled
> for affected configurations, ie on systems with gpio support which
> do need the optional gpio pins. Forcing gpiolib to be enabled even
> in systems with no gpio support seems to be a bit heavy-handed.
> It just bloats the kernel on such systems with no added benefit.
That's wrong. The usage of gpio_get_optional and friends means that the
gpio is optional for the *driver*, that is there are devices that make
use of said gpio and others don't. For the devices where the gpio is
specified its usage is not optional. So it must not be ignored e.g. by
GPIOLIB=n configurations. IMHO the best would be to unconditionally
enable that part of GPIOLIB such that the _optional variants do the
following with GPIOLIB=n:
if a GPIO is specified:
return -ENOSYS
else:
return NULL
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
^ permalink raw reply
* Re: Crashes in -next due to 'phy: add support for a reset-gpio specification'
From: Guenter Roeck @ 2016-05-22 15:41 UTC (permalink / raw)
To: Uwe Kleine-König
Cc: linux-next@vger.kernel.org, Network Development,
linux-kernel@vger.kernel.org, David S. Miller
In-Reply-To: <20160522101051.GA23704@pengutronix.de>
Hi Uwe,
On 05/22/2016 03:10 AM, Uwe Kleine-König wrote:
> Hello,
>
> On Tue, May 17, 2016 at 09:37:11PM -0700, Guenter Roeck wrote:
>> [ 9.366256] libphy: ethoc-mdio: probed
>> [ 9.367389] (null): could not attach to PHY
>> [ 9.368555] (null): failed to probe MDIO bus
>> [ 9.371540] Unable to handle kernel paging request at virtual address 0000001c
>> [ 9.371540] pc = d0320926, ra = 903209d1
>> [ 9.375358] Oops: sig: 11 [#1]
>> [ 9.376081] PREEMPT
>> [ 9.377080] CPU: 0 PID: 1 Comm: swapper Not tainted 4.6.0-next-20160517 #1
>> [ 9.378397] task: d7c2c000 ti: d7c30000 task.ti: d7c30000
>> [ 9.379394] a00: 903209d1 d7c31bd0 d7fb5810 00000001 00000000 00000000 d7f45c00 d7c31bd0
>> [ 9.382298] a08: 00000000 00000000 00000000 00000000 00060100 d04b0c10 d7f45dfc d7c31bb0
>> [ 9.385732] pc: d0320926, ps: 00060110, depc: 00000018, excvaddr: 0000001c
>> [ 9.387061] lbeg: d0322e35, lend: d0322e57 lcount: 00000000, sar: 00000011
>> [ 9.388173]
>> Stack: d7c31be0 00060700 d7f45c00 d7c31bd0 9021d509 d7c31c30 d7f45c00 00000000
>> d0485dcc d0485dcc d7fb5810 d7c2c000 00000000 d7c31c30 d7f45c00 d025befc
>> d0485dcc d7c30000 d7f45c34 d7c31bf0 9021c985 d7c31c50 d7f45c00 d7f45c34
>> [ 9.396652] Call Trace:
>> [ 9.397469] [<d021d4d9>] __device_release_driver+0x7d/0x98
>> [ 9.398869] [<d021d509>] device_release_driver+0x15/0x20
>> [ 9.400247] [<d021c985>] bus_remove_device+0xc1/0xd4
>> [ 9.401569] [<d021a935>] device_del+0x109/0x15c
>> [ 9.402794] [<d025c3f9>] phy_mdio_device_remove+0xd/0x18
>> [ 9.404124] [<d025d264>] mdiobus_unregister+0x40/0x5c
>> [ 9.405444] [<d025ff44>] ethoc_probe+0x534/0x5b8
>> [ 9.406742] [<d021e2e0>] platform_drv_probe+0x28/0x48
>> [ 9.408122] [<d021d1e5>] driver_probe_device+0x101/0x234
>> [ 9.409499] [<d021d395>] __driver_attach+0x7d/0x98
>> [ 9.410809] [<d021bd80>] bus_for_each_dev+0x30/0x5c
>> [ 9.412104] [<d021cdf0>] driver_attach+0x14/0x18
>> [ 9.413385] [<d021ca61>] bus_add_driver+0xc9/0x198
>> [ 9.414686] [<d021d7d4>] driver_register+0x70/0xa0
>> [ 9.416001] [<d021e2b4>] __platform_driver_register+0x24/0x28
>> [ 9.417463] [<d04a1d34>] ethoc_driver_init+0x10/0x14
>> [ 9.418824] [<d00032c8>] do_one_initcall+0x80/0x1ac
>> [ 9.420083] [<d049386d>] kernel_init_freeable+0x131/0x198
>> [ 9.421504] [<d03236e8>] kernel_init+0xc/0xb0
>> [ 9.422693] [<d000482c>] ret_from_kernel_thread+0x8/0xc
>
> Guenter, can you please test if the following patch fixes your setup:
>
> diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
> index 307f72a0f2e2..efa85fb31574 100644
> --- a/drivers/net/phy/phy_device.c
> +++ b/drivers/net/phy/phy_device.c
> @@ -1573,14 +1573,14 @@ static int phy_probe(struct device *dev)
> int err = 0;
> struct gpio_descs *reset_gpios;
>
> - phydev->drv = phydrv;
> -
> /* take phy out of reset */
> reset_gpios = devm_gpiod_get_array_optional(dev, "reset",
> GPIOD_OUT_LOW);
> if (IS_ERR(reset_gpios))
> return PTR_ERR(reset_gpios);
>
> + phydev->drv = phydrv;
> +
> /* Disable the interrupt if the PHY doesn't support it
> * but the interrupt is still a valid one
> */
>
> This doesn't make your ethernet work, but at least the driver should
> fail in a clean way.
>
I tried, but it still fails with exactly the same error, meaning
it still crashes with the same traceback.
> Together with enabling GPIOLIB this should put ethernet in a working
> state again.
>
I am not exactly in favor of forcing GPIOLIB to be enabled for every
system with Ethernet support, just because a few of them may require
a gpio based phy reset. The same is true, really, for every other
driver using _optional gpiolib functions.
Personally, I think that the _optional functions in gpiolib _should_
return no error if gpiolib is not configured. After all, those
gpio pins _are_ supposed to be optional. gpiolib should be enabled
for affected configurations, ie on systems with gpio support which
do need the optional gpio pins. Forcing gpiolib to be enabled even
in systems with no gpio support seems to be a bit heavy-handed.
It just bloats the kernel on such systems with no added benefit.
Thanks,
Guenter
^ permalink raw reply
* Re: Crashes in -next due to 'phy: add support for a reset-gpio specification'
From: Uwe Kleine-König @ 2016-05-22 10:10 UTC (permalink / raw)
To: Guenter Roeck
Cc: linux-next@vger.kernel.org, Network Development,
linux-kernel@vger.kernel.org, David S. Miller
In-Reply-To: <573BF177.6090507@roeck-us.net>
Hello,
On Tue, May 17, 2016 at 09:37:11PM -0700, Guenter Roeck wrote:
> [ 9.366256] libphy: ethoc-mdio: probed
> [ 9.367389] (null): could not attach to PHY
> [ 9.368555] (null): failed to probe MDIO bus
> [ 9.371540] Unable to handle kernel paging request at virtual address 0000001c
> [ 9.371540] pc = d0320926, ra = 903209d1
> [ 9.375358] Oops: sig: 11 [#1]
> [ 9.376081] PREEMPT
> [ 9.377080] CPU: 0 PID: 1 Comm: swapper Not tainted 4.6.0-next-20160517 #1
> [ 9.378397] task: d7c2c000 ti: d7c30000 task.ti: d7c30000
> [ 9.379394] a00: 903209d1 d7c31bd0 d7fb5810 00000001 00000000 00000000 d7f45c00 d7c31bd0
> [ 9.382298] a08: 00000000 00000000 00000000 00000000 00060100 d04b0c10 d7f45dfc d7c31bb0
> [ 9.385732] pc: d0320926, ps: 00060110, depc: 00000018, excvaddr: 0000001c
> [ 9.387061] lbeg: d0322e35, lend: d0322e57 lcount: 00000000, sar: 00000011
> [ 9.388173]
> Stack: d7c31be0 00060700 d7f45c00 d7c31bd0 9021d509 d7c31c30 d7f45c00 00000000
> d0485dcc d0485dcc d7fb5810 d7c2c000 00000000 d7c31c30 d7f45c00 d025befc
> d0485dcc d7c30000 d7f45c34 d7c31bf0 9021c985 d7c31c50 d7f45c00 d7f45c34
> [ 9.396652] Call Trace:
> [ 9.397469] [<d021d4d9>] __device_release_driver+0x7d/0x98
> [ 9.398869] [<d021d509>] device_release_driver+0x15/0x20
> [ 9.400247] [<d021c985>] bus_remove_device+0xc1/0xd4
> [ 9.401569] [<d021a935>] device_del+0x109/0x15c
> [ 9.402794] [<d025c3f9>] phy_mdio_device_remove+0xd/0x18
> [ 9.404124] [<d025d264>] mdiobus_unregister+0x40/0x5c
> [ 9.405444] [<d025ff44>] ethoc_probe+0x534/0x5b8
> [ 9.406742] [<d021e2e0>] platform_drv_probe+0x28/0x48
> [ 9.408122] [<d021d1e5>] driver_probe_device+0x101/0x234
> [ 9.409499] [<d021d395>] __driver_attach+0x7d/0x98
> [ 9.410809] [<d021bd80>] bus_for_each_dev+0x30/0x5c
> [ 9.412104] [<d021cdf0>] driver_attach+0x14/0x18
> [ 9.413385] [<d021ca61>] bus_add_driver+0xc9/0x198
> [ 9.414686] [<d021d7d4>] driver_register+0x70/0xa0
> [ 9.416001] [<d021e2b4>] __platform_driver_register+0x24/0x28
> [ 9.417463] [<d04a1d34>] ethoc_driver_init+0x10/0x14
> [ 9.418824] [<d00032c8>] do_one_initcall+0x80/0x1ac
> [ 9.420083] [<d049386d>] kernel_init_freeable+0x131/0x198
> [ 9.421504] [<d03236e8>] kernel_init+0xc/0xb0
> [ 9.422693] [<d000482c>] ret_from_kernel_thread+0x8/0xc
Guenter, can you please test if the following patch fixes your setup:
diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
index 307f72a0f2e2..efa85fb31574 100644
--- a/drivers/net/phy/phy_device.c
+++ b/drivers/net/phy/phy_device.c
@@ -1573,14 +1573,14 @@ static int phy_probe(struct device *dev)
int err = 0;
struct gpio_descs *reset_gpios;
- phydev->drv = phydrv;
-
/* take phy out of reset */
reset_gpios = devm_gpiod_get_array_optional(dev, "reset",
GPIOD_OUT_LOW);
if (IS_ERR(reset_gpios))
return PTR_ERR(reset_gpios);
+ phydev->drv = phydrv;
+
/* Disable the interrupt if the PHY doesn't support it
* but the interrupt is still a valid one
*/
This doesn't make your ethernet work, but at least the driver should
fail in a clean way.
Together with enabling GPIOLIB this should put ethernet in a working
state again.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
^ permalink raw reply related
* Quick loans
From: Fidelity Mortgage Loan @ 2016-05-21 22:28 UTC (permalink / raw)
To: Recipients
Loan Offer at 3%, Feel Free to REPLY back to us for more info
^ permalink raw reply
* Quick loans
From: Fidelity Mortgage Loan @ 2016-05-21 22:28 UTC (permalink / raw)
To: Recipients
Loan Offer at 3%, Feel Free to REPLY back to us for more info
^ permalink raw reply
* Re: linux-next: manual merge of the tty tree with Linus' tree
From: Greg KH @ 2016-05-21 3:26 UTC (permalink / raw)
To: Stephen Rothwell
Cc: linux-next, linux-kernel, Andrei Pistirica, Ralf Baechle,
Vladimir Murzin, Linus Torvalds
In-Reply-To: <20160520123151.0c8a7c47@canb.auug.org.au>
On Fri, May 20, 2016 at 12:31:51PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the tty tree got a conflict in:
>
> include/uapi/linux/serial_core.h
>
> between commits:
>
> 157b9394709e ("serial: pic32_uart: Add PIC32 UART driver")
> 07b75260ebc2 ("Merge branch 'upstream' of git://git.linux-mips.org/pub/scm/ralf/upstream-linus")
>
> from Linus' tree and commit:
>
> 041f031def33 ("serial: mps2-uart: add MPS2 UART driver")
>
> from the tty tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
Thanks for this, I've warned Linus to watch out for this when he merges
my tree into his.
greg k-h
^ permalink raw reply
* mmotm 2016-05-20-17-11 uploaded
From: akpm @ 2016-05-21 0:12 UTC (permalink / raw)
To: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next,
sfr, mhocko, broonie
The mm-of-the-moment snapshot 2016-05-20-17-11 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You will need quilt to apply these patches to the latest Linus release (4.x
or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
http://ozlabs.org/~akpm/mmotm/series
The file broken-out.tar.gz contains two datestamp files: .DATE and
.DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
followed by the base kernel version against which this patch series is to
be applied.
This tree is partially included in linux-next. To see which patches are
included in linux-next, consult the `series' file. Only the patches
within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
linux-next.
A git tree which contains the memory management portion of this tree is
maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
by Michal Hocko. It contains the patches which are between the
"#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
file, http://www.ozlabs.org/~akpm/mmotm/series.
A full copy of the full kernel tree with the linux-next and mmotm patches
already applied is available through git within an hour of the mmotm
release. Individual mmotm releases are tagged. The master branch always
points to the latest release, so it's constantly rebasing.
http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
To develop on top of mmotm git:
$ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
$ git remote update mmotm
$ git checkout -b topic mmotm/master
<make changes, commit>
$ git send-email mmotm/master.. [...]
To rebase a branch with older patches to a new mmotm release:
$ git remote update mmotm
$ git rebase --onto mmotm/master <topic base> topic
The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
contains daily snapshots of the -mm tree. It is updated more frequently
than mmotm, and is untested.
A git copy of this tree is available at
http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/
and use of this tree is similar to
http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above.
This mmotm tree contains the following patches against 4.6:
(patches marked "*" will be included in linux-next)
origin.patch
* mm-workingset-only-do-workingset-activations-on-reads.patch
* mm-filemap-only-do-access-activations-on-reads.patch
* mm-vmscan-reduce-size-of-inactive-file-list.patch
* vmscan-consider-classzone_idx-in-compaction_ready.patch
* mm-compaction-change-compact_-constants-into-enum.patch
* mm-compaction-cover-all-compaction-mode-in-compact_zone.patch
* mm-compaction-distinguish-compact_deferred-from-compact_skipped.patch
* mm-compaction-distinguish-between-full-and-partial-compact_complete.patch
* mm-compaction-update-compaction_result-ordering.patch
* mm-compaction-simplify-__alloc_pages_direct_compact-feedback-interface.patch
* mm-compaction-abstract-compaction-feedback-to-helpers.patch
* mm-oom-rework-oom-detection.patch
* mm-throttle-on-io-only-when-there-are-too-many-dirty-and-writeback-pages.patch
* mm-oom-protect-costly-allocations-some-more.patch
* mm-consider-compaction-feedback-also-for-costly-allocation.patch
* mm-oom-compaction-prevent-from-should_compact_retry-looping-for-ever-for-costly-orders.patch
* mm-oom-protect-costly-allocations-some-more-for-config_compaction.patch
* mm-oom_reaper-hide-oom-reaped-tasks-from-oom-killer-more-carefully.patch
* mm-oom_reaper-do-not-mmput-synchronously-from-the-oom-reaper-context.patch
* oom-consider-multi-threaded-tasks-in-task_will_free_mem.patch
* mmoom-speed-up-select_bad_process-loop.patch
* mm-thp-simplify-the-implementation-of-mk_huge_pmd.patch
* memory-failure-replace-mce-with-memory-failure.patch
* mm-memblock-move-memblock_addreserve_region-into-memblock_addreserve.patch
* mm-vmalloc-keep-a-separate-lazy-free-list.patch
* mm-fix-incorrect-pfn-passed-to-untrack_pfn-in-remap_pfn_range-v2.patch
* mm-enable-rlimit_data-by-default-with-workaround-for-valgrind.patch
* tmpfs-fix-vm_mayshare-mappings-for-nommu.patch
* mm-hugetlb_cgroup-round-limit_in_bytes-down-to-hugepage-size.patch
* mm-tighten-fault_in_pages_writeable.patch
* mm-put-activate_page_pvecs-and-others-pagevec-together.patch
* include-linux-hugetlb-clean-up-code.patch
* include-linux-hugetlbh-use-bool-instead-of-int-for-hugepage_migration_supported.patch
* mm-fix-commmets-if-sparsemem-pgdata-doesnt-have-page_ext.patch
* documentation-vm-fix-spelling-mistakes.patch
* mmwriteback-dont-use-memory-reserves-for-wb_start_writeback.patch
* use-existing-helper-to-convert-on-off-to-boolean.patch
* mm-use-unsigned-long-constant-for-page-flags.patch
* memcg-fix-stale-mem_cgroup_force_empty-comment.patch
* vmstat-get-rid-of-the-ugly-cpu_stat_off-variable-v2.patch
* mm-thp-microoptimize-compound_mapcount.patch
* mm-thp-split_huge_pmd_address-comment-improvement.patch
* z3fold-the-3-fold-allocator-for-compressed-pages.patch
* mm-memblockc-remove-unnecessary-always-true-comparison.patch
* userfaultfd-dont-pin-the-user-memory-in-userfaultfd_file_create.patch
* mm-use-phys_addr_t-for-reserve_bootmem_region-arguments.patch
* mm-make-faultaround-produce-old-ptes.patch
* mm-disable-fault-around-on-emulated-access-bit-architecture.patch
* mm-kasan-fix-to-call-kasan_free_pages-after-poisoning-page.patch
* mm-check_new_page_bad-directly-returns-in-__pg_hwpoison-case.patch
* mm-increase-safety-margin-provided-by-pf_less_throttle.patch
* mm-thp-khugepaged-should-scan-when-sleep-value-is-written.patch
* mm-page_is_guard-return-false-when-page_ext-arrays-are-not-allocated-yet.patch
* mm-compact-fix-zoneindex-in-compact.patch
* mm-migrate-increment-fail-count-on-enomem.patch
* mm-move-page_ext_init-after-all-struct-pages-are-initialized-v2.patch
* mm-kasan-initial-memory-quarantine-implementation.patch
* mm-kasan-dont-call-kasan_krealloc-from-ksize.patch
* mm-kasan-add-a-ksize-test.patch
* mm-kasan-print-name-of-mem-caller-in-report.patch
* mm-kasan-add-api-to-check-memory-regions.patch
* x86-kasan-instrument-user-memory-access-api.patch
* kasan-tests-add-tests-for-user-memory-access-functions.patch
* zsmalloc-use-first_page-rather-than-page.patch
* zsmalloc-clean-up-many-bug_on.patch
* zsmalloc-reordering-function-parameter.patch
* zsmalloc-remove-unused-pool-param-in-obj_free.patch
* zsmalloc-require-gfp-in-zs_malloc.patch
* zram-user-per-cpu-compression-streams.patch
* mm-zswap-use-workqueue-to-destroy-pool.patch
* mm-zsmalloc-dont-fail-if-cant-create-debugfs-info.patch
* zram-remove-max_comp_streams-internals.patch
* zram-introduce-per-device-debug_stat-sysfs-node.patch
* procfs-expose-umask-in-proc-pid-status.patch
* procfs-fixes-pthread-cross-thread-naming-if-pr_dumpable.patch
* mn10300-let-exit_fpu-accept-a-task.patch
* exit_thread-remove-empty-bodies.patch
* exit_thread-accept-a-task-parameter-to-be-exited.patch
* fork-free-thread-in-copy_process-on-failure.patch
* use-pid_t-instead-of-int.patch
* printk-nmi-generic-solution-for-safe-printk-in-nmi.patch
* printk-nmi-warn-when-some-message-has-been-lost-in-nmi-context.patch
* printk-nmi-increase-the-size-of-nmi-buffer-and-make-it-configurable.patch
* printk-nmi-flush-nmi-messages-on-the-system-panic.patch
* maintainers-remove-linux-listsopenriscnet.patch
* maintainers-remove-defunct-spear-mailing-list.patch
* maintainers-remove-koichi-yasutake.patch
* lib-vsprintf-simplify-uuid-printing.patch
* ima-use-%pu-to-output-uuid-in-printable-format.patch
* lib-uuid-move-generate_random_uuid-to-uuidc.patch
* lib-uuid-introduce-few-more-generic-helpers-for-uuid.patch
* lib-uuid-remove-fsf-address.patch
* sysctl-use-generic-uuid-library.patch
* efi-redefine-type-constant-macro-from-generic-code.patch
* efivars-use-generic-uuid-library.patch
* genhd-move-to-use-generic-uuid-library.patch
* ldm-use-generic-uuid-library.patch
* wmi-use-generic-uuid-library.patch
* radix-tree-introduce-radix_tree_empty.patch
* radix-tree-test-suite-fix-build.patch
* radix-tree-test-suite-add-tests-for-radix_tree_locate_item.patch
* radix-tree-test-suite-allow-testing-other-fan-out-values.patch
* radix-tree-test-suite-keep-regression-test-runs-short.patch
* radix-tree-test-suite-rebuild-when-headers-change.patch
* radix-tree-remove-unused-looping-macros.patch
* introduce-config_radix_tree_multiorder.patch
* radix-tree-add-missing-sibling-entry-functionality.patch
* radix-tree-fix-sibling-entry-insertion.patch
* radix-tree-fix-deleting-a-multi-order-entry-through-an-alias.patch
* radix-tree-remove-restriction-on-multi-order-entries.patch
* radix-tree-introduce-radix_tree_load_root.patch
* radix-tree-fix-extending-the-tree-for-multi-order-entries-at-offset-0.patch
* radix-tree-test-suite-start-adding-multiorder-tests.patch
* radix-tree-fix-several-shrinking-bugs-with-multiorder-entries.patch
* radix-tree-rewrite-__radix_tree_lookup.patch
* radix-tree-fix-multiorder-bug_on-in-radix_tree_insert.patch
* radix-tree-add-support-for-multi-order-iterating.patch
* radix-tree-test-suite-multi-order-iteration-test.patch
* radix-tree-rewrite-radix_tree_tag_set.patch
* radix-tree-rewrite-radix_tree_tag_clear.patch
* radix-tree-rewrite-radix_tree_tag_get.patch
* radix-tree-test-suite-add-multi-order-tag-test.patch
* radix-tree-fix-radix_tree_create-for-sibling-entries.patch
* radix-tree-rewrite-radix_tree_locate_item.patch
* radix-tree-add-test-for-radix_tree_locate_item.patch
* radix-tree-fix-radix_tree_range_tag_if_tagged-for-multiorder-entries.patch
* radix-tree-fix-radix_tree_dump-for-multi-order-entries.patch
* radix-tree-add-copyright-statements.patch
* drivers-hwspinlock-use-correct-radix-tree-api.patch
* radix-tree-miscellaneous-fixes.patch
* radix-tree-split-node-path-into-offset-and-height.patch
* radix-tree-replace-node-height-with-node-shift.patch
* radix-tree-remove-a-use-of-root-height-from-delete_node.patch
* radix-tree-test-suite-remove-dependencies-on-height.patch
* radix-tree-remove-root-height.patch
* radix-tree-rename-indirect_ptr-to-internal_node.patch
* radix-tree-rename-ptr_to_indirect-to-node_to_entry.patch
* radix-tree-rename-indirect_to_ptr-to-entry_to_node.patch
* radix-tree-rename-radix_tree_is_indirect_ptr.patch
* radix-tree-change-naming-conventions-in-radix_tree_shrink.patch
* radix-tree-tidy-up-next_chunk.patch
* radix-tree-tidy-up-range_tag_if_tagged.patch
* radix-tree-tidy-up-__radix_tree_create.patch
* radix-tree-introduce-radix_tree_replace_clear_tags.patch
* radix-tree-make-radix_tree_descend-more-useful.patch
* dax-move-radix_dax_-definitions-to-daxc.patch
* radix-tree-free-up-the-bottom-bit-of-exceptional-entries-for-reuse.patch
* lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean.patch
* checkpatch-add-prefer_is_enabled-test.patch
* checkpatch-improve-constant_comparison-test-for-structure-members.patch
* checkpatch-add-test-for-keywords-not-starting-on-tabstops.patch
* checkpatch-whine-about-access_once.patch
* checkpatch-advertise-the-fix-and-fix-inplace-options-more.patch
* checkpatch-add-list-types-to-show-message-types-to-show-or-ignore.patch
* checkpatch-add-support-to-check-already-applied-git-commits.patch
* checkpatch-reduce-number-of-git-log-calls-with-git.patch
* checkpatch-improve-git-commit-count-shortcut.patch
* fs-efs-fix-return-value.patch
* init-mainc-simplify-initcall_blacklisted.patch
* kprobes-add-the-tls-argument-for-j_do_fork.patch
* kprobes-add-a-new-module-parameter.patch
* kprobes-print-out-the-symbol-name-for-the-hooks.patch
i-need-old-gcc.patch
arch-alpha-kernel-systblss-remove-debug-check.patch
* arm-arch-arm-include-asm-pageh-needs-personalityh.patch
* fs-ext4-fsyncc-generic_file_fsync-call-based-on-barrier-flag.patch
* ocfs2-o2hb-add-negotiate-timer.patch
* ocfs2-o2hb-add-negotiate-timer-v2.patch
* ocfs2-o2hb-add-nego_timeout-message.patch
* ocfs2-o2hb-add-nego_timeout-message-v2.patch
* ocfs2-o2hb-add-negotiate_approve-message.patch
* ocfs2-o2hb-add-negotiate_approve-message-v2.patch
* ocfs2-o2hb-add-some-user-debug-log.patch
* ocfs2-o2hb-add-some-user-debug-log-v2.patch
* ocfs2-o2hb-dont-negotiate-if-last-hb-fail.patch
* ocfs2-o2hb-fix-hb-hung-time.patch
* block-restore-proc-partitions-to-not-display-non-partitionable-removable-devices.patch
mm.patch
* mm-add-config-option-to-select-the-initial-overcommit-mode.patch
* memory-hotplug-add-move_pfn_range.patch
* memory-hotplug-more-general-validation-of-zone-during-online.patch
* memory-hotplug-use-zone_can_shift-for-sysfs-valid_zones-attribute.patch
* mm-memblock-if-nr_new-is-0-just-return.patch
* mm-make-optimistic-check-for-swapin-readahead.patch
* mm-make-optimistic-check-for-swapin-readahead-fix-2.patch
* mm-make-swapin-readahead-to-improve-thp-collapse-rate.patch
* mm-make-swapin-readahead-to-improve-thp-collapse-rate-fix.patch
* mm-make-swapin-readahead-to-improve-thp-collapse-rate-fix-2.patch
* mm-make-swapin-readahead-to-improve-thp-collapse-rate-fix-3.patch
* mm-vmstat-calculate-particular-vm-event.patch
* mm-thp-avoid-unnecessary-swapin-in-khugepaged.patch
* mm-thp-avoid-unnecessary-swapin-in-khugepaged-fix.patch
* lib-switch-config_printk_time-to-int.patch
* printk-allow-different-timestamps-for-printktime.patch
* lib-add-crc64-ecma-module.patch
* fs-befs-datastreamc-befs_read_datastream-remove-unneeded-initialization-to-null.patch
* fs-befs-datastreamc-befs_read_lsymlink-remove-unneeded-initialization-to-null.patch
* fs-befs-datastreamc-befs_find_brun_dblindirect-remove-unneeded-initializations-to-null.patch
* fs-befs-linuxvfsc-befs_get_block-remove-unneeded-initialization-to-null.patch
* fs-befs-linuxvfsc-befs_iget-remove-unneeded-initialization-to-null.patch
* fs-befs-linuxvfsc-befs_iget-remove-unneeded-raw_inode-initialization-to-null.patch
* fs-befs-linuxvfsc-befs_iget-remove-unneeded-befs_nio-initialization-to-null.patch
* fs-befs-ioc-befs_bread_iaddr-remove-unneeded-initialization-to-null.patch
* fs-befs-ioc-befs_bread-remove-unneeded-initialization-to-null.patch
* nilfs2-constify-nilfs_sc_operations-structures.patch
* nilfs2-fix-white-space-issue-in-nilfs_mount.patch
* nilfs2-remove-space-before-comma.patch
* nilfs2-remove-fsf-mailing-address-from-gpl-notices.patch
* nilfs2-clean-up-old-e-mail-addresses.patch
* maintainers-add-web-link-for-nilfs-project.patch
* nilfs2-clarify-permission-to-replicate-the-design.patch
* nilfs2-get-rid-of-nilfs_mdt_mark_block_dirty.patch
* nilfs2-move-cleanup-code-of-metadata-file-from-inode-routines.patch
* nilfs2-replace-__attribute__packed-with-__packed.patch
* nilfs2-add-missing-line-spacing.patch
* nilfs2-clean-trailing-semicolons-in-macros.patch
* nilfs2-clean-trailing-semicolons-in-macros-fix.patch
* nilfs2-do-not-emit-extra-newline-on-nilfs_warning-and-nilfs_error.patch
* nilfs2-remove-space-before-semicolon.patch
* nilfs2-fix-code-indent-coding-style-issue.patch
* nilfs2-avoid-bare-use-of-unsigned.patch
* nilfs2-remove-unnecessary-else-after-return-or-break.patch
* nilfs2-remove-loops-of-single-statement-macros.patch
* nilfs2-fix-block-comments.patch
* wait-ptrace-assume-__wall-if-the-child-is-traced.patch
* wait-allow-sys_waitid-to-accept-__wnothread-__wclone-__wall.patch
* signal-make-oom_flags-a-bool.patch
* kernel-signalc-convert-printkkern_level-to-pr_level.patch
* signal-move-the-sig-sigrtmin-check-into-siginmasksig.patch
* allocate-idle-task-for-a-cpu-always-on-its-local-node.patch
* allocate-idle-task-for-a-cpu-always-on-its-local-node-fix.patch
* exec-remove-the-no-longer-needed-remove_arg_zero-free_arg_page.patch
* kexec-introduce-a-protection-mechanism-for-the-crashkernel-reserved-memory.patch
* kexec-provide-arch_kexec_protectunprotect_crashkres.patch
* kexec-make-a-pair-of-map-unmap-reserved-pages-in-error-path.patch
* kexec-do-a-cleanup-for-function-kexec_load.patch
* s390-kexec-consolidate-crash_map-unmap_reserved_pages-and-arch_kexec_protectunprotect_crashkres.patch
* kdump-fix-gdb-macros-work-work-with-newer-and-64-bit-kernels.patch
* kdump-vmcoreinfo-report-actual-value-of-phys_base.patch
* futex-fix-shared-futex-operations-on-nommu.patch
* rtsx_usb_ms-use-schedule_timeout_idle-in-polling-loop-v2.patch
* arch-defconfig-remove-config_resource_counters.patch
* scripts-gdb-adjust-module-reference-counter-reported-by-lx-lsmod.patch
* scripts-gdb-provide-linux-constants.patch
* scripts-gdb-provide-kernel-list-item-generators.patch
* scripts-gdb-convert-modules-usage-to-lists-functions.patch
* scripts-gdb-provide-exception-catching-parser.patch
* scripts-gdb-support-config_modules-gracefully.patch
* scripts-gdb-provide-a-dentry_name-vfs-path-helper.patch
* scripts-gdb-add-io-resource-readers.patch
* scripts-gdb-add-mount-point-list-command.patch
* scripts-gdb-add-cpu-iterators.patch
* scripts-gdb-cast-cpu-numbers-to-integer.patch
* scripts-gdb-add-a-radix-tree-parser.patch
* scripts-gdb-add-documentation-example-for-radix-tree.patch
* scripts-gdb-add-lx_thread_info_by_pid-helper.patch
* scripts-gdb-improve-types-abstraction-for-gdb-python-scripts.patch
* scripts-gdb-fix-issue-with-dmesgpy-and-python-3x.patch
* scripts-gdb-decode-bytestream-on-dmesg-for-python3.patch
* maintainers-add-co-maintainer-for-scripts-gdb.patch
* ipc-semc-fix-complex_count-vs-simple-op-race.patch
* ipc-msgc-msgsnd-use-freezable-blocking-call.patch
* msgrcv-use-freezable-blocking-call.patch
linux-next.patch
linux-next-git-rejects.patch
linux-next-rejects.patch
* mm-make-optimistic-check-for-swapin-readahead-fix.patch
* drivers-net-wireless-intel-iwlwifi-dvm-calibc-fix-min-warning.patch
* mm-make-mmap_sem-for-write-waits-killable-for-mm-syscalls.patch
* mm-make-vm_mmap-killable.patch
* mm-make-vm_munmap-killable.patch
* mm-aout-handle-vm_brk-failures.patch
* mm-elf-handle-vm_brk-error.patch
* mm-make-vm_brk-killable.patch
* mm-proc-make-clear_refs-killable.patch
* mm-fork-make-dup_mmap-wait-for-mmap_sem-for-write-killable.patch
* ipc-shm-make-shmem-attach-detach-wait-for-mmap_sem-killable.patch
* vdso-make-arch_setup_additional_pages-wait-for-mmap_sem-for-write-killable.patch
* coredump-make-coredump_wait-wait-for-mmap_sem-for-write-killable.patch
* aio-make-aio_setup_ring-killable.patch
* exec-make-exec-path-waiting-for-mmap_sem-killable.patch
* prctl-make-pr_set_thp_disable-wait-for-mmap_sem-killable.patch
* uprobes-wait-for-mmap_sem-for-write-killable.patch
* drm-i915-make-i915_gem_mmap_ioctl-wait-for-mmap_sem-killable.patch
* drm-radeon-make-radeon_mn_get-wait-for-mmap_sem-killable.patch
* drm-amdgpu-make-amdgpu_mn_get-wait-for-mmap_sem-killable.patch
* drm-amdgpu-make-amdgpu_mn_get-wait-for-mmap_sem-killable-fix.patch
* kgdb-depends-on-vt.patch
mm-add-strictlimit-knob-v2.patch
make-sure-nobodys-leaking-resources.patch
releasing-resources-with-children.patch
make-frame_pointer-default=y.patch
kernel-forkc-export-kernel_thread-to-modules.patch
mutex-subsystem-synchro-test-module.patch
slab-leaks3-default-y.patch
add-debugging-aid-for-memory-initialisation-problems.patch
workaround-for-a-pci-restoring-bug.patch
^ permalink raw reply
* Re: mmotm 2016-05-19-19-59 uploaded
From: Jan Kara @ 2016-05-20 10:31 UTC (permalink / raw)
To: Andrew Morton
Cc: Minchan Kim, mm-commits, linux-kernel, linux-mm, linux-fsdevel,
linux-next, sfr, mhocko, broonie, jack, Verma, Vishal L
In-Reply-To: <20160519223926.c2a6c169287c048ee78ec151@linux-foundation.org>
On Thu 19-05-16 22:39:26, Andrew Morton wrote:
>
> Someone stuck a load of for-4.8 stuff into -next during the merge
> window. It had better be for 4.8 anyway - it is super-late.
>
> I intend to simply ignore it and merge the for-4.7 material.
I think it was Vishal's tree (CCed) and the conflict is just a trivial
context one. So you can merge whatever you have without concern.
Honza
> On Fri, 20 May 2016 14:36:28 +0900 Minchan Kim <minchan@kernel.org> wrote:
>
> > Ccing Jan,
> >
> > dax: Remove complete_unwritten argument
> >
> > On Fri, May 20, 2016 at 02:14:17PM +0900, Minchan Kim wrote:
> > > On Thu, May 19, 2016 at 07:59:50PM -0700, akpm@linux-foundation.org wrote:
> > > > The mm-of-the-moment snapshot 2016-05-19-19-59 has been uploaded to
> > > >
> > > > http://www.ozlabs.org/~akpm/mmotm/
> > > >
> > > > mmotm-readme.txt says
> > > >
> > > > README for mm-of-the-moment:
> > > >
> > > > http://www.ozlabs.org/~akpm/mmotm/
> > > >
> > > > This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> > > > more than once a week.
> > > >
> > > > You will need quilt to apply these patches to the latest Linus release (4.x
> > > > or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> > > > http://ozlabs.org/~akpm/mmotm/series
> > > >
> > > > The file broken-out.tar.gz contains two datestamp files: .DATE and
> > > > .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> > > > followed by the base kernel version against which this patch series is to
> > > > be applied.
> > > >
> > > > This tree is partially included in linux-next. To see which patches are
> > > > included in linux-next, consult the `series' file. Only the patches
> > > > within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> > > > linux-next.
> > > >
> > > > A git tree which contains the memory management portion of this tree is
> > > > maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> > > > by Michal Hocko. It contains the patches which are between the
> > > > "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
> > > > file, http://www.ozlabs.org/~akpm/mmotm/series.
> > > >
> > > >
> > > > A full copy of the full kernel tree with the linux-next and mmotm patches
> > > > already applied is available through git within an hour of the mmotm
> > > > release. Individual mmotm releases are tagged. The master branch always
> > > > points to the latest release, so it's constantly rebasing.
> > > >
> > > > http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
> > > >
> > > > To develop on top of mmotm git:
> > > >
> > > > $ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> > > > $ git remote update mmotm
> > > > $ git checkout -b topic mmotm/master
> > > > <make changes, commit>
> > > > $ git send-email mmotm/master.. [...]
> > > >
> > > > To rebase a branch with older patches to a new mmotm release:
> > > >
> > > > $ git remote update mmotm
> > > > $ git rebase --onto mmotm/master <topic base> topic
> > > >
> > > >
> > > >
> > > >
> > > > The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
> > > > contains daily snapshots of the -mm tree. It is updated more frequently
> > > > than mmotm, and is untested.
> > > >
> > > > A git copy of this tree is available at
> > > >
> > > > http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/
> > > >
> > > > and use of this tree is similar to
> > > > http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above.
> > > >
> > >
> > > In first build, I got this.
> > >
> > > In file included from mm/filemap.c:14:0:
> > > include/linux/dax.h:14:3: error: unknown type name ___dax_iodone_t___
> > > dax_iodone_t);
> > > ^
> > > include/linux/dax.h:16:3: error: unknown type name ___dax_iodone_t___
> > > dax_iodone_t);
> > > ^
> > > include/linux/dax.h:39:5: error: unknown type name ___dax_iodone_t___
> > > dax_iodone_t di)
> > > ^
> > > In file included from mm/vmscan.c:49:0:
> > > include/linux/dax.h:14:3: error: unknown type name ___dax_iodone_t___
> > > dax_iodone_t);
> > > ^
> > > include/linux/dax.h:16:3: error: unknown type name ___dax_iodone_t___
> > > dax_iodone_t);
> > > ^
> > > include/linux/dax.h:39:5: error: unknown type name ___dax_iodone_t___
> > > dax_iodone_t di)
> > > ^
> > > In file included from mm/truncate.c:12:0:
> > > include/linux/dax.h:14:3: error: unknown type name ___dax_iodone_t___
> > > dax_iodone_t);
> > > ^
> > > include/linux/dax.h:16:3: error: unknown type name ___dax_iodone_t___
> > > dax_iodone_t);
> > > ^
> > > include/linux/dax.h:39:5: error: unknown type name ___dax_iodone_t___
> > > dax_iodone_t di)
> > > ^
> > > make[1]: *** [mm/truncate.o] Error 1
> > > make[1]: *** Waiting for unfinished jobs....
> > > make[1]: *** [mm/filemap.o] Error 1
> > > make[1]: *** [mm/vmscan.o] Error 1
> > > make: *** [mm/] Error 2
> > >
> > > --
> > > To unsubscribe, send a message with 'unsubscribe linux-mm' in
> > > the body to majordomo@kvack.org. For more info on Linux MM,
> > > see: http://www.linux-mm.org/ .
> > > Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply
* Re: Crash in -next due to 'drivers/of: Fix depth when unflattening devicetree'
From: Guenter Roeck @ 2016-05-20 9:17 UTC (permalink / raw)
To: Rob Herring; +Cc: Rhyland Klein, linux-next, linux-kernel@vger.kernel.org
In-Reply-To: <CAL_Jsq+g2T66Q7tMJq7iHncHPSk=MUfqz=zDG7-a3KtH==NLmA@mail.gmail.com>
On 05/19/2016 07:47 AM, Rob Herring wrote:
> On Wed, May 18, 2016 at 10:11 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> Hi,
>>
>> some of my ppc qemu tests crash with the following log message.
>>
>> VFS: Cannot open root device "hda" or unknown-block(0,0): error -6
>> Please append a correct "root=" boot option; here are the available partitions:
>> 0100 4096 ram0 (driver?)
>> 0101 4096 ram1 (driver?)
>> 0102 4096 ram2 (driver?)
>> 0103 4096 ram3 (driver?)
>> 0104 4096 ram4 (driver?)
>> 0105 4096 ram5 (driver?)
>> 0106 4096 ram6 (driver?)
>> 0107 4096 ram7 (driver?)
>> 0108 4096 ram8 (driver?)
>> 0109 4096 ram9 (driver?)
>> 010a 4096 ram10 (driver?)
>> 010b 4096 ram11 (driver?)
>> 010c 4096 ram12 (driver?)
>> 010d 4096 ram13 (driver?)
>> 010e 4096 ram14 (driver?)
>> 010f 4096 ram15 (driver?)
>> 1600 8383 hdc driver: ide-gd
>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
>>
>> A complete boot log is available at
>> http://kerneltests.org/builders/qemu-ppc-next/builds/408/steps/qemubuildcommand/logs/stdio
>>
>> Bisect points to commit 'drivers/of: Fix depth when unflattening devicetree'.
>> Reverting this commit fixes the problem. Bisect log is attached.
>
> I've pushed out a fix this morning with an updated version of that
> patch [1]. Please test.
>
The problem is no longer seen in next-20160520.
Thanks,
Guenter
^ permalink raw reply
* next-20160520 build: 0 failures 11 warnings (next-20160520)
From: Build bot for Mark Brown @ 2016-05-20 7:39 UTC (permalink / raw)
To: kernel-build-reports, linaro-kernel, linux-next
Tree/Branch: next-20160520
Git describe: next-20160520
Commit: 89949abc7f Add linux-next specific files for 20160520
Build Time: 78 min 17 sec
Passed: 9 / 9 (100.00 %)
Failed: 0 / 9 ( 0.00 %)
Errors: 0
Warnings: 11
Section Mismatches: 0
-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
11 warnings 0 mismatches : arm64-allmodconfig
4 warnings 0 mismatches : arm-multi_v7_defconfig
4 warnings 0 mismatches : arm-allmodconfig
5 warnings 0 mismatches : arm64-defconfig
-------------------------------------------------------------------------------
Warnings Summary: 11
4 ../drivers/net/usb/pegasus.c:475:1: warning: label 'goon' defined but not used [-Wunused-label]
4 ../drivers/net/usb/pegasus.c:446:8: warning: unused variable 'pkt_len' [-Wunused-variable]
4 ../drivers/net/usb/pegasus.c:445:6: warning: unused variable 'buf' [-Wunused-variable]
4 ../drivers/net/usb/pegasus.c:443:17: warning: unused variable 'count' [-Wunused-variable]
2 ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function]
1 ../include/soc/nps/common.h:162:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
1 ../include/soc/nps/common.h:148:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
1 ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 ../fs/gfs2/dir.c:802:9: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 ../fs/gfs2/dir.c:1021:8: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized]
===============================================================================
Detailed per-defconfig build reports below:
-------------------------------------------------------------------------------
arm64-allmodconfig : PASS, 0 errors, 11 warnings, 0 section mismatches
Warnings:
../fs/gfs2/dir.c:802:9: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized]
../fs/gfs2/dir.c:1021:8: warning: 'leaf_no' may be used uninitialized in this function [-Wmaybe-uninitialized]
../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized]
../include/soc/nps/common.h:148:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
../include/soc/nps/common.h:162:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
../drivers/net/usb/pegasus.c:475:1: warning: label 'goon' defined but not used [-Wunused-label]
../drivers/net/usb/pegasus.c:446:8: warning: unused variable 'pkt_len' [-Wunused-variable]
../drivers/net/usb/pegasus.c:445:6: warning: unused variable 'buf' [-Wunused-variable]
../drivers/net/usb/pegasus.c:443:17: warning: unused variable 'count' [-Wunused-variable]
../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized]
../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function]
-------------------------------------------------------------------------------
arm-multi_v7_defconfig : PASS, 0 errors, 4 warnings, 0 section mismatches
Warnings:
../drivers/net/usb/pegasus.c:475:1: warning: label 'goon' defined but not used [-Wunused-label]
../drivers/net/usb/pegasus.c:446:8: warning: unused variable 'pkt_len' [-Wunused-variable]
../drivers/net/usb/pegasus.c:445:6: warning: unused variable 'buf' [-Wunused-variable]
../drivers/net/usb/pegasus.c:443:17: warning: unused variable 'count' [-Wunused-variable]
-------------------------------------------------------------------------------
arm-allmodconfig : PASS, 0 errors, 4 warnings, 0 section mismatches
Warnings:
../drivers/net/usb/pegasus.c:475:1: warning: label 'goon' defined but not used [-Wunused-label]
../drivers/net/usb/pegasus.c:446:8: warning: unused variable 'pkt_len' [-Wunused-variable]
../drivers/net/usb/pegasus.c:445:6: warning: unused variable 'buf' [-Wunused-variable]
../drivers/net/usb/pegasus.c:443:17: warning: unused variable 'count' [-Wunused-variable]
-------------------------------------------------------------------------------
arm64-defconfig : PASS, 0 errors, 5 warnings, 0 section mismatches
Warnings:
../drivers/net/usb/pegasus.c:475:1: warning: label 'goon' defined but not used [-Wunused-label]
../drivers/net/usb/pegasus.c:446:8: warning: unused variable 'pkt_len' [-Wunused-variable]
../drivers/net/usb/pegasus.c:445:6: warning: unused variable 'buf' [-Wunused-variable]
../drivers/net/usb/pegasus.c:443:17: warning: unused variable 'count' [-Wunused-variable]
../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function]
-------------------------------------------------------------------------------
Passed with no errors, warnings or mismatches:
x86_64-allnoconfig
arm64-allnoconfig
arm-allnoconfig
arm-multi_v5_defconfig
x86_64-defconfig
^ permalink raw reply
* Re: linux-next: build warnings after merge of the net tree
From: David Miller @ 2016-05-20 5:57 UTC (permalink / raw)
To: sfr; +Cc: netdev, linux-next, linux-kernel, xypron.glpk
In-Reply-To: <20160520133330.12a1aa65@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 20 May 2016 13:33:30 +1000
> After merging the net tree, today's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
...
> Introduced by commit
>
> e00be9e4d0ff ("net: pegasus: remove dead coding")
This change has other problems too and I have just reverted it.
Thanks.
^ permalink raw reply
* Re: mmotm 2016-05-19-19-59 uploaded
From: Andrew Morton @ 2016-05-20 5:39 UTC (permalink / raw)
To: Minchan Kim
Cc: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next,
sfr, mhocko, broonie, jack
In-Reply-To: <20160520053628.GB6808@bbox>
Someone stuck a load of for-4.8 stuff into -next during the merge
window. It had better be for 4.8 anyway - it is super-late.
I intend to simply ignore it and merge the for-4.7 material.
On Fri, 20 May 2016 14:36:28 +0900 Minchan Kim <minchan@kernel.org> wrote:
> Ccing Jan,
>
> dax: Remove complete_unwritten argument
>
> On Fri, May 20, 2016 at 02:14:17PM +0900, Minchan Kim wrote:
> > On Thu, May 19, 2016 at 07:59:50PM -0700, akpm@linux-foundation.org wrote:
> > > The mm-of-the-moment snapshot 2016-05-19-19-59 has been uploaded to
> > >
> > > http://www.ozlabs.org/~akpm/mmotm/
> > >
> > > mmotm-readme.txt says
> > >
> > > README for mm-of-the-moment:
> > >
> > > http://www.ozlabs.org/~akpm/mmotm/
> > >
> > > This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> > > more than once a week.
> > >
> > > You will need quilt to apply these patches to the latest Linus release (4.x
> > > or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> > > http://ozlabs.org/~akpm/mmotm/series
> > >
> > > The file broken-out.tar.gz contains two datestamp files: .DATE and
> > > .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> > > followed by the base kernel version against which this patch series is to
> > > be applied.
> > >
> > > This tree is partially included in linux-next. To see which patches are
> > > included in linux-next, consult the `series' file. Only the patches
> > > within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> > > linux-next.
> > >
> > > A git tree which contains the memory management portion of this tree is
> > > maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> > > by Michal Hocko. It contains the patches which are between the
> > > "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
> > > file, http://www.ozlabs.org/~akpm/mmotm/series.
> > >
> > >
> > > A full copy of the full kernel tree with the linux-next and mmotm patches
> > > already applied is available through git within an hour of the mmotm
> > > release. Individual mmotm releases are tagged. The master branch always
> > > points to the latest release, so it's constantly rebasing.
> > >
> > > http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
> > >
> > > To develop on top of mmotm git:
> > >
> > > $ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> > > $ git remote update mmotm
> > > $ git checkout -b topic mmotm/master
> > > <make changes, commit>
> > > $ git send-email mmotm/master.. [...]
> > >
> > > To rebase a branch with older patches to a new mmotm release:
> > >
> > > $ git remote update mmotm
> > > $ git rebase --onto mmotm/master <topic base> topic
> > >
> > >
> > >
> > >
> > > The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
> > > contains daily snapshots of the -mm tree. It is updated more frequently
> > > than mmotm, and is untested.
> > >
> > > A git copy of this tree is available at
> > >
> > > http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/
> > >
> > > and use of this tree is similar to
> > > http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above.
> > >
> >
> > In first build, I got this.
> >
> > In file included from mm/filemap.c:14:0:
> > include/linux/dax.h:14:3: error: unknown type name ___dax_iodone_t___
> > dax_iodone_t);
> > ^
> > include/linux/dax.h:16:3: error: unknown type name ___dax_iodone_t___
> > dax_iodone_t);
> > ^
> > include/linux/dax.h:39:5: error: unknown type name ___dax_iodone_t___
> > dax_iodone_t di)
> > ^
> > In file included from mm/vmscan.c:49:0:
> > include/linux/dax.h:14:3: error: unknown type name ___dax_iodone_t___
> > dax_iodone_t);
> > ^
> > include/linux/dax.h:16:3: error: unknown type name ___dax_iodone_t___
> > dax_iodone_t);
> > ^
> > include/linux/dax.h:39:5: error: unknown type name ___dax_iodone_t___
> > dax_iodone_t di)
> > ^
> > In file included from mm/truncate.c:12:0:
> > include/linux/dax.h:14:3: error: unknown type name ___dax_iodone_t___
> > dax_iodone_t);
> > ^
> > include/linux/dax.h:16:3: error: unknown type name ___dax_iodone_t___
> > dax_iodone_t);
> > ^
> > include/linux/dax.h:39:5: error: unknown type name ___dax_iodone_t___
> > dax_iodone_t di)
> > ^
> > make[1]: *** [mm/truncate.o] Error 1
> > make[1]: *** Waiting for unfinished jobs....
> > make[1]: *** [mm/filemap.o] Error 1
> > make[1]: *** [mm/vmscan.o] Error 1
> > make: *** [mm/] Error 2
> >
> > --
> > To unsubscribe, send a message with 'unsubscribe linux-mm' in
> > the body to majordomo@kvack.org. For more info on Linux MM,
> > see: http://www.linux-mm.org/ .
> > Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply
* Re: mmotm 2016-05-19-19-59 uploaded
From: Minchan Kim @ 2016-05-20 5:36 UTC (permalink / raw)
To: akpm
Cc: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next,
sfr, mhocko, broonie, jack
In-Reply-To: <20160520051417.GA6808@bbox>
Ccing Jan,
dax: Remove complete_unwritten argument
On Fri, May 20, 2016 at 02:14:17PM +0900, Minchan Kim wrote:
> On Thu, May 19, 2016 at 07:59:50PM -0700, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2016-05-19-19-59 has been uploaded to
> >
> > http://www.ozlabs.org/~akpm/mmotm/
> >
> > mmotm-readme.txt says
> >
> > README for mm-of-the-moment:
> >
> > http://www.ozlabs.org/~akpm/mmotm/
> >
> > This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> > more than once a week.
> >
> > You will need quilt to apply these patches to the latest Linus release (4.x
> > or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> > http://ozlabs.org/~akpm/mmotm/series
> >
> > The file broken-out.tar.gz contains two datestamp files: .DATE and
> > .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> > followed by the base kernel version against which this patch series is to
> > be applied.
> >
> > This tree is partially included in linux-next. To see which patches are
> > included in linux-next, consult the `series' file. Only the patches
> > within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> > linux-next.
> >
> > A git tree which contains the memory management portion of this tree is
> > maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> > by Michal Hocko. It contains the patches which are between the
> > "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
> > file, http://www.ozlabs.org/~akpm/mmotm/series.
> >
> >
> > A full copy of the full kernel tree with the linux-next and mmotm patches
> > already applied is available through git within an hour of the mmotm
> > release. Individual mmotm releases are tagged. The master branch always
> > points to the latest release, so it's constantly rebasing.
> >
> > http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
> >
> > To develop on top of mmotm git:
> >
> > $ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> > $ git remote update mmotm
> > $ git checkout -b topic mmotm/master
> > <make changes, commit>
> > $ git send-email mmotm/master.. [...]
> >
> > To rebase a branch with older patches to a new mmotm release:
> >
> > $ git remote update mmotm
> > $ git rebase --onto mmotm/master <topic base> topic
> >
> >
> >
> >
> > The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
> > contains daily snapshots of the -mm tree. It is updated more frequently
> > than mmotm, and is untested.
> >
> > A git copy of this tree is available at
> >
> > http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/
> >
> > and use of this tree is similar to
> > http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above.
> >
>
> In first build, I got this.
>
> In file included from mm/filemap.c:14:0:
> include/linux/dax.h:14:3: error: unknown type name ‘dax_iodone_t’
> dax_iodone_t);
> ^
> include/linux/dax.h:16:3: error: unknown type name ‘dax_iodone_t’
> dax_iodone_t);
> ^
> include/linux/dax.h:39:5: error: unknown type name ‘dax_iodone_t’
> dax_iodone_t di)
> ^
> In file included from mm/vmscan.c:49:0:
> include/linux/dax.h:14:3: error: unknown type name ‘dax_iodone_t’
> dax_iodone_t);
> ^
> include/linux/dax.h:16:3: error: unknown type name ‘dax_iodone_t’
> dax_iodone_t);
> ^
> include/linux/dax.h:39:5: error: unknown type name ‘dax_iodone_t’
> dax_iodone_t di)
> ^
> In file included from mm/truncate.c:12:0:
> include/linux/dax.h:14:3: error: unknown type name ‘dax_iodone_t’
> dax_iodone_t);
> ^
> include/linux/dax.h:16:3: error: unknown type name ‘dax_iodone_t’
> dax_iodone_t);
> ^
> include/linux/dax.h:39:5: error: unknown type name ‘dax_iodone_t’
> dax_iodone_t di)
> ^
> make[1]: *** [mm/truncate.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make[1]: *** [mm/filemap.o] Error 1
> make[1]: *** [mm/vmscan.o] Error 1
> make: *** [mm/] Error 2
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply
* Re: mmotm 2016-05-19-19-59 uploaded
From: Minchan Kim @ 2016-05-20 5:14 UTC (permalink / raw)
To: akpm
Cc: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next,
sfr, mhocko, broonie
In-Reply-To: <573e7da6.pLi6U/36fnX6Drn0%akpm@linux-foundation.org>
On Thu, May 19, 2016 at 07:59:50PM -0700, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2016-05-19-19-59 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (4.x
> or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
>
> This tree is partially included in linux-next. To see which patches are
> included in linux-next, consult the `series' file. Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
>
> A git tree which contains the memory management portion of this tree is
> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> by Michal Hocko. It contains the patches which are between the
> "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
> file, http://www.ozlabs.org/~akpm/mmotm/series.
>
>
> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release. Individual mmotm releases are tagged. The master branch always
> points to the latest release, so it's constantly rebasing.
>
> http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
>
> To develop on top of mmotm git:
>
> $ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> $ git remote update mmotm
> $ git checkout -b topic mmotm/master
> <make changes, commit>
> $ git send-email mmotm/master.. [...]
>
> To rebase a branch with older patches to a new mmotm release:
>
> $ git remote update mmotm
> $ git rebase --onto mmotm/master <topic base> topic
>
>
>
>
> The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
> contains daily snapshots of the -mm tree. It is updated more frequently
> than mmotm, and is untested.
>
> A git copy of this tree is available at
>
> http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/
>
> and use of this tree is similar to
> http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above.
>
In first build, I got this.
In file included from mm/filemap.c:14:0:
include/linux/dax.h:14:3: error: unknown type name ‘dax_iodone_t’
dax_iodone_t);
^
include/linux/dax.h:16:3: error: unknown type name ‘dax_iodone_t’
dax_iodone_t);
^
include/linux/dax.h:39:5: error: unknown type name ‘dax_iodone_t’
dax_iodone_t di)
^
In file included from mm/vmscan.c:49:0:
include/linux/dax.h:14:3: error: unknown type name ‘dax_iodone_t’
dax_iodone_t);
^
include/linux/dax.h:16:3: error: unknown type name ‘dax_iodone_t’
dax_iodone_t);
^
include/linux/dax.h:39:5: error: unknown type name ‘dax_iodone_t’
dax_iodone_t di)
^
In file included from mm/truncate.c:12:0:
include/linux/dax.h:14:3: error: unknown type name ‘dax_iodone_t’
dax_iodone_t);
^
include/linux/dax.h:16:3: error: unknown type name ‘dax_iodone_t’
dax_iodone_t);
^
include/linux/dax.h:39:5: error: unknown type name ‘dax_iodone_t’
dax_iodone_t di)
^
make[1]: *** [mm/truncate.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [mm/filemap.o] Error 1
make[1]: *** [mm/vmscan.o] Error 1
make: *** [mm/] Error 2
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply
* linux-next: Tree for May 20
From: Stephen Rothwell @ 2016-05-20 4:43 UTC (permalink / raw)
To: linux-next; +Cc: linux-kernel
Hi all,
Please do not add any v4.8 destined material to your linux-next included
branches until after v4.7-rc1 has been released.
Changes since 20160519:
The vfs tree gained a conflict against the cifs tree.
The tty tree gained a conflict against Linus' tree.
The dax-misc tree gained a conflict against Linus' tree.
The akpm-current tree gained a conflict against the dax-misc tree.
Non-merge commits (relative to Linus' tree): 4907
3848 files changed, 218368 insertions(+), 94973 deletions(-)
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" and checkout or reset to the new
master.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log
files in the Next directory. Between each merge, the tree was built
with a ppc64_defconfig for powerpc and an allmodconfig (with
CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a
native build of tools/perf. After the final fixups (if any), I do an
x86_64 modules_install followed by builds for x86_64 allnoconfig,
powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig
(this fails its final link) and pseries_le_defconfig and i386, sparc
and sparc64 defconfig.
Below is a summary of the state of the merge.
I am currently merging 236 trees (counting Linus' and 35 trees of patches
pending for Linus' tree).
Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Randy Dunlap for doing many randconfig builds. And to Paul
Gortmaker for triage and bug fixes.
--
Cheers,
Stephen Rothwell
$ git checkout master
$ git reset --hard stable
Merging origin/master (f4c80d5a16eb Merge tag 'sound-4.7-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound)
Merging fixes/master (b507146bb6b9 Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging kbuild-current/rc-fixes (3d1450d54a4f Makefile: Force gzip and xz on module install)
Merging arc-current/for-curr (44549e8f5eea Linux 4.6-rc7)
Merging arm-current/fixes (ec953b70f368 ARM: 8573/1: domain: move {set,get}_domain under config guard)
Merging m68k-current/for-linus (9a6462763b17 m68k/mvme16x: Include generic <linux/rtc.h>)
Merging metag-fixes/fixes (0164a711c97b metag: Fix ioremap_wc/ioremap_cached build errors)
Merging powerpc-fixes/fixes (b4c112114aab powerpc: Fix bad inline asm constraint in create_zero_mask())
Merging powerpc-merge-mpe/fixes (bc0195aad0da Linux 4.2-rc2)
Merging sparc/master (33656a1f2ee5 Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs)
Merging net/master (e22cb5e78762 Merge tag 'batman-adv-fix-for-davem' of git://git.open-mesh.org/linux-merge)
Merging ipsec/master (d6af1a31cc72 vti: Add pmtu handling to vti_xmit.)
Merging ipvs/master (f28f20da704d Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net)
Merging wireless-drivers/master (cbbba30f1ac9 Merge tag 'iwlwifi-for-kalle-2016-05-04' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes)
Merging mac80211/master (e6436be21e77 mac80211: fix statistics leak if dev_alloc_name() fails)
Merging sound-current/for-linus (17e1717c11a3 ALSA: firewire-lib: change a member of event structure to suppress sparse wanings to bool type)
Merging pci-current/for-linus (9a2a5a638f8e PCI: Do not treat EPROBE_DEFER as device attach failure)
Merging driver-core.current/driver-core-linus (c3b46c73264b Linux 4.6-rc4)
Merging tty.current/tty-linus (44549e8f5eea Linux 4.6-rc7)
Merging usb.current/usb-linus (44549e8f5eea Linux 4.6-rc7)
Merging usb-gadget-fixes/fixes (38740a5b87d5 usb: gadget: f_fs: Fix use-after-free)
Merging usb-serial-fixes/usb-linus (74d2a91aec97 USB: serial: option: add even more ZTE device ids)
Merging usb-chipidea-fixes/ci-for-usb-stable (d144dfea8af7 usb: chipidea: otg: change workqueue ci_otg as freezable)
Merging staging.current/staging-linus (44549e8f5eea Linux 4.6-rc7)
Merging char-misc.current/char-misc-linus (44549e8f5eea Linux 4.6-rc7)
Merging input-current/for-linus (23ea5967d6bd Merge branch 'next' into for-linus)
Merging crypto-current/master (bad6a185b4d6 crypto: public_key: select CRYPTO_AKCIPHER)
Merging ide/master (1993b176a822 Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide)
Merging devicetree-current/devicetree/merge (f76502aa9140 of/dynamic: Fix test for PPC_PSERIES)
Merging rr-fixes/fixes (8244062ef1e5 modules: fix longstanding /proc/kallsyms vs module insertion race.)
Merging vfio-fixes/for-linus (8160c4e45582 vfio: fix ioctl error handling)
Merging kselftest-fixes/fixes (505ce68c6da3 selftest/seccomp: Fix the seccomp(2) signature)
Merging backlight-fixes/for-backlight-fixes (68feaca0b13e backlight: pwm: Handle EPROBE_DEFER while requesting the PWM)
Merging ftrace-fixes/for-next-urgent (6224beb12e19 tracing: Have branch tracer use recursive field of task struct)
Merging mfd-fixes/for-mfd-fixes (1b52e50f2a40 mfd: max77843: Fix max77843_chg_init() return on error)
Merging drm-intel-fixes/for-linux-next-fixes (2dcd0af568b0 Linux 4.6)
Merging asm-generic/master (b0da6d44157a asm-generic: Drop renameat syscall from default list)
Merging arc/for-next (776d7f1694a7 arc: axs103_smp: Fix CPU frequency to 100MHz for dual-core)
Merging arm/for-next (b6810489fa29 Merge branch 'devel-stable' into for-next)
Merging arm-perf/for-next/perf (4ba2578fa7b5 arm64: perf: don't expose CHAIN event in sysfs)
Merging arm-soc/for-next (475848b27103 Merge branch 'fixes' into for-next)
Merging at91/at91-next (5a0d7c6a48ae Merge branch 'at91-4.7-defconfig' into at91-next)
Merging bcm2835-dt/bcm2835-dt-next (896ad420db8d dt/bindings: bcm2835: correct description for DMA-int)
Merging bcm2835-soc/bcm2835-soc-next (92e963f50fc7 Linux 4.5-rc1)
Merging bcm2835-drivers/bcm2835-drivers-next (92e963f50fc7 Linux 4.5-rc1)
Merging bcm2835-defconfig/bcm2835-defconfig-next (3652bb35abf6 ARM: bcm2835: Enable NFS root support.)
Merging berlin/berlin/for-next (9a7e06833249 Merge branch 'berlin/fixes' into berlin/for-next)
Merging cortex-m/for-next (f719a0d6a854 ARM: efm32: switch to vendor,device compatible strings)
Merging imx-mxs/for-next (63b44471754b Merge branch 'imx/defconfig64' into for-next)
Merging keystone/next (02e15d234006 Merge branch 'for_4.7/kesytone' into next)
Merging mvebu/for-next (01316cded75b Merge branch 'mvebu/defconfig' into mvebu/for-next)
Merging omap/for-next (5c66191b5c76 Merge branch 'omap-for-v4.7/dt' into for-next)
Merging omap-pending/for-next (c20c8f750d9f ARM: OMAP2+: hwmod: fix _idle() hwmod state sanity check sequence)
Merging qcom/for-next (2dd0d1733417 ARM: dts: msm8974: Add SCM firmware node)
Merging renesas/next (e5c640c6f9cc Merge branches 'heads/arm64-defconfig-for-v4.7', 'heads/arm64-dt-pm-domain-for-v4.7', 'heads/dt-for-v4.7' and 'heads/pci-defconfig-for-v4.7' into next)
Merging rockchip/for-next (a108aca0c77f Merge branch 'v4.7-clk/fixes' into for-next)
Merging rpi/for-rpi-next (bc0195aad0da Linux 4.2-rc2)
Merging samsung/for-next (92e963f50fc7 Linux 4.5-rc1)
Merging samsung-krzk/for-next (35e691cf5165 Merge branch 'fixes-v4.7' into for-next)
Merging tegra/for-next (5c282bc9d0a3 Merge branch for-4.7/defconfig into for-next)
Merging arm64/for-next/core (e6d9a5254333 arm64: do not enforce strict 16 byte alignment to stack pointer)
Merging blackfin/for-linus (391e74a51ea2 eth: bf609 eth clock: add pclk clock for stmmac driver probe)
CONFLICT (content): Merge conflict in arch/blackfin/mach-common/pm.c
Merging c6x/for-linux-next (ca3060d39ae7 c6x: Use generic clkdev.h header)
Merging cris/for-next (f9f3f864b5e8 cris: Fix section mismatches in architecture startup code)
Merging h8300/h8300-next (8cad489261c5 h8300: switch EARLYCON)
Merging hexagon/linux-next (02cc2ccfe771 Revert "Hexagon: fix signal.c compile error")
Merging ia64/next (787ca32dc704 ia64/unaligned: Silence another GCC warning about an uninitialised variable)
Merging m68k/for-next (9a6462763b17 m68k/mvme16x: Include generic <linux/rtc.h>)
Merging m68knommu/for-next (44156affd184 m68k: change m68knommu maintainer email address)
Merging metag/for-next (096a8b6d5e7a metag: Fix atomic_*_return inline asm constraints)
Merging microblaze/next (52e9e6e05617 microblaze: pci: export isa_io_base to fix link errors)
Merging mips/mips-for-linux-next (2c93cd0d5d69 MIPS: Clear Status IPL field when using EIC)
Merging nios2/for-next (9fa78f63a892 nios2: Add order-only DTC dependency to %.dtb target)
Merging parisc-hd/for-next (695499920489 parisc: Add native high-resolution sched_clock() implementation)
Merging powerpc/next (138a076496e6 Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/scottwood/linux into next)
CONFLICT (content): Merge conflict in arch/powerpc/kernel/prom.c
Merging powerpc-mpe/next (bc0195aad0da Linux 4.2-rc2)
Merging fsl/next (1eef33bec12d powerpc/86xx: Fix PCI interrupt map definition)
Merging mpc5xxx/next (39e69f55f857 powerpc: Introduce the use of the managed version of kzalloc)
Merging s390/features (6edf0aa4f8bb s390/bpf: fix recache skb->data/hlen for skb_vlan_push/pop)
Merging sparc-next/master (9f935675d41a Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input)
Merging tile/master (4ef00aa30a3f tile: sort the "select" lines in the TILE/TILEGX configs)
Merging uml/linux-next (ad32a1f3c36b um: use %lx format specifiers for unsigned longs)
Merging unicore32/unicore32 (c83d8b2fc986 unicore32: mm: Add missing parameter to arch_vma_access_permitted)
Merging xtensa/for_next (9da8320bb977 xtensa: add test_kc705_hifi variant)
Merging btrfs/next (c315ef8d9db7 Merge branch 'for-chris-4.7' of git://git.kernel.org/pub/scm/linux/kernel/git/fdmanana/linux into for-linus-4.7)
Merging btrfs-kdave/for-next (a3a7fdf24a89 Merge branch 'for-next-next-4.7-20160512' into for-next-20160512)
CONFLICT (content): Merge conflict in fs/btrfs/inode.c
CONFLICT (content): Merge conflict in fs/btrfs/dev-replace.c
Merging ceph/master (d3767f0faeda rbd: report unsupported features to syslog)
Merging cifs/for-next (56c1d814aadf CIFS: Remove some obsolete comments)
Applying: cifs: fix for keyringalloc() API change
Merging configfs/for-next (96c22a329351 configfs: fix CONFIGFS_BIN_ATTR_[RW]O definitions)
Merging ecryptfs/next (933c32fe0e42 ecryptfs: drop null test before destroy functions)
Merging ext3/for_next (7888824b0b1c udf: Use correct partition reference number for metadata)
Merging ext4/dev (12735f881952 ext4: pre-zero allocated blocks for DAX IO)
CONFLICT (content): Merge conflict in fs/ext4/inode.c
CONFLICT (content): Merge conflict in fs/ext4/indirect.c
CONFLICT (content): Merge conflict in fs/ext4/ext4.h
Merging f2fs/dev (cb8be9a053f8 f2fs: avoid ENOSPC fault in the recovery process)
CONFLICT (content): Merge conflict in fs/f2fs/data.c
Merging fscache/fscache (b00c2ae2ed3c FS-Cache: Don't override netfs's primary_index if registering failed)
Merging fuse/for-next (4441f63ab7e5 fuse: update mailing list in MAINTAINERS)
Merging gfs2/for-next (68cd4ce2caf2 GFS2: Refactor gfs2_remove_from_journal)
Merging jfs/jfs-next (6ed71e9819ac jfs: Coalesce some formats)
Merging nfs/linux-next (1b3c6d07e295 pnfs: make pnfs_layout_process more robust)
CONFLICT (content): Merge conflict in fs/nfs/direct.c
Applying: nfs: fix for i_mutex to i_rwsem change
Merging nfsd/nfsd-next (d9e4084f6c97 svcrdma: Generalize svc_rdma_xdr_decode_req())
Merging orangefs/for-next (e56f49814250 orangefs: remove unused variable)
Merging overlayfs/overlayfs-next (41523ff335f4 ovl: override creds with the ones from the superblock mounter)
Merging v9fs/for-next (a333e4bf2556 fs/9p: use fscache mutex rather than spinlock)
Merging ubifs/linux-next (c27cb97218b3 ubifs: Remove unused header)
Merging xfs/for-next (d8bdd04e309b Merge branch 'xfs-4.7-misc-fixes' into for-next)
Merging file-locks/linux-next (5af9c2e19da6 Merge branch 'akpm' (patches from Andrew))
Merging vfs/for-next (51085a1f913a cifs: use C99 syntax for inode_operations initializer)
CONFLICT (content): Merge conflict in fs/cifs/cifsfs.c
Merging pci/next (e257ef55ce51 Merge branches 'pci/arm64' and 'pci/host-hv' into next)
Applying: iommu/amd: fix up for aliases API change
Merging hid/for-next (185a9cac5b1e Merge branch 'for-4.6/upstream-fixes' into for-next)
Merging i2c/i2c/for-next (0b008267ec1b Merge branch 'i2c/for-4.7' into i2c/for-next)
Merging jdelvare-hwmon/master (f02de116250d Documentation/hwmon: Update links in max34440)
Merging dmi/master (c3db05ecf8ac firmware: dmi_scan: Save SMBIOS Type 9 System Slots)
Merging hwmon-staging/hwmon-next (d6a442df63b2 hwmon: (sch5636) trivial fix of spelling mistake on revision)
Merging v4l-dvb/master (73dfb701d254 Merge branch 'v4l_for_linus' into to_next)
Merging pm/linux-next (16490980e396 Merge tag 'device-properties-4.7-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm)
Merging idle/next (f55532a0c0b8 Linux 4.6-rc1)
Merging thermal/next (f1ba9eb85b5e thermal: int340x: processor_thermal: support acpi notification)
Merging thermal-soc/next (ddc8fdc6e2f0 Merge branch 'work-fixes' into work-next)
Merging ieee1394/for-next (384fbb96f926 firewire: nosy: Replace timeval with timespec64)
Merging dlm/next (82c7d823cc31 dlm: config: Fix ENOMEM failures in make_cluster())
Merging swiotlb/linux-next (386744425e35 swiotlb: Make linux/swiotlb.h standalone includible)
Merging slave-dma/next (628b5139c906 Merge branch 'for-linus' into next)
Merging net-next/master (07b75260ebc2 Merge branch 'upstream' of git://git.linux-mips.org/pub/scm/ralf/upstream-linus)
Merging ipsec-next/master (cb866e3298cd xfrm: Increment statistic counter on inner mode error)
Merging ipvs-next/master (698e2a8dca98 ipvs: make drop_entry protection effective for SIP-pe)
Merging wireless-drivers-next/master (52776a700b53 Merge ath-next from ath.git)
Merging bluetooth/master (0b7962a6c4a3 Merge branch 'for-4.7' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata)
Merging mac80211-next/master (4f45bb3e8a8f mac80211_hwsim: Allow managing radios from non-initial namespaces)
Merging rdma/for-next (c16d2750a08c IB/mlx5: Fire the CQ completion handler from tasklet)
CONFLICT (content): Merge conflict in net/sunrpc/xprtrdma/frwr_ops.c
CONFLICT (content): Merge conflict in include/linux/mlx5/driver.h
Merging rdma-leon/rdma-next (2dcd0af568b0 Linux 4.6)
Merging rdma-leon-test/testing/rdma-next (2dcd0af568b0 Linux 4.6)
Merging mtd/master (20c07a5bf094 mtd: nand: Drop mtd.owner requirement in nand_scan)
Merging l2-mtd/master (e5366a266a8c mtd: spi-nor: support GigaDevice gd25lq64c)
Merging nand/nand/next (666b65683dad mtd: brcmnand: respect ECC algorithm set by NAND subsystem)
Merging crypto/master (256b1cfb9a34 crypto: qat - change the adf_ctl_stop_devices to void)
Merging drm/drm-next (7c10ddf87472 Merge branch 'drm-uapi-extern-c-fixes' of https://github.com/evelikov/linux into drm-next)
Merging drm-panel/drm/panel/for-next (227e4f4079e1 drm/panel: simple: Add support for TPK U.S.A. LLC Fusion 7" and 10.1" panels)
Merging drm-intel/for-linux-next (5b4fd5b1111b drm/i915: Update DRIVER_DATE to 20160425)
Merging drm-tegra/drm/tegra/for-next (057eab2013ec MAINTAINERS: Remove Terje Bergström as Tegra DRM maintainer)
Merging drm-misc/topic/drm-misc (c6740c9c9e91 drm: remove unused dev variables)
Merging drm-exynos/exynos-drm/for-next (25364a9e54fb Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid)
Merging drm-msm/msm-next (2b669875332f drm/msm: Drop load/unload drm_driver ops)
Merging hdlcd/for-upstream/hdlcd (69c2565a3cca drm: ARM HDLCD - fix an error code)
Merging drm-vc4/drm-vc4-next (efea172891fc drm/vc4: Return -EBUSY if there's already a pending flip event.)
Merging sunxi/sunxi/for-next (ed490b3ebfa4 Merge branches 'sunxi/drm-fixes-for-4.7' and 'sunxi/dt-for-4.7' into sunxi/for-next)
Merging kbuild/for-next (0c644e04ad1b Merge branch 'kbuild/misc' into kbuild/for-next)
Merging kconfig/for-next (5bcba792bb30 localmodconfig: Fix whitespace repeat count after "tristate")
Merging regmap/for-next (d4ab78d7076d Merge remote-tracking branches 'regmap/topic/doc' and 'regmap/topic/flat' into regmap-next)
Merging sound/for-next (17e1717c11a3 ALSA: firewire-lib: change a member of event structure to suppress sparse wanings to bool type)
Merging sound-asoc/for-next (349982487e26 Merge remote-tracking branches 'asoc/fix/ak4642' and 'asoc/fix/twl6040' into asoc-linus)
Merging modules/modules-next (e2d1248432c4 module: Disable MODULE_FORCE_LOAD when MODULE_SIG_FORCE is enabled)
Merging input/next (4feacbc24eea Input: add new driver for the Surface 3)
Merging block/for-next (661806a31989 Merge branch 'for-4.7/core' into for-next)
Merging lightnvm/for-next (2a65aee4011b lightnvm: reserved space calculation incorrect)
Merging device-mapper/for-next (202bae52934d dm thin: unroll issue_discard() to create longer discard bio chains)
Merging pcmcia/master (e8e68fd86d22 pcmcia: do not break rsrc_nonstatic when handling anonymous cards)
Merging mmc-uh/next (57da0c042f4a mmc: block: Pause re-tuning while switched to the RPMB partition)
Merging md/for-next (1fa9a1ad0a9d md-cluster: check the return value of process_recvd_msg)
Merging mfd/for-mfd-next (b52207ef4ea5 mfd: hi655x: Add MFD driver for hi655x)
Merging backlight/for-backlight-next (60d613d6aef4 backlight: pwm_bl: Free PWM requested by legacy API on error path)
Merging battery/master (4a99fa06a8ca sbs-battery: fix power status when battery charging near dry)
Merging omap_dss2/for-next (ffe1b6c453ef video: AMBA CLCD: Remove unncessary include in amba-clcd.c)
Merging regulator/for-next (6b3f657e5e3e Merge remote-tracking branch 'regulator/fix/ccv' into regulator-linus)
Merging security/next (b937190c40de LSM: LoadPin: provide enablement CONFIG)
Merging integrity/next (05d1a717ec04 ima: add support for creating files using the mknodat syscall)
Merging keys/keys-next (75aeddd12f20 MAINTAINERS: Update keyrings record and add asymmetric keys record)
Merging selinux/next (b937190c40de LSM: LoadPin: provide enablement CONFIG)
Merging tpmdd/next (e8f2f45a4402 tpm: Fix suspend regression)
Merging watchdog/master (ae67643edc6e Documentation: Add ebc-c384_wdt watchdog-parameters.txt entry)
Merging iommu/next (6c0b43df74f9 Merge branches 'arm/io-pgtable', 'arm/rockchip', 'arm/omap', 'x86/vt-d', 'ppc/pamu', 'core' and 'x86/amd' into next)
Merging dwmw2-iommu/master (22e2f9fa63b0 iommu/vt-d: Use per-cpu IOVA caching)
Merging vfio/next (f70552809419 vfio_pci: Test for extended capabilities if config space > 256 bytes)
Merging jc_docs/docs-next (9f8036643dd9 doc: self-protection: provide initial details)
CONFLICT (content): Merge conflict in samples/Makefile
Merging trivial/for-next (52bbe141f37f gitignore: fix wording)
Merging audit/next (188e3c5cd2b6 tty: provide tty_name() even without CONFIG_TTY)
Merging devicetree/devicetree/next (48a9b733e644 of/irq: Rename "intc_desc" to "of_intc_desc" to fix OF on sh)
Merging dt-rh/for-next (f2c27767af0a devicetree: Add Creative Technology vendor id)
CONFLICT (content): Merge conflict in drivers/iommu/arm-smmu.c
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt
Merging mailbox/mailbox-for-next (c430cf376fee mailbox: Fix devm_ioremap_resource error detection code)
Merging spi/for-next (2dcd0af568b0 Linux 4.6)
Merging tip/auto-latest (139f278f8e96 Merge branch 'core/urgent')
Merging clockevents/clockevents/next (cee77c2c5b57 clocksource/drivers/tango-xtal: Fix incorrect test)
Merging edac/linux_next (12f0721c5a70 sb_edac: correctly fetch DIMM width on Ivy Bridge and Haswell)
Merging edac-amd/for-next (3f37a36b6282 EDAC, amd64_edac: Drop pci_register_driver() use)
Merging irqchip/irqchip/for-next (a66ce4b7d9d2 Merge branch 'irqchip/mvebu' into irqchip/for-next)
Merging ftrace/for-next (0fc1b09ff1ff tracing: Use temp buffer when filtering events)
Merging rcu/rcu/next (0e7e2457e4e4 Merge commit 'dcd36d01fb3f99d1d5df01714f6ccbe3fbbaf81f' into HEAD)
Merging kvm/linux-next (9842df62004f KVM: MTRR: remove MSR 0x2f8)
Merging kvm-arm/next (064850532444 kvm: arm64: Enable hardware updates of the Access Flag for Stage 2 page tables)
Merging kvm-ppc/kvm-ppc-next (c63517c2e381 KVM: PPC: Book3S: correct width in XER handling)
Merging kvm-ppc-paulus/kvm-ppc-next (b1a4286b8f33 KVM: PPC: Book3S HV: Re-enable XICS fast path for irqfd-generated interrupts)
Merging kvms390/next (60a37709ce60 KVM: s390: Populate mask of non-hypervisor managed facility bits)
Merging xen-tip/linux-next (51c2a7526e54 xen/gntdev: reduce copy batch size to 16)
CONFLICT (content): Merge conflict in drivers/xen/efi.c
CONFLICT (content): Merge conflict in arch/arm64/kernel/setup.c
Applying: xen: efi: merge fix patch
Merging percpu/for-next (18fc93fd6412 percpu: remove PERCPU_ENOUGH_ROOM which is stale definition)
Merging workqueues/for-next (f1e89a8f3358 Merge branch 'for-4.6-fixes' into for-next)
Merging drivers-x86/for-next (f831153ac9d3 asus-wmi: provide access to ALS control)
Merging chrome-platform/for-next (9e96aa70e9ac platform/chrome: chromeos_laptop - Add Elan touchpad for Wolf)
Merging hsi/for-next (c2f90a465df7 HSI: omap-ssi: move omap_ssi_port_update_fclk)
Merging leds/for-next (80d6737b27bb leds: gpio: Support the "panic-indicator" firmware property)
Merging ipmi/for-next (a1b4e31bfabb IPMI: reserve memio regions separately)
Merging driver-core/driver-core-next (c6e360a0d9d2 Revert "base: dd: don't remove driver_data in -EPROBE_DEFER case")
Merging tty/tty-next (d20bb59af646 MAINTAINERS: 8250: remove website reference)
CONFLICT (content): Merge conflict in include/uapi/linux/serial_core.h
CONFLICT (content): Merge conflict in drivers/tty/serial/Makefile
Merging usb/usb-next (60d5794fe5a5 Merge tag 'usb-serial-4.7-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial into usb-next)
Merging usb-gadget/next (2a58f9c12bb3 usb: dwc3: gadget: disable automatic calculation of ACK TP NUMP)
Merging usb-serial/usb-next (b923c6c62981 USB: serial: ti_usb_3410_5052: add MOXA UPORT 11x0 support)
Merging usb-chipidea-next/ci-for-usb-next (764763f0a0c8 doc: usb: chipidea: update the doc for OTG FSM)
Merging staging/staging-next (ffc83a79b44e Staging: emxx_udc: emxx_udc: fixed coding style issue)
CONFLICT (content): Merge conflict in drivers/staging/lustre/lustre/llite/rw26.c
Applying: staging: lustre: o2iblnd: fix for ib_map_mr_sg() API changes
Merging char-misc/char-misc-next (725d0123dfff Merge 4.6-rc7 into char-misc-testing)
Merging extcon/extcon-next (453fc627c7b5 extcon: usb-gpio: add support for ACPI gpio interface)
Merging cgroup/for-next (a6b18f07bc86 Merge branch 'for-4.6-fixes' into for-next)
Merging scsi/for-next (02714f2c73a6 Merge branch 'misc' into for-next)
Merging target-updates/for-next (8f0dfb3d8b11 iscsi-target: Fix early sk_data_ready LOGIN_FLAGS_READY race)
Merging target-merge/for-next-merge (2994a7518317 cxgb4: update Kconfig and Makefile)
Merging libata/for-next (a85742332511 Merge branch 'for-4.7' into for-next)
Merging pinctrl/for-next (58d73d264a02 Merge branch 'devel' into for-next)
Merging vhost/linux-next (21ba4174ef40 virtio_balloon: fix PFN format for virtio-1)
Merging remoteproc/for-next (7a6271a80cae remoteproc/wkup_m3: Use MODULE_DEVICE_TABLE to export alias)
Merging rpmsg/for-next (0259cd1b6496 Merge remote-tracking branches 'remoteproc/rpmsg-next' and 'remoteproc/rproc-next' into for-next)
Merging gpio/for-next (d30a2b47d4c2 MIPS: do away with ARCH_[WANT_OPTIONAL|REQUIRE]_GPIOLIB)
Merging dma-mapping/dma-mapping-next (d770e558e219 Linux 4.2-rc1)
Merging pwm/for-next (18c588786c08 Merge branch 'for-4.7/pwm-atomic' into for-next)
Merging dma-buf/for-next (12566cc35d0e Merge tag 'pci-v4.6-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci)
Merging userns/for-next (f2ca379642d7 namei: permit linking with CAP_FOWNER in userns)
Merging ktest/for-next (2dcd0af568b0 Linux 4.6)
Merging clk/clk-next (ef56b79b66fa clk: fix critical clock locking)
CONFLICT (content): Merge conflict in drivers/clk/Kconfig
Merging aio/master (b562e44f507e Linux 4.5)
Merging kselftest/next (6eab37daf0ec tools: testing: define the _GNU_SOURCE macro)
Merging y2038/y2038 (4b277763c5b3 vfs: Add support to document max and min inode times)
Merging luto-misc/next (afd2ff9b7e1b Linux 4.4)
Merging borntraeger/linux-next (b562e44f507e Linux 4.5)
Merging livepatching/for-next (6d9122078097 Merge branch 'for-4.7/core' into for-next)
Merging coresight/next (f85f84cd36af coresight: Handle build path error)
Merging rtc/rtc-next (854ec813cc23 rtc: rename so the tps6586x-rtc module can be autoloaded at boot)
Merging hwspinlock/for-next (bd5717a4632c hwspinlock: qcom: Correct msb in regmap_field)
Merging nvdimm/libnvdimm-for-next (e897b3cc7a5a Merge branch 'for-4.7/acpi6.1' into libnvdimm-for-next)
Merging dax-misc/dax-misc (4d9a2c874667 dax: Remove i_mmap_lock protection)
CONFLICT (content): Merge conflict in include/linux/dax.h
CONFLICT (content): Merge conflict in fs/block_dev.c
Merging akpm-current/current (db264f60346a ipc/msg.c: use freezable blocking call)
CONFLICT (content): Merge conflict in include/linux/radix-tree.h
CONFLICT (content): Merge conflict in include/linux/dax.h
CONFLICT (content): Merge conflict in fs/dax.c
CONFLICT (content): Merge conflict in arch/tile/Kconfig
CONFLICT (content): Merge conflict in arch/powerpc/include/asm/book3s/64/pgtable.h
CONFLICT (content): Merge conflict in arch/mips/kernel/process.c
CONFLICT (content): Merge conflict in arch/mips/Kconfig
$ git checkout -b akpm remotes/origin/akpm/master
Applying: mm: make optimistic check for swapin readahead fix
Applying: drivers/net/wireless/intel/iwlwifi/dvm/calib.c: simplfy min() expression
Applying: mm: make mmap_sem for write waits killable for mm syscalls
Applying: mm: make vm_mmap killable
Applying: mm: make vm_munmap killable
Applying: mm, aout: handle vm_brk failures
Applying: mm, elf: handle vm_brk error
Applying: mm: make vm_brk killable
Applying: mm, proc: make clear_refs killable
Applying: mm, fork: make dup_mmap wait for mmap_sem for write killable
Applying: ipc, shm: make shmem attach/detach wait for mmap_sem killable
Applying: vdso: make arch_setup_additional_pages wait for mmap_sem for write killable
Applying: coredump: make coredump_wait wait for mmap_sem for write killable
Applying: aio: make aio_setup_ring killable
Applying: exec: make exec path waiting for mmap_sem killable
Applying: prctl: make PR_SET_THP_DISABLE wait for mmap_sem killable
Applying: uprobes: wait for mmap_sem for write killable
Applying: drm/i915: make i915_gem_mmap_ioctl wait for mmap_sem killable
Applying: drm/radeon: make radeon_mn_get wait for mmap_sem killable
Applying: drm/amdgpu: make amdgpu_mn_get wait for mmap_sem killable
Applying: drm/amdgpu: use ERR_PTR() to return from amdgpu_mn_get
Applying: kgdb: depends on VT
Merging akpm/master (259a35d944af kgdb: depends on VT)
^ permalink raw reply
* linux-next: manual merge of the akpm-current tree with the dax-misc tree
From: Stephen Rothwell @ 2016-05-20 3:58 UTC (permalink / raw)
To: Andrew Morton, Verma, Vishal L
Cc: linux-next, linux-kernel, Toshi Kani, Jan Kara
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
include/linux/dax.h
between commit:
bc2466e42573 ("dax: Use radix tree entry lock to protect cow faults")
from the dax-misc tree and commit:
c2ce6adc69c8 ("dax: add dax_get_unmapped_area for pmd mappings")
from the akpm-current tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc include/linux/dax.h
index 43d5f0b799c7,0cd64c152361..000000000000
--- a/include/linux/dax.h
+++ b/include/linux/dax.h
@@@ -21,36 -17,26 +21,39 @@@ void dax_wake_mapping_entry_waiter(stru
#ifdef CONFIG_FS_DAX
struct page *read_dax_sector(struct block_device *bdev, sector_t n);
+void dax_unlock_mapping_entry(struct address_space *mapping, pgoff_t index);
+int __dax_zero_page_range(struct block_device *bdev, sector_t sector,
+ unsigned int offset, unsigned int length);
+ unsigned long dax_get_unmapped_area(struct file *filp, unsigned long addr,
+ unsigned long len, unsigned long pgoff, unsigned long flags);
#else
static inline struct page *read_dax_sector(struct block_device *bdev,
sector_t n)
{
return ERR_PTR(-ENXIO);
}
+/* Shouldn't ever be called when dax is disabled. */
+static inline void dax_unlock_mapping_entry(struct address_space *mapping,
+ pgoff_t index)
+{
+ BUG();
+}
+static inline int __dax_zero_page_range(struct block_device *bdev,
+ sector_t sector, unsigned int offset, unsigned int length)
+{
+ return -ENXIO;
+}
+ #define dax_get_unmapped_area NULL
#endif
-#ifdef CONFIG_TRANSPARENT_HUGEPAGE
+#if defined(CONFIG_TRANSPARENT_HUGEPAGE)
int dax_pmd_fault(struct vm_area_struct *, unsigned long addr, pmd_t *,
- unsigned int flags, get_block_t, dax_iodone_t);
+ unsigned int flags, get_block_t);
int __dax_pmd_fault(struct vm_area_struct *, unsigned long addr, pmd_t *,
- unsigned int flags, get_block_t, dax_iodone_t);
+ unsigned int flags, get_block_t);
#else
static inline int dax_pmd_fault(struct vm_area_struct *vma, unsigned long addr,
- pmd_t *pmd, unsigned int flags, get_block_t gb,
- dax_iodone_t di)
+ pmd_t *pmd, unsigned int flags, get_block_t gb)
{
return VM_FAULT_FALLBACK;
}
^ permalink raw reply
* linux-next: build warnings after merge of the net tree
From: Stephen Rothwell @ 2016-05-20 3:33 UTC (permalink / raw)
To: David Miller, netdev; +Cc: linux-next, linux-kernel, Heinrich Schuchardt
Hi all,
After merging the net tree, today's linux-next build (arm
multi_v7_defconfig) produced these warnings:
drivers/net/usb/pegasus.c: In function 'read_bulk_callback':
drivers/net/usb/pegasus.c:475:1: warning: label 'goon' defined but not used [-Wunused-label]
goon:
^
drivers/net/usb/pegasus.c:446:8: warning: unused variable 'pkt_len' [-Wunused-variable]
__u16 pkt_len;
^
drivers/net/usb/pegasus.c:445:6: warning: unused variable 'buf' [-Wunused-variable]
u8 *buf = urb->transfer_buffer;
^
drivers/net/usb/pegasus.c:443:17: warning: unused variable 'count' [-Wunused-variable]
int rx_status, count = urb->actual_length;
^
Introduced by commit
e00be9e4d0ff ("net: pegasus: remove dead coding")
--
Cheers,
Stephen Rothwell
^ permalink raw reply
* Re: mmotm 2016-05-19-19-59 uploaded
From: Stephen Rothwell @ 2016-05-20 3:27 UTC (permalink / raw)
To: akpm
Cc: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next,
mhocko, broonie
In-Reply-To: <573e7da6.pLi6U/36fnX6Drn0%akpm@linux-foundation.org>
Hi Andrew,
On Thu, 19 May 2016 19:59:50 -0700 akpm@linux-foundation.org wrote:
>
> The mm-of-the-moment snapshot 2016-05-19-19-59 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
This one looks much better, thanks.
--
Cheers,
Stephen Rothwell
^ permalink raw reply
* linux-next: manual merge of the dax-misc tree with Linus' tree
From: Stephen Rothwell @ 2016-05-20 3:26 UTC (permalink / raw)
To: Verma, Vishal L
Cc: linux-next, linux-kernel, Christoph Hellwig, Al Viro, Jan Kara,
Ross Zwisler
Hi all,
Today's linux-next merge of the dax-misc tree got a conflict in:
include/linux/dax.h
between commit:
c8b8e32d700f ("direct-io: eliminate the offset argument to ->direct_IO")
from Linus' tree and commit:
e804315dd0f5 ("dax: Define DAX lock bit for radix tree exceptional entry")
from the dax-misc tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc include/linux/dax.h
index 982a6c4a62f3,7bf12277c006..000000000000
--- a/include/linux/dax.h
+++ b/include/linux/dax.h
@@@ -3,17 -3,21 +3,21 @@@
#include <linux/fs.h>
#include <linux/mm.h>
+ #include <linux/radix-tree.h>
#include <asm/pgtable.h>
+ /* We use lowest available exceptional entry bit for locking */
+ #define RADIX_DAX_ENTRY_LOCK (1 << RADIX_TREE_EXCEPTIONAL_SHIFT)
+
-ssize_t dax_do_io(struct kiocb *, struct inode *, struct iov_iter *, loff_t,
+ssize_t dax_do_io(struct kiocb *, struct inode *, struct iov_iter *,
get_block_t, dio_iodone_t, int flags);
- int dax_clear_sectors(struct block_device *bdev, sector_t _sector, long _size);
int dax_zero_page_range(struct inode *, loff_t from, unsigned len, get_block_t);
int dax_truncate_page(struct inode *, loff_t from, get_block_t);
- int dax_fault(struct vm_area_struct *, struct vm_fault *, get_block_t,
- dax_iodone_t);
- int __dax_fault(struct vm_area_struct *, struct vm_fault *, get_block_t,
- dax_iodone_t);
+ int dax_fault(struct vm_area_struct *, struct vm_fault *, get_block_t);
+ int __dax_fault(struct vm_area_struct *, struct vm_fault *, get_block_t);
+ int dax_delete_mapping_entry(struct address_space *mapping, pgoff_t index);
+ void dax_wake_mapping_entry_waiter(struct address_space *mapping,
+ pgoff_t index, bool wake_all);
#ifdef CONFIG_FS_DAX
struct page *read_dax_sector(struct block_device *bdev, sector_t n);
^ permalink raw reply
* Re: linux-next: build failure after merge of the security tree
From: Steve French @ 2016-05-20 3:07 UTC (permalink / raw)
To: Stephen Rothwell
Cc: James Morris, linux-cifs@vger.kernel.org, linux-next, LKML,
Sachin Prabhu, David Howells
In-Reply-To: <20160520091447.1cba4885@canb.auug.org.au>
I fixed the build break (and some trivial compile warnings) due to the
change to the format of keyring_alloc and repushed the *"cifs: Create
dedicated keyring for spnego operations" patch to cifs-2.6.git
for-next
On Thu, May 19, 2016 at 6:14 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Steve,
>
> On Thu, 19 May 2016 14:01:20 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the security tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> fs/cifs/cifs_spnego.c: In function 'init_cifs_spnego':
>> fs/cifs/cifs_spnego.c:206:12: error: too few arguments to function 'keyring_alloc'
>> keyring = keyring_alloc(".cifs_spnego",
>> ^
>> In file included from include/linux/cred.h:17:0,
>> from include/linux/sched.h:56,
>> from include/linux/kasan.h:4,
>> from include/linux/slab.h:118,
>> from fs/cifs/cifs_spnego.c:23:
>> include/linux/key.h:302:20: note: declared here
>> extern struct key *keyring_alloc(const char *description, kuid_t uid, kgid_t gid,
>> ^
>>
>> Caused by commit
>>
>> 5b82c5cbcfe4 ("cifs: Create dedicated keyring for spnego operations")
>>
>> from the cifs tree interacting with commit
>>
>> 5ac7eace2d00 ("KEYS: Add a facility to restrict new links into a keyring")
>>
>> from the security tree.
>>
>> I added the following merge fix patch (and someone will have to let
>> Linus know):
>>
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Thu, 19 May 2016 13:45:10 +1000
>> Subject: [PATCH] cifs: fix for keyringalloc() API change
>>
>> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> ---
>> fs/cifs/cifs_spnego.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/cifs/cifs_spnego.c b/fs/cifs/cifs_spnego.c
>> index 248ab431930c..9ef0dfcb2f95 100644
>> --- a/fs/cifs/cifs_spnego.c
>> +++ b/fs/cifs/cifs_spnego.c
>> @@ -207,7 +207,7 @@ init_cifs_spnego(void)
>> GLOBAL_ROOT_UID, GLOBAL_ROOT_GID, cred,
>> (KEY_POS_ALL & ~KEY_POS_SETATTR) |
>> KEY_USR_VIEW | KEY_USR_READ,
>> - KEY_ALLOC_NOT_IN_QUOTA, NULL);
>> + KEY_ALLOC_NOT_IN_QUOTA, NULL, NULL);
>> if (IS_ERR(keyring)) {
>> ret = PTR_ERR(keyring);
>> goto failed_put_cred;
>> --
>> 2.7.0
>
> The security tree has now been merged into Linus' tree, so this build
> breakage occurs when I merge the cifs tree. So you will need to tell
> Linus about this needed fixup when he merges the cifs tree.
>
> --
> Cheers,
> Stephen Rothwell
--
Thanks,
Steve
^ permalink raw reply
* mmotm 2016-05-19-19-59 uploaded
From: akpm @ 2016-05-20 2:59 UTC (permalink / raw)
To: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next,
sfr, mhocko, broonie
The mm-of-the-moment snapshot 2016-05-19-19-59 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You will need quilt to apply these patches to the latest Linus release (4.x
or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
http://ozlabs.org/~akpm/mmotm/series
The file broken-out.tar.gz contains two datestamp files: .DATE and
.DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
followed by the base kernel version against which this patch series is to
be applied.
This tree is partially included in linux-next. To see which patches are
included in linux-next, consult the `series' file. Only the patches
within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
linux-next.
A git tree which contains the memory management portion of this tree is
maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
by Michal Hocko. It contains the patches which are between the
"#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
file, http://www.ozlabs.org/~akpm/mmotm/series.
A full copy of the full kernel tree with the linux-next and mmotm patches
already applied is available through git within an hour of the mmotm
release. Individual mmotm releases are tagged. The master branch always
points to the latest release, so it's constantly rebasing.
http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/
To develop on top of mmotm git:
$ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
$ git remote update mmotm
$ git checkout -b topic mmotm/master
<make changes, commit>
$ git send-email mmotm/master.. [...]
To rebase a branch with older patches to a new mmotm release:
$ git remote update mmotm
$ git rebase --onto mmotm/master <topic base> topic
The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
contains daily snapshots of the -mm tree. It is updated more frequently
than mmotm, and is untested.
A git copy of this tree is available at
http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/
and use of this tree is similar to
http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above.
This mmotm tree contains the following patches against 4.6:
(patches marked "*" will be included in linux-next)
origin.patch
* fsnotify-avoid-spurious-emfile-errors-from-inotify_init.patch
* time-add-missing-implementation-for-timespec64_add_safe.patch
* fs-poll-select-recvmmsg-use-timespec64-for-timeout-events.patch
* time-remove-timespec_add_safe.patch
* scripts-decode_stacktracesh-handle-symbols-in-modules.patch
* scripts-spellingtxt-add-fimware-misspelling.patch
* scripts-bloat-o-meter-print-percent-change.patch
* debugobjects-make-fixup-functions-return-bool-instead-of-int.patch
* debugobjects-correct-the-usage-of-fixup-call-results.patch
* workqueue-update-debugobjects-fixup-callbacks-return-type.patch
* timer-update-debugobjects-fixup-callbacks-return-type.patch
* rcu-update-debugobjects-fixup-callbacks-return-type.patch
* percpu_counter-update-debugobjects-fixup-callbacks-return-type.patch
* documentation-update-debugobjects-doc.patch
* debugobjects-insulate-non-fixup-logic-related-to-static-obj-from-fixup-callbacks.patch
* ocfs2-error-code-comments-and-amendments-the-comment-of-ocfs2_extended_slot-should-be-0x08.patch
* ocfs2-clean-up-an-unused-variable-wants_rotate-in-ocfs2_truncate_rec.patch
* ocfs2-clean-up-unused-parameter-count-in-o2hb_read_block_input.patch
* ocfs2-clean-up-an-unuseful-goto-in-ocfs2_put_slot-function.patch
* padata-removed-unused-code.patch
* kernel-padata-hide-unused-functions.patch
* mm-slab-fix-the-theoretical-race-by-holding-proper-lock.patch
* mm-slab-remove-bad_alien_magic-again.patch
* mm-slab-drain-the-free-slab-as-much-as-possible.patch
* mm-slab-factor-out-kmem_cache_node-initialization-code.patch
* mm-slab-clean-up-kmem_cache_node-setup.patch
* mm-slab-dont-keep-free-slabs-if-free_objects-exceeds-free_limit.patch
* mm-slab-racy-access-modify-the-slab-color.patch
* mm-slab-make-cache_grow-handle-the-page-allocated-on-arbitrary-node.patch
* mm-slab-separate-cache_grow-to-two-parts.patch
* mm-slab-refill-cpu-cache-through-a-new-slab-without-holding-a-node-lock.patch
* mm-slab-lockless-decision-to-grow-cache.patch
* mm-slub-replace-kick_all_cpus_sync-with-synchronize_sched-in-kmem_cache_shrink.patch
* mm-slab-freelist-randomization-v4.patch
* mm-slab-remove-zone_dma_flag.patch
* mm-slubc-fix-sysfs-filename-in-comment.patch
* mm-page_ref-use-page_ref-helper-instead-of-direct-modification-of-_count.patch
* mm-rename-_count-field-of-the-struct-page-to-_refcount.patch
* compilerh-add-support-for-malloc-attribute.patch
* include-linux-apply-__malloc-attribute.patch
* include-linux-nodemaskh-create-next_node_in-helper.patch
* mm-hugetlb-optimize-minimum-size-min_size-accounting.patch
* mm-hugetlb-introduce-hugetlb_bad_size.patch
* arm64-mm-use-hugetlb_bad_size.patch
* metag-mm-use-hugetlb_bad_size.patch
* powerpc-mm-use-hugetlb_bad_size.patch
* tile-mm-use-hugetlb_bad_size.patch
* x86-mm-use-hugetlb_bad_size.patch
* mm-hugetlb-is_vm_hugetlb_page-can-be-boolean.patch
* mm-memory_hotplug-is_mem_section_removable-can-be-boolean.patch
* mm-vmalloc-is_vmalloc_addr-can-be-boolean.patch
* mm-mempolicy-vma_migratable-can-be-boolean.patch
* mm-memcontrolc-mem_cgroup_select_victim_node-clarify-comment.patch
* mm-page_alloc-remove-useless-parameter-of-__free_pages_boot_core.patch
* mm-hugetlbc-use-first_memory_node.patch
* mm-mempolicyc-offset_il_node-document-and-clarify.patch
* mm-rmap-replace-bug_onanon_vma-degree-with-vm_warn_on.patch
* mm-compaction-wrap-calculating-first-and-last-pfn-of-pageblock.patch
* mm-compaction-reduce-spurious-pcplist-drains.patch
* mm-compaction-skip-blocks-where-isolation-fails-in-async-direct-compaction.patch
* mm-highmem-simplify-is_highmem.patch
* mm-uninline-page_mapped.patch
* mm-hugetlb-add-same-zone-check-in-pfn_range_valid_gigantic.patch
* mm-memory_hotplug-add-comment-to-some-functions-related-to-memory-hotplug.patch
* mm-vmstat-add-zone-range-overlapping-check.patch
* mm-page_owner-add-zone-range-overlapping-check.patch
* power-add-zone-range-overlapping-check.patch
* mm-writeback-correct-dirty-page-calculation-for-highmem.patch
* mm-page_alloc-correct-highmem-memory-statistics.patch
* mm-highmem-make-nr_free_highpages-handles-all-highmem-zones-by-itself.patch
* mm-vmstat-make-node_page_state-handles-all-zones-by-itself.patch
* mm-mmap-kill-hook-arch_rebalance_pgtables.patch
* mm-update_lru_size-warn-and-reset-bad-lru_size.patch
* mm-update_lru_size-do-the-__mod_zone_page_state.patch
* mm-use-__setpageswapbacked-and-dont-clearpageswapbacked.patch
* tmpfs-preliminary-minor-tidyups.patch
* tmpfs-mem_cgroup-charge-fault-to-vm_mm-not-current-mm.patch
* mm-proc-sys-vm-stat_refresh-to-force-vmstat-update.patch
* huge-mm-move_huge_pmd-does-not-need-new_vma.patch
* huge-pagecache-extend-mremap-pmd-rmap-lockout-to-files.patch
* arch-fix-has_transparent_hugepage.patch
* memory_hotplug-introduce-config_memory_hotplug_default_online.patch
* memory_hotplug-introduce-memhp_default_state=-command-line-parameter.patch
* mm-oom-move-gfp_nofs-check-to-out_of_memory.patch
* oom-oom_reaper-try-to-reap-tasks-which-skip-regular-oom-killer-path.patch
* mm-oom_reaper-clear-tif_memdie-for-all-tasks-queued-for-oom_reaper.patch
* mm-page_alloc-only-check-pagecompound-for-high-order-pages.patch
* mm-page_alloc-use-new-pageanonhead-helper-in-the-free-page-fast-path.patch
* mm-page_alloc-reduce-branches-in-zone_statistics.patch
* mm-page_alloc-inline-zone_statistics.patch
* mm-page_alloc-inline-the-fast-path-of-the-zonelist-iterator.patch
* mm-page_alloc-use-__dec_zone_state-for-order-0-page-allocation.patch
* mm-page_alloc-avoid-unnecessary-zone-lookups-during-pageblock-operations.patch
* mm-page_alloc-convert-alloc_flags-to-unsigned.patch
* mm-page_alloc-convert-nr_fair_skipped-to-bool.patch
* mm-page_alloc-remove-unnecessary-local-variable-in-get_page_from_freelist.patch
* mm-page_alloc-remove-unnecessary-initialisation-in-get_page_from_freelist.patch
* mm-page_alloc-remove-unnecessary-initialisation-from-__alloc_pages_nodemask.patch
* mm-page_alloc-simplify-last-cpupid-reset.patch
* mm-page_alloc-move-__gfp_hardwall-modifications-out-of-the-fastpath.patch
* mm-page_alloc-check-once-if-a-zone-has-isolated-pageblocks.patch
* mm-page_alloc-shorten-the-page-allocator-fast-path.patch
* mm-page_alloc-reduce-cost-of-fair-zone-allocation-policy-retry.patch
* mm-page_alloc-shortcut-watermark-checks-for-order-0-pages.patch
* mm-page_alloc-avoid-looking-up-the-first-zone-in-a-zonelist-twice.patch
* mm-page_alloc-remove-field-from-alloc_context.patch
* mm-page_alloc-check-multiple-page-fields-with-a-single-branch.patch
* mm-page_alloc-un-inline-the-bad-part-of-free_pages_check.patch
* mm-page_alloc-pull-out-side-effects-from-free_pages_check.patch
* mm-page_alloc-remove-unnecessary-variable-from-free_pcppages_bulk.patch
* mm-page_alloc-inline-pageblock-lookup-in-page-free-fast-paths.patch
* cpuset-use-static-key-better-and-convert-to-new-api.patch
* mm-page_alloc-defer-debugging-checks-of-freed-pages-until-a-pcp-drain.patch
* mm-page_alloc-defer-debugging-checks-of-pages-allocated-from-the-pcp.patch
* mm-page_alloc-dont-duplicate-code-in-free_pcp_prepare.patch
* mm-page_alloc-uninline-the-bad-page-part-of-check_new_page.patch
* mm-page_alloc-restore-the-original-nodemask-if-the-fast-path-allocation-failed.patch
i-need-old-gcc.patch
arch-alpha-kernel-systblss-remove-debug-check.patch
* arm-arch-arm-include-asm-pageh-needs-personalityh.patch
* dax-add-dax_get_unmapped_area-for-pmd-mappings.patch
* ext2-4-xfs-blk-call-dax_get_unmapped_area-for-dax-pmd-mappings.patch
* fs-ext4-fsyncc-generic_file_fsync-call-based-on-barrier-flag.patch
* ocfs2-o2hb-add-negotiate-timer.patch
* ocfs2-o2hb-add-negotiate-timer-v2.patch
* ocfs2-o2hb-add-nego_timeout-message.patch
* ocfs2-o2hb-add-nego_timeout-message-v2.patch
* ocfs2-o2hb-add-negotiate_approve-message.patch
* ocfs2-o2hb-add-negotiate_approve-message-v2.patch
* ocfs2-o2hb-add-some-user-debug-log.patch
* ocfs2-o2hb-add-some-user-debug-log-v2.patch
* ocfs2-o2hb-dont-negotiate-if-last-hb-fail.patch
* ocfs2-o2hb-fix-hb-hung-time.patch
* block-restore-proc-partitions-to-not-display-non-partitionable-removable-devices.patch
mm.patch
* mm-workingset-only-do-workingset-activations-on-reads.patch
* mm-filemap-only-do-access-activations-on-reads.patch
* mm-vmscan-reduce-size-of-inactive-file-list.patch
* vmscan-consider-classzone_idx-in-compaction_ready.patch
* mm-compaction-change-compact_-constants-into-enum.patch
* mm-compaction-cover-all-compaction-mode-in-compact_zone.patch
* mm-compaction-distinguish-compact_deferred-from-compact_skipped.patch
* mm-compaction-distinguish-between-full-and-partial-compact_complete.patch
* mm-compaction-update-compaction_result-ordering.patch
* mm-compaction-simplify-__alloc_pages_direct_compact-feedback-interface.patch
* mm-compaction-abstract-compaction-feedback-to-helpers.patch
* mm-compaction-abstract-compaction-feedback-to-helpers-fix.patch
* mm-oom-rework-oom-detection.patch
* mm-throttle-on-io-only-when-there-are-too-many-dirty-and-writeback-pages.patch
* mm-throttle-on-io-only-when-there-are-too-many-dirty-and-writeback-pages-fix.patch
* mm-oom-protect-costly-allocations-some-more.patch
* mm-oom-protect-costly-allocations-some-more-fix.patch
* mm-consider-compaction-feedback-also-for-costly-allocation.patch
* mm-oom-compaction-prevent-from-should_compact_retry-looping-for-ever-for-costly-orders.patch
* mm-oom-compaction-prevent-from-should_compact_retry-looping-for-ever-for-costly-orders-fix.patch
* mm-oom-protect-costly-allocations-some-more-for-config_compaction.patch
* mm-oom-protect-costly-allocations-some-more-for-config_compaction-checkpatch-fixes.patch
* mm-oom_reaper-hide-oom-reaped-tasks-from-oom-killer-more-carefully.patch
* mm-oom_reaper-do-not-mmput-synchronously-from-the-oom-reaper-context.patch
* mm-oom_reaper-do-not-mmput-synchronously-from-the-oom-reaper-context-fix.patch
* oom-consider-multi-threaded-tasks-in-task_will_free_mem.patch
* mmoom-speed-up-select_bad_process-loop.patch
* mm-thp-simplify-the-implementation-of-mk_huge_pmd.patch
* memory-failure-replace-mce-with-memory-failure.patch
* memory-failure-replace-mce-with-memory-failure-fix.patch
* mm-memblock-move-memblock_addreserve_region-into-memblock_addreserve.patch
* mm-vmalloc-keep-a-separate-lazy-free-list.patch
* mm-fix-incorrect-pfn-passed-to-untrack_pfn-in-remap_pfn_range-v2.patch
* mm-enable-rlimit_data-by-default-with-workaround-for-valgrind.patch
* tmpfs-fix-vm_mayshare-mappings-for-nommu.patch
* mm-hugetlb_cgroup-round-limit_in_bytes-down-to-hugepage-size.patch
* mm-tighten-fault_in_pages_writeable.patch
* mm-put-activate_page_pvecs-and-others-pagevec-together.patch
* include-linux-hugetlb-clean-up-code.patch
* include-linux-hugetlbh-use-bool-instead-of-int-for-hugepage_migration_supported.patch
* mm-fix-commmets-if-sparsemem-pgdata-doesnt-have-page_ext.patch
* documentation-vm-fix-spelling-mistakes.patch
* mmwriteback-dont-use-memory-reserves-for-wb_start_writeback.patch
* use-existing-helper-to-convert-on-off-to-boolean.patch
* mm-use-unsigned-long-constant-for-page-flags.patch
* memcg-fix-stale-mem_cgroup_force_empty-comment.patch
* vmstat-get-rid-of-the-ugly-cpu_stat_off-variable-v2.patch
* vmstat-get-rid-of-the-ugly-cpu_stat_off-variable-v2-fix.patch
* mm-thp-microoptimize-compound_mapcount.patch
* mm-thp-split_huge_pmd_address-comment-improvement.patch
* z3fold-the-3-fold-allocator-for-compressed-pages.patch
* mm-add-config-option-to-select-the-initial-overcommit-mode.patch
* mm-memblockc-remove-unnecessary-always-true-comparison.patch
* userfaultfd-dont-pin-the-user-memory-in-userfaultfd_file_create.patch
* memory-hotplug-add-move_pfn_range.patch
* memory-hotplug-more-general-validation-of-zone-during-online.patch
* memory-hotplug-use-zone_can_shift-for-sysfs-valid_zones-attribute.patch
* mm-use-phys_addr_t-for-reserve_bootmem_region-arguments.patch
* mm-make-faultaround-produce-old-ptes.patch
* mm-disable-fault-around-on-emulated-access-bit-architecture.patch
* mm-kasan-fix-to-call-kasan_free_pages-after-poisoning-page.patch
* mm-check_new_page_bad-directly-returns-in-__pg_hwpoison-case.patch
* mm-increase-safety-margin-provided-by-pf_less_throttle.patch
* mm-thp-khugepaged-should-scan-when-sleep-value-is-written.patch
* mm-page_is_guard-return-false-when-page_ext-arrays-are-not-allocated-yet.patch
* mm-compact-fix-zoneindex-in-compact.patch
* mm-compact-fix-zoneindex-in-compact-fix.patch
* mm-migrate-increment-fail-count-on-enomem.patch
* mm-memblock-if-nr_new-is-0-just-return.patch
* mm-make-optimistic-check-for-swapin-readahead.patch
* mm-make-optimistic-check-for-swapin-readahead-fix-2.patch
* mm-make-swapin-readahead-to-improve-thp-collapse-rate.patch
* mm-make-swapin-readahead-to-improve-thp-collapse-rate-fix.patch
* mm-make-swapin-readahead-to-improve-thp-collapse-rate-fix-2.patch
* mm-make-swapin-readahead-to-improve-thp-collapse-rate-fix-3.patch
* mm-vmstat-calculate-particular-vm-event.patch
* mm-thp-avoid-unnecessary-swapin-in-khugepaged.patch
* mm-thp-avoid-unnecessary-swapin-in-khugepaged-fix.patch
* mm-kasan-initial-memory-quarantine-implementation.patch
* mm-kasan-initial-memory-quarantine-implementation-v8.patch
* mm-kasan-initial-memory-quarantine-implementation-v9.patch
* mm-kasan-dont-call-kasan_krealloc-from-ksize.patch
* mm-kasan-add-a-ksize-test.patch
* mm-kasan-print-name-of-mem-caller-in-report.patch
* mm-kasan-add-api-to-check-memory-regions.patch
* x86-kasan-instrument-user-memory-access-api.patch
* x86-kasan-instrument-user-memory-access-api-fix.patch
* kasan-tests-add-tests-for-user-memory-access-functions.patch
* zsmalloc-use-first_page-rather-than-page.patch
* zsmalloc-clean-up-many-bug_on.patch
* zsmalloc-reordering-function-parameter.patch
* zsmalloc-remove-unused-pool-param-in-obj_free.patch
* zsmalloc-require-gfp-in-zs_malloc.patch
* zsmalloc-require-gfp-in-zs_malloc-v2.patch
* zram-user-per-cpu-compression-streams.patch
* zram-user-per-cpu-compression-streams-fix.patch
* mm-zswap-use-workqueue-to-destroy-pool.patch
* mm-zsmalloc-dont-fail-if-cant-create-debugfs-info.patch
* zram-remove-max_comp_streams-internals.patch
* zram-introduce-per-device-debug_stat-sysfs-node.patch
* zram-introduce-per-device-debug_stat-sysfs-node-update.patch
* zram-introduce-per-device-debug_stat-sysfs-node-update-2.patch
* zram-introduce-per-device-debug_stat-sysfs-node-minchan.patch
* procfs-expose-umask-in-proc-pid-status.patch
* procfs-fixes-pthread-cross-thread-naming-if-pr_dumpable.patch
* procfs-fixes-pthread-cross-thread-naming-if-pr_dumpable-fix.patch
* mn10300-let-exit_fpu-accept-a-task.patch
* exit_thread-remove-empty-bodies.patch
* exit_thread-remove-empty-bodies-fix.patch
* exit_thread-accept-a-task-parameter-to-be-exited.patch
* exit_thread-accept-a-task-parameter-to-be-exited-checkpatch-fixes.patch
* fork-free-thread-in-copy_process-on-failure.patch
* use-pid_t-instead-of-int.patch
* printk-nmi-generic-solution-for-safe-printk-in-nmi.patch
* printk-nmi-warn-when-some-message-has-been-lost-in-nmi-context.patch
* printk-nmi-increase-the-size-of-nmi-buffer-and-make-it-configurable.patch
* printk-nmi-flush-nmi-messages-on-the-system-panic.patch
* lib-switch-config_printk_time-to-int.patch
* printk-allow-different-timestamps-for-printktime.patch
* maintainers-remove-linux-listsopenriscnet.patch
* maintainers-remove-defunct-spear-mailing-list.patch
* maintainers-remove-koichi-yasutake.patch
* lib-vsprintf-simplify-uuid-printing.patch
* ima-use-%pu-to-output-uuid-in-printable-format.patch
* lib-uuid-move-generate_random_uuid-to-uuidc.patch
* lib-uuid-introduce-few-more-generic-helpers-for-uuid.patch
* lib-uuid-introduce-few-more-generic-helpers-for-uuid-fix.patch
* lib-uuid-remove-fsf-address.patch
* sysctl-use-generic-uuid-library.patch
* efi-redefine-type-constant-macro-from-generic-code.patch
* efivars-use-generic-uuid-library.patch
* genhd-move-to-use-generic-uuid-library.patch
* ldm-use-generic-uuid-library.patch
* wmi-use-generic-uuid-library.patch
* radix-tree-introduce-radix_tree_empty.patch
* radix-tree-test-suite-fix-build.patch
* radix-tree-test-suite-add-tests-for-radix_tree_locate_item.patch
* radix-tree-test-suite-allow-testing-other-fan-out-values.patch
* radix-tree-test-suite-keep-regression-test-runs-short.patch
* radix-tree-test-suite-rebuild-when-headers-change.patch
* radix-tree-remove-unused-looping-macros.patch
* introduce-config_radix_tree_multiorder.patch
* radix-tree-add-missing-sibling-entry-functionality.patch
* radix-tree-fix-sibling-entry-insertion.patch
* radix-tree-fix-deleting-a-multi-order-entry-through-an-alias.patch
* radix-tree-remove-restriction-on-multi-order-entries.patch
* radix-tree-introduce-radix_tree_load_root.patch
* radix-tree-fix-extending-the-tree-for-multi-order-entries-at-offset-0.patch
* radix-tree-test-suite-start-adding-multiorder-tests.patch
* radix-tree-fix-several-shrinking-bugs-with-multiorder-entries.patch
* radix-tree-rewrite-__radix_tree_lookup.patch
* radix-tree-fix-multiorder-bug_on-in-radix_tree_insert.patch
* radix-tree-add-support-for-multi-order-iterating.patch
* radix-tree-test-suite-multi-order-iteration-test.patch
* radix-tree-rewrite-radix_tree_tag_set.patch
* radix-tree-rewrite-radix_tree_tag_clear.patch
* radix-tree-rewrite-radix_tree_tag_get.patch
* radix-tree-test-suite-add-multi-order-tag-test.patch
* radix-tree-fix-radix_tree_create-for-sibling-entries.patch
* radix-tree-rewrite-radix_tree_locate_item.patch
* radix-tree-rewrite-radix_tree_locate_item-fix.patch
* radix-tree-add-test-for-radix_tree_locate_item.patch
* radix-tree-fix-radix_tree_range_tag_if_tagged-for-multiorder-entries.patch
* radix-tree-fix-radix_tree_dump-for-multi-order-entries.patch
* radix-tree-add-copyright-statements.patch
* drivers-hwspinlock-use-correct-radix-tree-api.patch
* radix-tree-miscellaneous-fixes.patch
* radix-tree-split-node-path-into-offset-and-height.patch
* radix-tree-replace-node-height-with-node-shift.patch
* radix-tree-remove-a-use-of-root-height-from-delete_node.patch
* radix-tree-test-suite-remove-dependencies-on-height.patch
* radix-tree-remove-root-height.patch
* radix-tree-rename-indirect_ptr-to-internal_node.patch
* radix-tree-rename-ptr_to_indirect-to-node_to_entry.patch
* radix-tree-rename-indirect_to_ptr-to-entry_to_node.patch
* radix-tree-rename-radix_tree_is_indirect_ptr.patch
* radix-tree-change-naming-conventions-in-radix_tree_shrink.patch
* radix-tree-tidy-up-next_chunk.patch
* radix-tree-tidy-up-range_tag_if_tagged.patch
* radix-tree-tidy-up-__radix_tree_create.patch
* radix-tree-introduce-radix_tree_replace_clear_tags.patch
* radix-tree-make-radix_tree_descend-more-useful.patch
* dax-move-radix_dax_-definitions-to-daxc.patch
* radix-tree-free-up-the-bottom-bit-of-exceptional-entries-for-reuse.patch
* lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean.patch
* lib-gcd-use-binary-gcd-algorithm-instead-of-euclidean-fix.patch
* lib-add-crc64-ecma-module.patch
* checkpatch-add-prefer_is_enabled-test.patch
* checkpatch-improve-constant_comparison-test-for-structure-members.patch
* checkpatch-add-test-for-keywords-not-starting-on-tabstops.patch
* checkpatch-whine-about-access_once.patch
* checkpatch-advertise-the-fix-and-fix-inplace-options-more.patch
* checkpatch-add-list-types-to-show-message-types-to-show-or-ignore.patch
* checkpatch-add-support-to-check-already-applied-git-commits.patch
* checkpatch-reduce-number-of-git-log-calls-with-git.patch
* checkpatch-improve-git-commit-count-shortcut.patch
* fs-efs-fix-return-value.patch
* init-mainc-simplify-initcall_blacklisted.patch
* kprobes-add-the-tls-argument-for-j_do_fork.patch
* kprobes-add-a-new-module-parameter.patch
* kprobes-print-out-the-symbol-name-for-the-hooks.patch
* fs-befs-datastreamc-befs_read_datastream-remove-unneeded-initialization-to-null.patch
* fs-befs-datastreamc-befs_read_lsymlink-remove-unneeded-initialization-to-null.patch
* fs-befs-datastreamc-befs_find_brun_dblindirect-remove-unneeded-initializations-to-null.patch
* fs-befs-linuxvfsc-befs_get_block-remove-unneeded-initialization-to-null.patch
* fs-befs-linuxvfsc-befs_iget-remove-unneeded-initialization-to-null.patch
* fs-befs-linuxvfsc-befs_iget-remove-unneeded-raw_inode-initialization-to-null.patch
* fs-befs-linuxvfsc-befs_iget-remove-unneeded-befs_nio-initialization-to-null.patch
* fs-befs-ioc-befs_bread_iaddr-remove-unneeded-initialization-to-null.patch
* fs-befs-ioc-befs_bread-remove-unneeded-initialization-to-null.patch
* nilfs2-constify-nilfs_sc_operations-structures.patch
* nilfs2-fix-white-space-issue-in-nilfs_mount.patch
* nilfs2-remove-space-before-comma.patch
* nilfs2-remove-fsf-mailing-address-from-gpl-notices.patch
* nilfs2-clean-up-old-e-mail-addresses.patch
* maintainers-add-web-link-for-nilfs-project.patch
* nilfs2-clarify-permission-to-replicate-the-design.patch
* nilfs2-get-rid-of-nilfs_mdt_mark_block_dirty.patch
* nilfs2-move-cleanup-code-of-metadata-file-from-inode-routines.patch
* nilfs2-replace-__attribute__packed-with-__packed.patch
* nilfs2-add-missing-line-spacing.patch
* nilfs2-clean-trailing-semicolons-in-macros.patch
* nilfs2-clean-trailing-semicolons-in-macros-fix.patch
* nilfs2-do-not-emit-extra-newline-on-nilfs_warning-and-nilfs_error.patch
* nilfs2-remove-space-before-semicolon.patch
* nilfs2-fix-code-indent-coding-style-issue.patch
* nilfs2-avoid-bare-use-of-unsigned.patch
* nilfs2-remove-unnecessary-else-after-return-or-break.patch
* nilfs2-remove-loops-of-single-statement-macros.patch
* nilfs2-fix-block-comments.patch
* wait-ptrace-assume-__wall-if-the-child-is-traced.patch
* wait-allow-sys_waitid-to-accept-__wnothread-__wclone-__wall.patch
* signal-make-oom_flags-a-bool.patch
* kernel-signalc-convert-printkkern_level-to-pr_level.patch
* signal-move-the-sig-sigrtmin-check-into-siginmasksig.patch
* allocate-idle-task-for-a-cpu-always-on-its-local-node.patch
* allocate-idle-task-for-a-cpu-always-on-its-local-node-fix.patch
* exec-remove-the-no-longer-needed-remove_arg_zero-free_arg_page.patch
* kexec-introduce-a-protection-mechanism-for-the-crashkernel-reserved-memory.patch
* kexec-provide-arch_kexec_protectunprotect_crashkres.patch
* kexec-make-a-pair-of-map-unmap-reserved-pages-in-error-path.patch
* kexec-do-a-cleanup-for-function-kexec_load.patch
* s390-kexec-consolidate-crash_map-unmap_reserved_pages-and-arch_kexec_protectunprotect_crashkres.patch
* kdump-fix-gdb-macros-work-work-with-newer-and-64-bit-kernels.patch
* kdump-vmcoreinfo-report-actual-value-of-phys_base.patch
* futex-fix-shared-futex-operations-on-nommu.patch
* rtsx_usb_ms-use-schedule_timeout_idle-in-polling-loop-v2.patch
* arch-defconfig-remove-config_resource_counters.patch
* scripts-gdb-adjust-module-reference-counter-reported-by-lx-lsmod.patch
* scripts-gdb-provide-linux-constants.patch
* scripts-gdb-provide-kernel-list-item-generators.patch
* scripts-gdb-convert-modules-usage-to-lists-functions.patch
* scripts-gdb-provide-exception-catching-parser.patch
* scripts-gdb-support-config_modules-gracefully.patch
* scripts-gdb-provide-a-dentry_name-vfs-path-helper.patch
* scripts-gdb-add-io-resource-readers.patch
* scripts-gdb-add-mount-point-list-command.patch
* scripts-gdb-add-cpu-iterators.patch
* scripts-gdb-cast-cpu-numbers-to-integer.patch
* scripts-gdb-add-a-radix-tree-parser.patch
* scripts-gdb-add-documentation-example-for-radix-tree.patch
* scripts-gdb-add-lx_thread_info_by_pid-helper.patch
* scripts-gdb-improve-types-abstraction-for-gdb-python-scripts.patch
* scripts-gdb-fix-issue-with-dmesgpy-and-python-3x.patch
* scripts-gdb-decode-bytestream-on-dmesg-for-python3.patch
* maintainers-add-co-maintainer-for-scripts-gdb.patch
* ipc-semc-fix-complex_count-vs-simple-op-race.patch
* ipc-msgc-msgsnd-use-freezable-blocking-call.patch
* msgrcv-use-freezable-blocking-call.patch
linux-next.patch
linux-next-git-rejects.patch
linux-next-rejects.patch
* mm-make-optimistic-check-for-swapin-readahead-fix.patch
* drivers-net-wireless-intel-iwlwifi-dvm-calibc-fix-min-warning.patch
* mm-make-mmap_sem-for-write-waits-killable-for-mm-syscalls.patch
* mm-make-vm_mmap-killable.patch
* mm-make-vm_munmap-killable.patch
* mm-aout-handle-vm_brk-failures.patch
* mm-elf-handle-vm_brk-error.patch
* mm-make-vm_brk-killable.patch
* mm-proc-make-clear_refs-killable.patch
* mm-fork-make-dup_mmap-wait-for-mmap_sem-for-write-killable.patch
* ipc-shm-make-shmem-attach-detach-wait-for-mmap_sem-killable.patch
* vdso-make-arch_setup_additional_pages-wait-for-mmap_sem-for-write-killable.patch
* coredump-make-coredump_wait-wait-for-mmap_sem-for-write-killable.patch
* aio-make-aio_setup_ring-killable.patch
* exec-make-exec-path-waiting-for-mmap_sem-killable.patch
* prctl-make-pr_set_thp_disable-wait-for-mmap_sem-killable.patch
* uprobes-wait-for-mmap_sem-for-write-killable.patch
* drm-i915-make-i915_gem_mmap_ioctl-wait-for-mmap_sem-killable.patch
* drm-radeon-make-radeon_mn_get-wait-for-mmap_sem-killable.patch
* drm-amdgpu-make-amdgpu_mn_get-wait-for-mmap_sem-killable.patch
* drm-amdgpu-make-amdgpu_mn_get-wait-for-mmap_sem-killable-fix.patch
* kgdb-depends-on-vt.patch
mm-add-strictlimit-knob-v2.patch
make-sure-nobodys-leaking-resources.patch
releasing-resources-with-children.patch
make-frame_pointer-default=y.patch
kernel-forkc-export-kernel_thread-to-modules.patch
mutex-subsystem-synchro-test-module.patch
slab-leaks3-default-y.patch
add-debugging-aid-for-memory-initialisation-problems.patch
workaround-for-a-pci-restoring-bug.patch
^ permalink raw reply
* Re: mmotm 2016-05-19-18-01 uploaded
From: Andrew Morton @ 2016-05-20 2:59 UTC (permalink / raw)
To: Stephen Rothwell
Cc: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next,
mhocko, broonie
In-Reply-To: <20160520123715.191726f5@canb.auug.org.au>
On Fri, 20 May 2016 12:37:15 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> On Thu, 19 May 2016 18:02:16 -0700 akpm@linux-foundation.org wrote:
> >
> > The mm-of-the-moment snapshot 2016-05-19-18-01 has been uploaded to
> >
> > http://www.ozlabs.org/~akpm/mmotm/
> .
> .
> > mm-page_alloc-defer-debugging-checks-of-pages-allocated-from-the-pcp.patch
> > mm-page_alloc-dont-duplicate-code-in-free_pcp_prepare.patch
> > mm-page_alloc-uninline-the-bad-page-part-of-check_new_page.patch
> > mm-page_alloc-restore-the-original-nodemask-if-the-fast-path-allocation-failed.patch
>
> Is that all there is? No linux-next patch?
oop, let me try that again.
^ permalink raw reply
* Re: mmotm 2016-05-19-18-01 uploaded
From: Stephen Rothwell @ 2016-05-20 2:37 UTC (permalink / raw)
To: akpm
Cc: mm-commits, linux-kernel, linux-mm, linux-fsdevel, linux-next,
mhocko, broonie
In-Reply-To: <573e6218.YQH2A+YBUHmPqyvU%akpm@linux-foundation.org>
Hi Andrew,
On Thu, 19 May 2016 18:02:16 -0700 akpm@linux-foundation.org wrote:
>
> The mm-of-the-moment snapshot 2016-05-19-18-01 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
.
.
> mm-page_alloc-defer-debugging-checks-of-pages-allocated-from-the-pcp.patch
> mm-page_alloc-dont-duplicate-code-in-free_pcp_prepare.patch
> mm-page_alloc-uninline-the-bad-page-part-of-check_new_page.patch
> mm-page_alloc-restore-the-original-nodemask-if-the-fast-path-allocation-failed.patch
Is that all there is? No linux-next patch?
--
Cheers,
Stephen Rothwell
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox