binary:affs-modules-4.8.0-2-4kc-malta-di is NEW.
binary:affs-modules-4.8.0-2-5kc-malta-di is NEW.
binary:affs-modules-4.8.0-2-loongson-3-di is NEW.
binary:affs-modules-4.8.0-2-octeon-di is NEW.
binary:ata-modules-4.8.0-2-4kc-malta-di is NEW.
binary:ata-modules-4.8.0-2-5kc-malta-di is NEW.
binary:at
linux_4.8.11-1_multi.changes uploaded successfully to localhost
along with the files:
linux_4.8.11-1.dsc
linux_4.8.11.orig.tar.xz
linux_4.8.11-1.debian.tar.xz
linux-doc-4.8_4.8.11-1_all.deb
linux-manual-4.8_4.8.11-1_all.deb
linux-source-4.8_4.8.11-1_all.deb
linux-support-4.8.0-2_4.8.1
Thanks for this; I've applied it to the master branch for Debian.
After comparing all the symbols potentially exported from assembly with
those declared in asm-prototypes.h, I found that cmpxchg8b_emu is
missing. This is only defined when building for 486 so it doesn't
affect Debian, but you may
Processing commands for cont...@bugs.debian.org:
> tags 846492 + upstream
Bug #846492 [src:linux] linux-image-4.8.0-1-686-pae: frequently crash during
boot
Added tag(s) upstream.
> forwarded 846492 https://bugs.freedesktop.org/show_bug.cgi?id=93782
Bug #846492 [src:linux] linux-image-4.8.0-1-686-
Hi
We intend to upload linux version 4.8.11-1 to unstable over this
weekend.
The upload incorporates the upstream stable updates 4.8.8, 4.8.9, 4.8.10
and 4.8.11 with various bugfixes and fixed vulnerabilities
(CVE-2015-1350 CVE-2016-6213 CVE-2016-8645 CVE-2016-8650 CVE-2016-9083
CVE-2016-9084 CVE
Your message dated Thu, 01 Dec 2016 19:46:58 +
with message-id <1480621618.16599.103.ca...@decadent.org.uk>
and subject line Re: Bug#846513: linux-libc-dev possibly needs dependency on
corresponding linux-image
has caused the Debian Bug report #846513,
regarding linux-libc-dev possibly needs d
On Thu, Dec 01, 2016 at 05:06:11PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Dec 01, 2016 at 10:40:59AM -0500, Don Zickus wrote:
> > Unfortunately, there are various drivers that will never go upstream
> >
> > - paid storage drivers that provide bells and whistles on top of inbox
> > driver
>
On Thu, Dec 1, 2016 at 5:58 AM, Arnd Bergmann wrote:
>
> WARNING: EXPORT symbol "mcount" [arch/x86/entry/built-in.ko] version
> generation failed, symbol will not be versioned.
> WARNING: EXPORT symbol "mcount" [arch/x86/built-in.ko] version generation
> failed, symbol will not be versioned.
> W
On 2016-12-01 14:58, Arnd Bergmann wrote:
> On Tuesday, November 29, 2016 9:14:46 AM CET Linus Torvalds wrote:
>> On Tue, Nov 29, 2016 at 9:10 AM, Linus Torvalds
>> wrote:
>>>
>>> So quite frankly, I don't want to make our kernel sources worse due to
>>> broken shit tools getting something wrong t
On 2016-12-01 05:13, Don Zickus wrote:
> Sorry for chiming in late, but yes RHEL is a big user of MODVERSIONS for our
> kabi protection work. Despite our best intentions we still have lots of
> partners and customers that provide value-add out-of-tree drivers to their
> customers. These module bu
On Thu, Dec 01, 2016 at 10:40:59AM -0500, Don Zickus wrote:
> Unfortunately, there are various drivers that will never go upstream
>
> - paid storage drivers that provide bells and whistles on top of inbox
> driver
That's because the developer doesn't want them upstream, that's their
fault, not
On 2016-12-01 04:39, Nicholas Piggin wrote:
> On Thu, 01 Dec 2016 02:35:54 +
> Ben Hutchings wrote:
>> As I understand it, genksyms incorporates the definitions of a
>> function's parameter and return types - not just their names - and all
>> the types they refer to, recursively. So a structu
On Thu, Dec 01, 2016 at 10:20:39AM -0500, Don Zickus wrote:
>
> - provide the memory allocation (instead of having the driver staticly
> allocate)
> - provide functions to retrieve various internal data (instead of having the
> driver do direct referencing to deep internal elements)
> - cut do
On Thu, Dec 01, 2016 at 07:26:09AM -0800, Christoph Hellwig wrote:
> On Thu, Dec 01, 2016 at 10:20:39AM -0500, Don Zickus wrote:
> >
> > - provide the memory allocation (instead of having the driver staticly
> > allocate)
> > - provide functions to retrieve various internal data (instead of havi
Nicholas Piggin a écrit:
[...]
> On Thu, 1 Dec 2016 11:48:09 +0100
> Stanislav Kozina wrote:
>
>> On 12/01/2016 05:13 AM, Don Zickus wrote:
>>
>> ...
>>
>> > I think GregKH pointed to one such tool, libabigail? We are working on
>> > others too.
>>
>> I should mention one of the others he
On Thu, Dec 01, 2016 at 03:32:15PM +1100, Nicholas Piggin wrote:
> > Anyway, MODVERSIONS is our way of protecting our kabi for the last 10 years.
> > It isn't perfect and we have fixed the genksyms tool over the years, but so
> > far it mostly works fine.
>
> Okay. It would be good to get all the
Thursday, December 1, 2016, 2:59:36 PM, you wrote:
> On 01.12.2016 14:26, Wei Liu wrote:
>> This is still the same kernel log that was sent some time ago.
>> So, if you have built Xen with debug=y, could you try to set Xen log
>> level to the highest and capture "xl dmesg" when guest crashes?
>
On 01.12.2016 14:26, Wei Liu wrote:
This is still the same kernel log that was sent some time ago.
So, if you have built Xen with debug=y, could you try to set Xen log
level to the highest and capture "xl dmesg" when guest crashes?
It's not the guest that crashes, it's dom0. So when the host c
Package: src:linux
Version: 4.8.7-1
Severity: important
Dear Maintainer,
after upgrading our Acer Extensa 5220 to linux version 4.8.5-1 and 4.8.7-1 it
frequently crash during boot (if it does not crash is completly usable).
This is the relevant kernel log:
Dec 1 12:52:59 computer kernel: [ 126
On Tuesday, November 29, 2016 9:14:46 AM CET Linus Torvalds wrote:
> On Tue, Nov 29, 2016 at 9:10 AM, Linus Torvalds
> wrote:
> >
> > So quite frankly, I don't want to make our kernel sources worse due to
> > broken shit tools getting something wrong that we shouldn't even care
> > about.
>
> And
On Thu, Dec 01, 2016 at 02:59:36PM +0100, Ingo Jürgensmann wrote:
> On 01.12.2016 14:26, Wei Liu wrote:
>
> >This is still the same kernel log that was sent some time ago.
> >So, if you have built Xen with debug=y, could you try to set Xen log
> >level to the highest and capture "xl dmesg" when gu
Package: linux-signed
Version: 3.2
Severity: important
Hi,
Your packages includes broken Built-Using fields, e.g.:
Package: linux-image-4.8.0-1-amd64
Source: linux-signed (3.2)
Built-Using: linux (4.8.7-1)
That should have been: linux (= 4.8.7-1)
See Debian Policy 7.8:
A Built-Using field
On Tue, Nov 29, 2016 at 09:20:55PM +0100, Ingo Jürgensmann wrote:
> Am 29.11.2016 um 10:08 schrieb Wei Liu :
> >> http://paste.debian.net/895464/
> > Entry not found -- maybe it expired... Sorry.
>
> Here it is:
>
This is still the same kernel log that was sent some time ago.
So, if you have b
On Thu, 1 Dec 2016 12:33:02 +0100
Stanislav Kozina wrote:
> On 12/01/2016 12:09 PM, Nicholas Piggin wrote:
> > On Thu, 1 Dec 2016 11:48:09 +0100
> > Stanislav Kozina wrote:
> >
> >> On 12/01/2016 05:13 AM, Don Zickus wrote:
> >>
> >> ...
> >>
> >>> I think GregKH pointed to one such tool, li
On 12/01/2016 12:09 PM, Nicholas Piggin wrote:
On Thu, 1 Dec 2016 11:48:09 +0100
Stanislav Kozina wrote:
On 12/01/2016 05:13 AM, Don Zickus wrote:
...
I think GregKH pointed to one such tool, libabigail? We are working on
others too.
I should mention one of the others here:
https://gith
On Thu, 1 Dec 2016 11:48:09 +0100
Stanislav Kozina wrote:
> On 12/01/2016 05:13 AM, Don Zickus wrote:
>
> ...
>
> > I think GregKH pointed to one such tool, libabigail? We are working on
> > others too.
>
> I should mention one of the others here:
> https://github.com/skozina/kabi-dw
>
> I
On 12/01/2016 05:13 AM, Don Zickus wrote:
...
I think GregKH pointed to one such tool, libabigail? We are working on
others too.
I should mention one of the others here:
https://github.com/skozina/kabi-dw
It's quite comparable to libabigail in the way it works, the main
differences are:
27 matches
Mail list logo
