Hi,
it was brought to my attention that there are claims of data corruption
caused by VMware's SCSI implementation. After investigating, problem
seems to be in a way completion handler for WRITE_SAME handles EOPNOTSUPP
error, causing all-but-first WRITE_SAME request on the LVM device to be
silen
On 10/08/14 at 03:27pm, Vivek Goyal wrote:
> On Wed, Oct 08, 2014 at 08:09:59AM -0700, H. Peter Anvin wrote:
> > Sorry... this makes no sense.
> >
> > For x86-64, there is no direct connection between the physical and
> > virtual address spaces that the kernel runs in...
>
> I am sorry I did no
Attention!!!
Are you interested in any kind of loan and been turned down severally,
due to bad credit or unnecessary fees? If yes, search no further as We
Lend out instant cash to individual and companies at 2% interest rate.
Apply today and get approved; do fill the loan application form.
Full N
I received two mails about faile to apply patches to 3.16-stable tree:
FAILED: patch "[PATCH] virtio-rng: skip reading when we start to remove the
device" failed to apply to 3.16-stable tree
FAILED: patch "[PATCH] virtio-rng: fix stuck of hot-unplugging busy device"
failed to apply to 3.16-stabl
When we try to hot-remove a busy virtio-rng device from QEMU monitor,
the device can't be hot-removed. Because virtio-rng driver hangs at
wait_for_completion_killable().
This patch exits the waiting by completing have_data completion before
unregistering, resets data_avail to avoid the hwrng core
Before we really unregister the hwrng device, reading will get stuck if
the virtio device is reset. We should return error for reading when we
start to remove the device.
Signed-off-by: Amos Kong
Reviewed-by: Amit Shah
Cc: stable@vger.kernel.org
Signed-off-by: Rusty Russell
(cherry picked from
I've updated my contact details and removed obsolete comments.
Signed-off-by: Bernd Porr
---
drivers/staging/comedi/drivers/usbdux.c | 59 -
1 file changed, 28 insertions(+), 31 deletions(-)
diff --git a/drivers/staging/comedi/drivers/usbdux.c
b/drivers/staging
I've updated my contact details of the driver. I've also tested it
thoroughly and it works perfectly. I've changed the status to stable.
Signed-off-by: Bernd Porr
---
drivers/staging/comedi/drivers/usbduxsigma.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers
Updated the range of years, e-mail and added driver desription as
usually done in comedi.
Signed-off-by: Bernd Porr
---
drivers/staging/comedi/drivers/usbduxfast.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/drivers/usbduxfast.c
b/driv
On Thu, Oct 09, 2014 at 09:06:24PM +0200, Johan Hovold wrote:
> The platform device must be registered as wakeup capable before
> registering the class device, or the wakealarm attribute will not be
> created.
>
> Also make sure to unregister the wakeup source on probe errors.
>
> Fixes: 1d2e2b65
On Thu, Oct 09, 2014 at 09:06:23PM +0200, Johan Hovold wrote:
> Make sure not to reset the clock-source configuration when enabling the
> 32kHz clock mux.
>
> Until the clock source can be configured through device tree we must not
> overwrite settings made by the bootloader (e.g. clock-source sel
Hello,
I'm deeply sorry about the patch spam I set a while ago. I've
accidentally run git-send-email on a wrong directory...
Honza
--
Jan Kara
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe stable" i
The check whether quota format is set even though there are no
quota files with journalled quota is pointless and it actually
makes it impossible to turn off journalled quotas (as there's
no way to unset journalled quota format). Just remove the check.
CC: stable@vger.kernel.org
Signed-off-by: Jan
Tail of a page straddling inode size must be zeroed when being written
out due to POSIX requirement that modifications of mmaped page beyond
inode size must not be written to the file. ext4_bio_write_page() did
this only for blocks fully beyond inode size but didn't properly zero
blocks partially b
Hole punching code for files with indirect blocks wrongly computed
number of blocks which need to be cleared when traversing the indirect
block tree. That could result in punching more blocks than actually
requested and thus effectively cause a data loss. For example:
fallocate -n -p 1024 4096
Global quota files are accessed from different nodes. Thus we cannot
cache offset of quota structure in the quota file after we drop our
node reference count to it because after that moment quota structure may
be freed and reallocated elsewhere by a different node resulting in
corruption of quota f
The check whether quota format is set even though there are no
quota files with journalled quota is pointless and it actually
makes it impossible to turn off journalled quotas (as there's
no way to unset journalled quota format). Just remove the check.
CC: stable@vger.kernel.org
Signed-off-by: Jan
From: Derek Basehore
bdi_wakeup_thread_delayed() used the mod_delayed_work() function to
schedule work to writeback dirty inodes. The problem with this is that
it can delay work that is scheduled for immediate execution, such as the
work from sync_inodes_sb(). This can happen since mod_delayed_w
After 839a8e8660b67 "writeback: replace custom worker pool
implementation with unbound workqueue" when device is removed while we
are writing to it we crash in bdi_writeback_workfn() ->
set_worker_desc() because bdi->dev is NULL. This can happen because
even though bdi_unregister() cancels all pen
commit 5838d4442bd5971687b72221736222637e03140d upstream.
Commit 85816794240b ("fanotify: Fix use after free for permission
events") introduced a double free issue for permission events which are
pending in group's notification queue while group is being destroyed.
These events are freed from fano
Commit d127e9c ("ARM: tegra: make tegra_resume can work with current and later
chips") removed tegra_get_soc_id macro leaving used cpu register corrupted after
branching to v7_invalidate_l1() and as result causing execution of unintended
code on tegra20. Possibly it was expected that r6 would be So
On Oct10 04:40, Greg Kroah-Hartman wrote:
> The last 3.14.x release had a bunch of these patches already in them,
> with more to come in future releases, so yes, 3.14.x is going to benefit
> from it, and you didn't even notice :)
oh true; did not catch the last one.
> But 3.10 will probably not,
On Fri, Oct 10, 2014 at 09:32:45AM +0200, William Dauchy wrote:
> Hi stable release team,
>
> On Wed, Oct 1, 2014 at 10:57 AM, Jiri Slaby wrote:
> > This one is special. First, it is rounded (30). Second, most of the
> > patches are performance improvements. They are coming from SUSE
> > Enterpri
On 10/10/2014 07:48 PM, Krzysztof Kozlowski wrote:
> All interrupts coming from MUIC were ignored because interrupt source
> register was masked.
>
> The Maxim 77693 has a "interrupt source" - a separate register and interrupts
> which give information about PMIC block triggering the individual
>
On Fri, 10 Oct 2014, Krzysztof Kozlowski wrote:
> All interrupts coming from MUIC were ignored because interrupt source
> register was masked.
>
> The Maxim 77693 has a "interrupt source" - a separate register and interrupts
> which give information about PMIC block triggering the individual
> in
All interrupts coming from MUIC were ignored because interrupt source
register was masked.
The Maxim 77693 has a "interrupt source" - a separate register and interrupts
which give information about PMIC block triggering the individual
interrupt (charger, topsys, MUIC, flash LED).
By default bootl
On Fri, Oct 10, 2014 at 11:54:00AM +0200, Johan Hovold wrote:
> On Fri, Oct 10, 2014 at 11:52:08AM +0200, Frans Klaver wrote:
> > Add new IDs for the Xsens Awinda Station and Awinda Dongle.
> >
> > While at it, order the definitions by PID and add a logical separation
> > between devices using Xse
On pią, 2014-10-10 at 19:05 +0900, Chanwoo Choi wrote:
> On 10/10/2014 06:03 PM, Krzysztof Kozlowski wrote:
> > On pią, 2014-10-10 at 17:45 +0900, Chanwoo Choi wrote:
> >> On 10/10/2014 05:22 PM, Krzysztof Kozlowski wrote:
> >>> All interrupts coming from MUIC were ignored because interrupt source
On pią, 2014-10-10 at 10:48 +0100, Lee Jones wrote:
> On Fri, 10 Oct 2014, Krzysztof Kozlowski wrote:
>
> > On pią, 2014-10-10 at 09:58 +0100, Lee Jones wrote:
> > > On Fri, 10 Oct 2014, Krzysztof Kozlowski wrote:
> > >
> > > > All interrupts coming from MUIC were ignored because interrupt source
On 10/10/2014 06:03 PM, Krzysztof Kozlowski wrote:
> On pią, 2014-10-10 at 17:45 +0900, Chanwoo Choi wrote:
>> On 10/10/2014 05:22 PM, Krzysztof Kozlowski wrote:
>>> All interrupts coming from MUIC were ignored because interrupt source
>>> register was masked.
>>>
>>> The Maxim 77693 has a "interru
On Fri, Oct 10, 2014 at 11:52:08AM +0200, Frans Klaver wrote:
> Add new IDs for the Xsens Awinda Station and Awinda Dongle.
>
> While at it, order the definitions by PID and add a logical separation
> between devices using Xsens' VID and those using FTDI's VID.
>
> Cc:
> Signed-off-by: Frans Kla
Add new IDs for the Xsens Awinda Station and Awinda Dongle.
While at it, order the definitions by PID and add a logical separation
between devices using Xsens' VID and those using FTDI's VID.
Cc:
Signed-off-by: Frans Klaver
---
Third time's a charm.
drivers/usb/serial/ftdi_sio.c | 2 ++
d
On Fri, 10 Oct 2014, Krzysztof Kozlowski wrote:
> On pią, 2014-10-10 at 09:58 +0100, Lee Jones wrote:
> > On Fri, 10 Oct 2014, Krzysztof Kozlowski wrote:
> >
> > > All interrupts coming from MUIC were ignored because interrupt source
> > > register was masked.
> > >
> > > The Maxim 77693 has a "
On Fri, Oct 10, 2014 at 11:34:43AM +0200, Johan Hovold wrote:
> On Fri, Oct 10, 2014 at 11:32:27AM +0200, Frans Klaver wrote:
> > Add new IDs for the Xsens Awinda Station and Awinda Dongle.
> >
> > While at it, order the definitions by PID and add a logical separation
> > between devices using Xse
On Fri, Oct 10, 2014 at 11:32:27AM +0200, Frans Klaver wrote:
> Add new IDs for the Xsens Awinda Station and Awinda Dongle.
>
> While at it, order the definitions by PID and add a logical separation
> between devices using Xsens' VID and those using FTDI's VID.
>
> Cc:
> Signed-off-by: Frans Kla
Add new IDs for the Xsens Awinda Station and Awinda Dongle.
While at it, order the definitions by PID and add a logical separation
between devices using Xsens' VID and those using FTDI's VID.
Cc:
Signed-off-by: Frans Klaver
---
drivers/usb/serial/ftdi_sio.c | 2 ++
drivers/usb/serial/ftdi_
On Fri, Oct 10, 2014 at 11:20:14AM +0200, Johan Hovold wrote:
> On Fri, Oct 10, 2014 at 11:12:09AM +0200, Frans Klaver wrote:
> > I'll move the new entries up. How about I throw in a separate patch that
> > cleans up stuff around the PID definitions? There's some alignment off
> > as well. That doe
On Fri, Oct 10, 2014 at 11:12:09AM +0200, Frans Klaver wrote:
> On Fri, Oct 10, 2014 at 11:01:17AM +0200, Johan Hovold wrote:
> > On Fri, Oct 10, 2014 at 10:44:54AM +0200, Frans Klaver wrote:
> > > diff --git a/drivers/usb/serial/ftdi_sio_ids.h
> > > b/drivers/usb/serial/ftdi_sio_ids.h
> > > inde
On Fri, Oct 10, 2014 at 11:01:17AM +0200, Johan Hovold wrote:
> On Fri, Oct 10, 2014 at 10:44:54AM +0200, Frans Klaver wrote:
> > Add new IDs for the Xsens Awinda Station and Awinda Dongle.
> >
> > Cc:
> > Signed-off-by: Frans Klaver
> > ---
> > drivers/usb/serial/ftdi_sio.c | 2 ++
> > dri
On Fri, Oct 10, 2014 at 10:44:54AM +0200, Frans Klaver wrote:
> Add new IDs for the Xsens Awinda Station and Awinda Dongle.
>
> Cc:
> Signed-off-by: Frans Klaver
> ---
> drivers/usb/serial/ftdi_sio.c | 2 ++
> drivers/usb/serial/ftdi_sio_ids.h | 2 ++
> 2 files changed, 4 insertions(+)
>
>
On pią, 2014-10-10 at 17:45 +0900, Chanwoo Choi wrote:
> On 10/10/2014 05:22 PM, Krzysztof Kozlowski wrote:
> > All interrupts coming from MUIC were ignored because interrupt source
> > register was masked.
> >
> > The Maxim 77693 has a "interrupt source" - a separate register and
> > interrupts
On pią, 2014-10-10 at 09:58 +0100, Lee Jones wrote:
> On Fri, 10 Oct 2014, Krzysztof Kozlowski wrote:
>
> > All interrupts coming from MUIC were ignored because interrupt source
> > register was masked.
> >
> > The Maxim 77693 has a "interrupt source" - a separate register and
> > interrupts
> >
On Fri, 10 Oct 2014, Krzysztof Kozlowski wrote:
> All interrupts coming from MUIC were ignored because interrupt source
> register was masked.
>
> The Maxim 77693 has a "interrupt source" - a separate register and interrupts
> which give information about PMIC block triggering the individual
> in
On Fri, 10 Oct 2014, Krzysztof Kozlowski wrote:
> Interrupts coming from Maxim77693 MUIC block (MicroUSB Interface
> Controller) were not handled at all because wrong regmap was used for
> MUIC's regmap_irq_chip.
>
> The MUIC component of Maxim 77693 uses different I2C address thus second
> regma
On 10/10/2014 05:22 PM, Krzysztof Kozlowski wrote:
> Interrupts coming from Maxim77693 MUIC block (MicroUSB Interface
> Controller) were not handled at all because wrong regmap was used for
> MUIC's regmap_irq_chip.
>
> The MUIC component of Maxim 77693 uses different I2C address thus second
> reg
On 10/10/2014 05:22 PM, Krzysztof Kozlowski wrote:
> All interrupts coming from MUIC were ignored because interrupt source
> register was masked.
>
> The Maxim 77693 has a "interrupt source" - a separate register and interrupts
> which give information about PMIC block triggering the individual
>
Add new IDs for the Xsens Awinda Station and Awinda Dongle.
Cc:
Signed-off-by: Frans Klaver
---
drivers/usb/serial/ftdi_sio.c | 2 ++
drivers/usb/serial/ftdi_sio_ids.h | 2 ++
2 files changed, 4 insertions(+)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
index
All interrupts coming from MUIC were ignored because interrupt source
register was masked.
The Maxim 77693 has a "interrupt source" - a separate register and interrupts
which give information about PMIC block triggering the individual
interrupt (charger, topsys, MUIC, flash LED).
By default bootl
Interrupts coming from Maxim77693 MUIC block (MicroUSB Interface
Controller) were not handled at all because wrong regmap was used for
MUIC's regmap_irq_chip.
The MUIC component of Maxim 77693 uses different I2C address thus second
regmap is created and used by max77693 extcon driver. The register
On 10/01/2014, 06:23 PM, Guenter Roeck wrote:> Build results:
> total: 135 pass: 135 fail: 0
> Qemu test results:
> total: 23 pass: 23 fail: 0
On 10/01/2014, 06:24 PM, Shuah Khan wrote:
> Compiled and booted on my test system. No dmesg regressions.
On 10/03/2014, 01:40 PM, Satoru Take
Hi stable release team,
On Wed, Oct 1, 2014 at 10:57 AM, Jiri Slaby wrote:
> This one is special. First, it is rounded (30). Second, most of the
> patches are performance improvements. They are coming from SUSE
> Enterprise Linux and all are backed by proper testing and performance
> measurements
51 matches
Mail list logo
