From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Tue Sep  2 11:15:47 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Tue, 02 Sep 2014 11:15:47 -0700
Subject: [DragonFlyBSD - Bug #2722] (New) bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2722.20140902181547.d4d3dc347cabcdc6@leaf.dragonflybsd.org>

Issue #2722 has been reported by guy.

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 06:34:40 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 06:34:40 -0700
Subject: [DragonFlyBSD - Bug #2722] bpf_filter's memory array is signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12221.20140903133440.21dee10f4f196eaf@leaf.dragonflybsd.org>

Issue #2722 has been updated by sepherosa.


Fixed, thank!

On Wed, Sep 3, 2014 at 2:15 AM,  <bugtracker-admin at leaf.dragonflybsd.org> wrote:
> Issue #2722 has been reported by guy.
>
> ----------------------------------------
> Bug #2722: bpf_filter's memory array is signed
> http://bugs.dragonflybsd.org/issues/2722
>
> * Author: guy
> * Status: New
> * Priority: Normal
> * Assignee:
> * Category: Networking
> * Target version:
> ----------------------------------------
> The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.
>
> This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.
>
> I've attached a fix.
>
> ---Files--------------------------------
> patch (376 Bytes)
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



-- 
Tomorrow Will Never Die

----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12221

* Author: guy
* Status: New
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:43:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:43:09 -0700
Subject: [DragonFlyBSD - Bug #2722] (Closed) bpf_filter's memory array is
 signed
References: <redmine.issue-2722.20140902181547@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12224.20140903194308.5ee931e5c94bbf3b@leaf.dragonflybsd.org>

Issue #2722 has been updated by swildner.

Status changed from New to Closed

It was pushed (05b1e6eac15534d3ea7e33de2cbccc3d08a286d4)


----------------------------------------
Bug #2722: bpf_filter's memory array is signed
http://bugs.dragonflybsd.org/issues/2722#change-12224

* Author: guy
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Networking
* Target version: 
----------------------------------------
The mem[] array in bpf_filter(), for scratch memory in BPF programs, is an array of signed 32-bit integers.  However, 1) all references to it either assign unsigned 32-bit values to elements in the array or assign the value of elements in the array to unsigned 32-bit values, and in some other BSDs it's unsigned.

This shouldn't affect the behavior of the code (at least on 2's-complement machines, but I don't foresee a Univac 2200-series port of any of the BSDs any time soon :-)), but it makes it a bit cleaner and more like some other BSDs (the others will get their own patches) and the current top-of-trunk libpcap.

I've attached a fix.

---Files--------------------------------
patch (376 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Wed Sep  3 12:46:09 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Wed, 03 Sep 2014 12:46:09 -0700
Subject: [DragonFlyBSD - Bug #2698] (Closed) http://www.dragonflybsd.de -
 outdated website
References: <redmine.issue-2698.20140708182000@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12225.20140903194609.68aa37b396a5f466@leaf.dragonflybsd.org>

Issue #2698 has been updated by swildner.

Status changed from New to Closed

As far as I remember it was tried already in the past to reach the admin of that site.


----------------------------------------
Bug #2698: http://www.dragonflybsd.de - outdated website
http://bugs.dragonflybsd.org/issues/2698#change-12225

* Author: patpi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: Other
* Target version: 
----------------------------------------
Hi,

I just typed 'dragonflybsd' on a newly installed Firefox with DuckDuckGo search engine set as default. The result of pre-loading search terms in Firefox URL-bar was that bar showed 'http://www.dragonflybsd.de/' as a suggested url to go. When you visit this page you see some outdated website. Maybe you are able to contact administrator of dragonflybsd.de  and either delete this website or update it?




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Thu Sep 11 05:22:52 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Thu, 11 Sep 2014 05:22:52 -0700
Subject: [DragonFlyBSD - Bug #2683] (Resolved) HAMMER data corruption with
 rebranded LSI RAID adapters
References: <redmine.issue-2683.20140611084415@leaf.dragonflybsd.org>
Message-ID: <redmine.journal-12226.20140911122252.1fc586b051760e8f@leaf.dragonflybsd.org>

Issue #2683 has been updated by ftigeot.

Status changed from New to Resolved

The aforementioned database server has now been running in production for months.
Closing.

----------------------------------------
Bug #2683: HAMMER data corruption with rebranded LSI RAID adapters
http://bugs.dragonflybsd.org/issues/2683#change-12226

* Author: ftigeot
* Status: Resolved
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Two different machines running DragonFly 3.6.x had the kernel report HAMMER CRC32 data corruption and then panic.

After a reboot, the kernel couldn't repair and mount the HAMMER volumes where these CRC32 errors occurred due to massive amounts of data corruption.

The systems had these elements in common:
- DragonFly 3.6.x
- Dell rack servers
- HAMMER filesystem on a hardware RAID volume managed by the mfi(4) LSI MegaRAID SAS driver

The two different machines were apparently using the same kind of rebranded LSI RAID adapter.

PCI id from one of the cards:
mfi0 at pci0:3:0:0:        class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account


From bugtracker-admin at leaf.dragonflybsd.org  Mon Sep 22 05:00:13 2014
From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org)
Date: Mon, 22 Sep 2014 05:00:13 -0700
Subject: [DragonFlyBSD - Bug #2724] (New) PANIC message when installing
 DragonFly 3.8.2
References: <redmine.issue-2724.20140922120013@leaf.dragonflybsd.org>
Message-ID: <redmine.issue-2724.20140922120013.67af41c84cde077e@leaf.dragonflybsd.org>

Issue #2724 has been reported by eduardo.

----------------------------------------
Bug #2724: PANIC message when installing DragonFly 3.8.2
http://bugs.dragonflybsd.org/issues/2724

* Author: eduardo
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Hello,
       I'm trying to install DragonFly from USB (dfly-x86_64-3.8.2_REL.img) but I'm getting some PANIC messages when shutting down just before the installation ask for testing the system. 
  I attach a picture of the screen and I leave the "db>" prompt waiting for your response. 
  Many thanks in advance, 

Ps: I tried in two machines (Laptop and Desktop) and I got the same message. 

---Files--------------------------------
2014-09-18-17-23-04_photo.jpg (1.4 MB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account