From: David Woodhouse
The GPL does not permit us to link against the OpenSSL library. Use
LGPL for sign-file and extract-file instead.
Reported-by: Julian Andres Klode
Signed-off-by: David Woodhouse
Signed-off-by: David Howells
Reviewed-by: Julian Andres Klode
---
scripts/extract-cert.c |
On 15.09.2015 17:27, Eric W. Biederman wrote:
Konstantin Khlebnikov writes:
pid_t getvpid(pid_t pid, pid_t source, pid_t target);
This syscall converts pid from one pid-ns into pid in another pid-ns:
it takes @pid in namespace of @source task (zero for current) and
returns related pid in name
On Mon, Sep 14, 2015 at 09:00:51PM +0100, Steve Muckle wrote:
> Hi Patrick,
>
> On 09/11/2015 04:09 AM, Patrick Bellasi wrote:
> >> It's also worth noting that mobile vendors typically add all sorts of
> >> hacks on top of the existing cpufreq governors which further complicate
> >> policy.
> >
>
On Mon, Sep 14, 2015 at 4:37 PM, Yinghai Lu wrote:
> On Mon, Sep 14, 2015 at 1:21 PM, Bjorn Helgaas wrote:
>> I spent a couple hours trying to understand the v3 version of this
>> patch, and I gave you some detailed examples and questions. If you
>> want me to look at v4, I expect you to try to
Hi Jiry,
Maybe you would want to consider this:
https://patchwork.ozlabs.org/patch/459088/
It has already found its ways in other stable kernels, despite not being
cc'ed to stable.
Regards,
Nikolay
On 09/15/2015 05:22 PM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the
> --recursive-includes is already a parameter.
I am unsure if its effect on source code analysis speed will matter here.
> size_t is also unsigned.
Will such a specification work also without an explicit SmPL typedef?
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe
With the split into struct clk and struct clk_core, clocks lost the
ability for nested __clk_get clkdev calls. While it stays possible to
call __clk_get, the first call to (__)clk_put will clear the struct clk,
making subsequent clk_put calls run into a NULL pointer dereference.
One prime example
From: Dave Airlie
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 7f98ca454ad373fc1b76be804fa7138ff68c1d27 upstream.
We apparantly get a hotplug irq before we've initialised
modesetting,
[drm] Loading R100 Microcode
BUG: unable to handle ker
On Mon, Sep 14, 2015 at 1:27 PM, Andy Whitcroft wrote:
>
> On Sat, Sep 12, 2015 at 03:13:31PM +0300, Tal Shorer wrote:
> > Since my last pull from upstream (today) , I started seeing some
> > checkpatch warnings regarding suspect code indent I believe are false
> > positive. Take this code for exa
On Tue, Sep 15, 2015 at 03:44:09PM +0100, Will Deacon wrote:
> On Tue, Sep 15, 2015 at 03:31:35PM +0100, Catalin Marinas wrote:
> > On Tue, Sep 15, 2015 at 07:20:08PM +0800, Leo Yan wrote:
> > > On Fri, Aug 21, 2015 at 04:54:25PM +0100, Catalin Marinas wrote:
> > > > On Fri, Aug 21, 2015 at 05:14:4
From: Eric Dumazet
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit d339727c2b1a10f25e6636670ab6e1841170e328 ]
User space can crash kernel with
ip link add ifb10 numtxqueues 10 type ifb
We must replace a BUG_ON() by proper tes
From: Mika Westerberg
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 1abf25a25b86dcfe28d243a5af71bd1c9d6de1ef upstream.
Using -1 as platform device id means that the platform driver core will not
assign any id to the device (the device name
Michael Turquette writes:
> Quoting Rhyland Klein (2015-02-17 08:58:29)
>> On 2/15/2015 7:33 AM, Mans Rullgard wrote:
>> > If a mux clock is initialised (by hardware or firmware) with an
>> > invalid parent, its ->get_parent() can return an out of range
>> > index. For example, the generic mux c
From: Stephen Smalley
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit fdd75ea8df370f206a8163786e7470c1277a5064 ]
Calling connect() with an AF_TIPC socket would trigger a series
of error messages from SELinux along the lines of:
SEL
From: Herbert Xu
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 738ac1ebb96d02e0d23bc320302a6ea94c612dec ]
Shared skbs must not be modified and this is crucial for broadcast
and/or multicast paths where we use it as an optimisatio
From: Julian Anastasov
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit e9e4dd3267d0c5234c5c0f47440456b10875dec9 ]
commit 381c759d9916 ("ipv4: Avoid crashing in ip_error")
fixes a problem where processed packet comes from device
wit
From: Timo Teräs
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit fc24f2b2094366da8786f59f2606307e934cea17 ]
Frag needed should be sent only if the inner header asked
to not fragment. Currently fragmentation is broken if the
tunnel
From: Nikolay Aleksandrov
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit f1158b74e54f2e2462ba5e2f45a118246d9d5b43 ]
Since commit b0e9a30dd669 ("bridge: Add vlan id to multicast groups")
there's a check in br_ip_equal() for a match
Hello Greg,
On 10.08.2015 13:47, Vladimir Zapolskiy wrote:
> Hi Greg,
>
> On 10.08.2015 06:27, Greg Kroah-Hartman wrote:
>> On Mon, Aug 10, 2015 at 12:40:02AM +0300, Vladimir Zapolskiy wrote:
>>> This change adds functionality to operate on reserved SRAM partitions
>>> described in device tree fi
On 06/09/15 05:20, Peter Chen wrote:
> On Wed, Sep 02, 2015 at 09:43:38AM -0500, Felipe Balbi wrote:
>> Hi,
>>
>>> +
>>> +static irqreturn_t dwc3_otg_irq(int irq, void *_dwc)
>>> +{
>>> + struct dwc3 *dwc = _dwc;
>>> + irqreturn_t ret = IRQ_NONE;
>>> + u32 reg;
>>> +
>>> + spin_lock(&dwc->l
On 09/15/2015 04:28 PM, Maxime Ripard wrote:
>> +static int sunxican_get_berr_counter(const struct net_device *dev,
>> + struct can_berr_counter *bec)
>> +{
>> +struct sunxican_priv *priv = netdev_priv(dev);
>> +u32 errors;
>> +int err;
>> +
>> +err =
From: Herbert Xu
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 89c22d8c3b278212eef6a8cc66b570bc840a6f5a ]
When we calculate the checksum on the recv path, we store the
result in the skb as an optimisation in case we need the chec
From: Angga
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 4c938d22c88a9ddccc8c55a85e0430e9c62b1ac5 ]
Before commit daad151263cf ("ipv6: Make ipv6_is_mld() inline and use it
from ip6_mc_input().") MLD packets were only processed l
From: Daniel Borkmann
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 4f7d2cdfdde71ffe962399b7020c674050329423 ]
Jason Gunthorpe reported that since commit c02db8c6290b ("rtnetlink: make
SR-IOV VF interface symmetric"), we don't ve
From: Herbert Xu
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit a0a2a6602496a45ae838a96db8b8173794b5d398 ]
The commit 738ac1ebb96d02e0d23bc320302a6ea94c612dec ("net: Clone
skb before setting peeked flag") introduced a use-after-fr
From: Julian Anastasov
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 2c17d27c36dcce2b6bf689f41a46b9e909877c21 ]
Incoming packet should be either in backlog queue or
in RCU read-side section. Otherwise, the final sequence of
flush
From: dingtianhong
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit a951bc1e6ba58f11df5ed5ddc41311e10f5fd20b ]
The "follow" fail_over_mac policy is useful for multiport devices that
either become confused or incur a performance pena
On Tue, Sep 15, 2015 at 03:31:35PM +0100, Catalin Marinas wrote:
> On Tue, Sep 15, 2015 at 07:20:08PM +0800, Leo Yan wrote:
> > On Fri, Aug 21, 2015 at 04:54:25PM +0100, Catalin Marinas wrote:
> > > On Fri, Aug 21, 2015 at 05:14:46PM +0800, Leo Yan wrote:
> > > > On Fri, Aug 21, 2015 at 10:00:43AM
On Tue, 15 Sep 2015, SF Markus Elfring wrote:
> > If you think about removing all u* typedefs
>
> I became interested in the use case to consider more type definitions
> besides the ones which should usually be handled for Linux source files.
>
>
> > it will result in omitting u* related compariso
From: Tilman Schmidt
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit fd98e9419d8d622a4de91f76b306af6aa627aa9c ]
Commit 79901317ce80 ("n_tty: Don't flush buffer when closing ldisc"),
first merged in kernel release 3.10, caused the f
On 2015-09-15 06:36:30, Julia Lawall wrote:
>
>
> On Mon, 14 Sep 2015, Tyler Hicks wrote:
>
> > On 2015-09-13 14:15:21, Julia Lawall wrote:
> > > Remove unneeded NULL test.
> > >
> > > The semantic patch that makes this change is as follows:
> > > (http://coccinelle.lip6.fr/)
> > >
> > > //
>
From: Edward Hyunkoo Jee
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 0848f6428ba3a2e42db124d41ac6f548655735bf ]
When ip_frag_queue() computes positions, it assumes that the passed
sk_buff does not contain L2 headers.
However,
From: Nikolay Aleksandrov
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 06f6d1094aa0992432b1e2a0920b0ee86ccd83bf ]
When the bonding is being unloaded and the netdevice notifier is
unregistered it executes NETDEV_UNREGISTER for ea
From: Eric Dumazet
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 03645a11a570d52e70631838cb786eb4253eb463 ]
ip6_datagram_connect() is doing a lot of socket changes without
socket being locked.
This looks wrong, at least for udp_
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_mass_storage we only need to store in ep->driver
Document the new compatible for Hisilicon Hi6220 mailbox driver.
Signed-off-by: Leo Yan
---
.../bindings/mailbox/hisilicon,hi6220-mailbox.txt | 57 ++
1 file changed, 57 insertions(+)
create mode 100644
Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt
Currently on ARM when is triggered from an interrupt handler
(e.g. a SysRq issued using UART or kbd) the main CPU will wedge for ten
seconds with interrupts masked before issuing a backtrace for every CPU
except itself.
The new backtrace code introduced by commit 96f0e00378d4 ("ARM: add
basic sup
Signed-off-by: Irina Tirdea
Acked-by: Bastien Nocera
---
drivers/input/touchscreen/goodix.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/input/touchscreen/goodix.c
b/drivers/input/touchscreen/goodix.c
index e36162b..6ae28c5 100644
--- a/drivers/input/
From: Jack Morgenstein
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 1c1bf34951e8d17941bf708d1901c47e81b15d55 ]
The port-change event processing in procedure mlx4_eq_int() uses "slave"
as the vf_oper array index. Since the value
On Hi6220, below memory regions in DDR have specific purpose:
0x05e0, - 0x05ef,: For MCU firmware using at runtime;
0x06df,f000 - 0x06df,: For mailbox message data;
0x0740,f000 - 0x0740,: For MCU firmware's section;
0x3e00, - 0x3fff,: For OP-TEE.
This patch reserve
Add driver for Hi6220 mailbox, the mailbox communicates with MCU; for
sending data, it can support two methods for low level implementation:
one is to use interrupt as acknowledge, another is automatic mode which
without any acknowledge. These two methods have been supported in the
driver. For rece
Konstantin Khlebnikov writes:
> pid_t getvpid(pid_t pid, pid_t source, pid_t target);
>
> This syscall converts pid from one pid-ns into pid in another pid-ns:
> it takes @pid in namespace of @source task (zero for current) and
> returns related pid in namespace of @target task (zero for current
Fix comments in code to make them up to date.
composite: claiming endpoint is now done by setting ep->claimed flag,
not ep->driver_data.
epautoconf: usb_ep_autoconfig() and usb_ep_autoconfig_ss() return
claimed endpoint with ep->claimed flag already set.
Signed-off-by: Robert Baldyga
---
drive
Hi6220 mailbox supports up to 32 channels. Each channel is unidirectional
with a maximum message size of 8 words. I/O is performed using register
access (there is no DMA) and the cell raises an interrupt when messages
are received.
This patch series is to implement Hi6220 mailbox driver. It regist
This patch introduces 'enabled' flag in struct usb_ep, and modifies
usb_ep_enable() and usb_ep_disable() functions to encapsulate endpoint
enabled/disabled state. It helps to avoid enabling endpoints which are
already enabled, and disabling endpoints which are already disables.
>From now USB funct
> -Original Message-
> From: Aleksei Mamlin [mailto:mamli...@gmail.com]
> Sent: 15 September, 2015 12:48
> To: Tirdea, Irina
> Cc: Dmitry Torokhov; Bastien Nocera; linux-in...@vger.kernel.org; Mark
> Rutland; Purdila, Octavian; linux-kernel@vger.kernel.org;
> devicet...@vger.kernel.org
>
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_ecm, ep->driver_data was used only for endpoint
After power on, it is recommended that the driver resets the device.
The reset procedure timing is described in the datasheet and is used
at device init (before writing device configuration) and
for power management. It is a sequence of setting the interrupt
and reset pins high/low at specific timi
> If you think about removing all u* typedefs
I became interested in the use case to consider more type definitions
besides the ones which should usually be handled for Linux source files.
> it will result in omitting u* related comparisons,
> unless you use --recursive-includes option.
How do
> This patch adds filemap_fdatawait_keep_errors() for call sites where
> writeback error is not handled so that they don't clear error status.
Patch looks good to me.
Acked-by: Andi Kleen
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Add several enhancements to the Goodix touchscreen driver.
This version includes a couple of fixes.
Thanks,
Irina
Changes in v6:
- skip runtime power manangent calls in open/close if the device
ACPI/DT configuration does not declare interrupt and reset gpio pins.
- reset the device before start
Each of the Goodix devices supported by this driver has a fixed size for
the configuration information registers. The size varies depending on the
device and is specified in the datasheet.
Use the proper configuration length as specified in the datasheet for
each device model, so we do not read mo
Implement suspend/resume for goodix driver.
The suspend and resume process uses the gpio pins.
If the device ACPI/DT information does not declare gpio pins,
suspend/resume will not be available for these devices.
This is based on Goodix datasheets for GT911 and GT9271
and on Goodix driver gt9xx.c
Goodix devices have a configuration information register area that
specify various parameters for the device. The configuration information
has a specific format described in the Goodix datasheet. It includes X/Y
resolution, maximum supported touch points, interrupt flags, various
sesitivity factor
Use goodix_i2c_write_u8 instead of i2c_master_send to simplify code.
Signed-off-by: Irina Tirdea
---
drivers/input/touchscreen/goodix.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/input/touchscreen/goodix.c
b/drivers/input/touchscreen/goodix.c
index 1993b6c
Add ESD (Electrostatic Discharge) protection mechanism.
The driver enables ESD protection in HW and checks a register
to determine if ESD occurred. If ESD is signalled by the HW,
the driver will reset the device.
The ESD poll time (in ms) can be set through the sysfs property
esd_timeout. If it i
Goodix devices can be configured by writing custom data to the device at
init. The configuration data is read with request_firmware from
"goodix__cfg.bin", where is the product id read from the device
(e.g.: goodix_911_cfg.bin for Goodix GT911, goodix_9271_cfg.bin for
GT9271).
The configuration i
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_ncm, ep->driver_data was used only for endpoint
Add support for runtime power management so that the device is
turned off when not used (when the userspace holds no open
handles of the input device). The device uses autosuspend with a
default delay of 2 seconds, so the device will suspend if no
handles to it are open for 2 seconds.
The runtime
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_obex, ep->driver_data was used only for endpoint
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_printer we only need to store in ep->driver_data
On Tue, Sep 15, 2015 at 07:20:08PM +0800, Leo Yan wrote:
> On Fri, Aug 21, 2015 at 04:54:25PM +0100, Catalin Marinas wrote:
> > On Fri, Aug 21, 2015 at 05:14:46PM +0800, Leo Yan wrote:
> > > On Fri, Aug 21, 2015 at 10:00:43AM +0100, Catalin Marinas wrote:
> > > > On Fri, Aug 21, 2015 at 11:40:22AM
On Mon, Sep 14, 2015 at 07:50:02PM +0200, Peter Senna Tschudin wrote:
> On Mon, Sep 14, 2015 at 5:01 PM, Felipe Balbi wrote:
> > On Sat, Sep 12, 2015 at 03:14:50PM +0200, Peter Senna Tschudin wrote:
> >> >> Should these files be consolidated? And if so how?
> >> > if you can find an easy way, that
On Thu, 2015-08-27 at 11:24 +0100, George Dunlap wrote:
> On 08/18/2015 04:55 PM, Dario Faggioli wrote:
> > *** Intel(R) Xeon(R) X5650 @ 2.67GHz
> > *** pCPUs 48DOM0 vCPUS 16
> > *** RAM393138 MB DOM0 Memory 9955 MB
> > *** NUMA nodes 2
> > ===
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_uac1, ep->driver_data was used only for endpoint
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_serial, ep->driver_data was used only for endpoi
On Tue, Sep 15, 2015 at 08:08:01PM +0600, Alexander Kuleshov wrote:
> The provides offset_in_page() macro. Let's use already
> predefined macro instead of (addr & ~PAGE_MASK).
>
> Signed-off-by: Alexander Kuleshov
Acked-by: Tejun Heo
Please feel free to route with other patches.
Thanks.
--
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_ecm, ep->driver_data was used only for endpoint
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_uac2, ep->driver_data was used only for endpoint
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of u_ether we only need to store in ep->driver_data p
On Tue, 2015-09-15 at 17:15 +0300, Alexander Shishkin wrote:
>
> > It seems to me that current->ext_err_code needs to be cleared on
> > each system call entry (except for your special prctl() of
> > course!).
>
> I'd say, it should be up to the program to decide for how long they
> want to kee
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of dbgp, ep->driver_data was used only for endpoint c
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_phonet we only need to store in ep->driver_data
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of tcm, ep->driver_data was used only for endpoint cl
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_uvc, ep->driver_data was used only for endpoint
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_rndis, ep->driver_data was used only for endpoin
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of u_serial ep->driver_data stores pointer to struct
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_midi we only need to store in ep->driver_data po
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_subset, ep->driver_data was used only for endpoi
On Tue, Sep 15, 2015 at 01:17:12AM +0200, Gerhard Bertelsmann wrote:
> Kernel module for Allwinner A10/A20 CAN
>
> Signed-off-by: Gerhard Bertelsmann
> ---
>
> drivers/net/can/Kconfig| 10 +
> drivers/net/can/Makefile | 1 +
> drivers/net
The command buffer address is necessarily not naturally aligned.
The hardware drops the entire read on some platforms and fills the
address with 1's. This patch fixes the issue by splitting the read
into two 32 bit reads.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm_crb.c | 7 ---
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_sourcesink we only need to store in ep->driver_d
From: Oleg Nesterov
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit fecdf8be2d91e04b0a9a4f79ff06499a36f5d14f ]
pktgen_thread_worker() is obviously racy, kthread_stop() can come
between the kthread_should_stop() check and set_curren
From: James Smart
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 5116fbf136ea21b8678a85eee5c03508736ada9f upstream.
Didn't check for less-than-or-equal zero. Means we may later call
scsi_dma_unmap() even though we don't have valid mappings.
On 09/15/2015 02:03 AM, l...@kernel.org wrote:
From: Zefan Li
This is the start of the stable review cycle for the 3.4.109 release.
There are 146 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Respon
From: Shirish Pargaonkar
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 7f48558e6489d032b1584b0cc9ac4bb11072c034 upstream.
Send a smb session logoff request before removing smb session off of the list.
On a signed smb session, remvoing a ses
From: Dan Carpenter
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 468b732b6f76b138c0926eadf38ac88467dcd271 ]
"len" is a signed integer. We check that len is not negative, so it
goes from zero to INT_MAX. PAGE_SIZE is unsigned l
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_acm we only need to store in ep->driver_data poi
On 09/15, Konstantin Khlebnikov wrote:
>
> +SYSCALL_DEFINE3(getvpid, pid_t, pid, pid_t, source, pid_t, target)
> +{
> +#ifdef CONFIG_PID_NS
> + struct pid_namespace *current_ns = task_active_pid_ns(current);
> + struct pid_namespace *source_ns = current_ns, *target_ns = current_ns;
> +
Hi Felipe,
There is my next patches series containing few fixes and slightly
reworking USB gadget function API. It introduces ep->enabled flag which
indicates whether endpointis enabled or not, and encapsulates its checking
and setting into usb_ep_enable() and usb_ep_disable() functions. So now
th
Since ep->driver_data is not used for endpoint claiming, neither for
enabled/disabled state storing, we can reduce number of places where
we read or modify it's value, as now it has no particular meaning for
function or framework logic.
In case of f_hid we only need to store in ep->driver_data poi
From: Mark Rustad
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 7aa6ca4d39edf01f997b9e02cf6d2fdeb224f351 upstream.
Set the PCI_DEV_FLAGS_VPD_REF_F0 flag on all Intel Ethernet device
functions other than function 0, so that on multi-function
On 09/15/2015 06:50 AM, Sudip Mukherjee wrote:
On Tue, Sep 15, 2015 at 06:28:40AM -0700, Guenter Roeck wrote:
On 09/15/2015 01:21 AM, Sudip Mukherjee wrote:
On Mon, Sep 14, 2015 at 02:22:08PM -0700, Guenter Roeck wrote:
On Mon, Sep 14, 2015 at 05:19:27PM +0530, Sudip Mukherjee wrote:
I am no
From: Nikolay Aleksandrov
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 5ebc784625ea68a9570d1f70557e7932988cd1b4 ]
Since the mdb add/del code was introduced there have been 2 br_mdb_notify
calls when doing br_mdb_add() resulting
From: Florian Westphal
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 0470eb99b4721586ccac954faac3fa4472da0845 ]
Kirill A. Shutemov says:
This simple test-case trigers few locking asserts in kernel:
int main(int argc, char **arg
Vitaly Kuznetsov writes:
> Some host adapters (e.g. Hyper-V storvsc) are known for not respecting the
> SPC-2/3/4 requirement for 'INQUIRY data (see table ...) shall contain at
> least 36 bytes'. As a result we get tons on 'scsi 0:7:1:1: scsi scan:
> INQUIRY result too short (5), using 36' messag
From: David Milburn
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit c8afd0dcbd14e2352258f2e2d359b36d0edd459f upstream.
Dynamically allocate buf to prevent warnings:
drivers/block/mtip32xx/mtip32xx.c: In function ‘mtip_hw_read_device_status’:
The 'driver_data' field in ep0 is never set to pointer to cdev, so we
have to obtain it from another source as in this context ep->driver_data
contains invalid data.
Signed-off-by: Robert Baldyga
---
drivers/usb/gadget/function/f_ncm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: Andrey Vagin
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit c6825c0976fa7893692e0e43b09740b419b23c09 ]
Lets look at destroy_conntrack:
hlist_nulls_del_rcu(&ct->tuplehash[IP_CT_DIR_ORIGINAL].hnnode);
...
nf_conntrack_free(ct
This patch introduces usb_ep_autoconfig_release() function which allows
to release endpoint previously obtained from usb_ep_autoconfig() during
USB function bind.
Signed-off-by: Robert Baldyga
---
drivers/usb/gadget/epautoconf.c | 17 +
include/linux/usb/gadget.h | 2 ++
2
501 - 600 of 1097 matches
Mail list logo
