Package: isc-dhcp-client
Version: 4.3.1-6+deb8u2
Severity: serious
File: /sbin/dhclient
Tags: security
https://samy.pl/poisontap/
This is a variation on an ancient "gem" by a DSL Modem vendor
where the router pretends to be the entire internet by spoofing
arp so that it captures all traffic.
The
Package: src:linux
Version: 5.10.13-1~bpo10+1
Severity: critical
Justification: causes serious data loss
Dear Maintainer,
Large USB drives (example - Seagate 4TB Backup) which work perfectly fine with
4.19 are identified as incorrect size. In the case of the 4TB sized USB it's
identified as a 1
On 20/02/2021 10:33, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the src:linux package:
#940821: linux-image-5.2.0-2-amd64: file cache corruption with nfs4
It has been closed by Bastian Blank .
Their explanation is attac
On 20/02/2021 20:04, Salvatore Bonaccorso wrote:
Hi,
On Mon, Jul 08, 2019 at 07:19:54PM +0100, Anton Ivanov wrote:
Hi list,
NFS caching appears broken in 4.19.37.
The more cores/threads the easier to reproduce. Tested with identical
results on Ryzen 1600 and 1600X.
1. Mount an openwrt build
On 23/02/2021 17:26, Ritesh Raj Sarraf wrote:
Added the debian bug report in CC.
On Tue, 2021-02-23 at 17:19 +, Anton Ivanov wrote:
The current Debian user-mode-linux package in unstable is based on
the 5.10.5 stable source which includes the mentioned patch, but is
still causing an error
On 23/02/2021 17:26, Ritesh Raj Sarraf wrote:
Added the debian bug report in CC.
On Tue, 2021-02-23 at 17:19 +, Anton Ivanov wrote:
The current Debian user-mode-linux package in unstable is based on
the 5.10.5 stable source which includes the mentioned patch, but is
still causing an
On 02/03/2021 09:09, Ritesh Raj Sarraf wrote:
On Wed, 2021-02-24 at 11:44 +, Anton Ivanov wrote:
In all cases it boots cleanly and there are no segfaults.
So, frankly, no idea what is causing it to crash - I have run most
combinations of 5.10 on a 5.10, all work fine here.
Is there
On 02/03/2021 14:23, Ritesh Raj Sarraf wrote:
On Tue, 2021-03-02 at 11:34 +, Anton Ivanov wrote:
If gdb gives you the exact lines, that may be helpful.
It doesn't. But it does show drawbacks in my packaging. The debug
symbols packaged are not read/honored by gdb at all.
```
Re
On 02/03/2021 17:27, Ritesh Raj Sarraf wrote:
On Tue, 2021-03-02 at 17:05 +, Anton Ivanov wrote:
So the best I can extract for you is to compile the kernel with as
much
information as possible.
Can you try using one of the older kernels so we can verify if this
is indeed a 5.10 thing
On 03/03/2021 10:45, Ritesh Raj Sarraf wrote:
HI Anton,
On Wed, 2021-03-03 at 09:30 +, Anton Ivanov wrote:
OTOH, I have one more user (other than you) who's not been able to
reproduce the issue.
I will do a dissect the moment I figure out how to reproduce it.
I
will try to do some
On 03/03/2021 22:40, Johannes Berg wrote:
I think the problem is here:
#24 0x6080f234 in ipc_init_ids (ids=0x60c60de8 )
at ipc/util.c:119
#25 0x60813c6d in sem_init_ns (ns=0x60d895bb ) at
ipc/sem.c:254
#26 0x60015b5d in sem_init () at ipc/sem.c:268
#27 0x7f89906d92f7
On 04/03/2021 05:38, Hajime Tazaki wrote:
On Thu, 04 Mar 2021 07:40:00 +0900,
Johannes Berg wrote:
I think the problem is here:
#24 0x6080f234 in ipc_init_ids (ids=0x60c60de8 )
at ipc/util.c:119
#25 0x60813c6d in sem_init_ns (ns=0x60d895bb ) at
ipc/sem.c:254
#26 0x600
On 04/03/2021 08:05, Benjamin Berg wrote:
On Thu, 2021-03-04 at 08:47 +0100, Johannes Berg wrote:
On Thu, 2021-03-04 at 14:38 +0900, Hajime Tazaki wrote:
Now, I don't know how to fix it (short of changing your nsswitch
configuration) - maybe we could somehow rename sem_init()? Or maybe
we
ca
On 04/03/2021 18:41, Anton Ivanov wrote:
On 04/03/2021 08:05, Benjamin Berg wrote:
On Thu, 2021-03-04 at 08:47 +0100, Johannes Berg wrote:
On Thu, 2021-03-04 at 14:38 +0900, Hajime Tazaki wrote:
Now, I don't know how to fix it (short of changing your nsswitch
configuration) - may
On 04/03/2021 07:47, Johannes Berg wrote:
On Thu, 2021-03-04 at 14:38 +0900, Hajime Tazaki wrote:
Now, I don't know how to fix it (short of changing your nsswitch
configuration) - maybe we could somehow rename sem_init()? Or maybe we
can somehow give the kernel binary a lower symbol resoluti
On 05/03/2021 18:32, Johannes Berg wrote:
On 5 March 2021 18:39:42 CET, Anton Ivanov
wrote:
On 04/03/2021 07:47, Johannes Berg wrote:
On Thu, 2021-03-04 at 14:38 +0900, Hajime Tazaki wrote:
Now, I don't know how to fix it (short of changing your nsswitch
configuration) - may
SION {
+ {
+local: *;
+ };
+}
+
SECTIONS
{
/* This must contain the right address - not quite the default ELF one.*/
Acked-By: Anton Ivanov
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
Package: amanda-server
Version: 1:3.3.9-5
Severity: grave
Justification: renders package unusable
Dear Maintainer,
If one or more backup host is unreachable, the backup of all hosts fails.
Example - backing up two hosts - smaug and TerriblTerror:
If the latter is unreachable
TerribleTerror1
tly,
>to sid and backports. If you are dead on water I
>can provide my working in progress packages for stretch on amd64.
>
>Kind regards
>Jose M Calhariz
>
>On 09/10/17 06:55, Anton Ivanov wrote:
>> Package: amanda-server
>> Version: 1:3.3.9-5
>> Severit
That is not an advice.
If nscd is a required dependency, NIS should bring it in.
Presently it is not.
Still broken
A.
On 18/04/2019 14:43, Elimar Riesebieter wrote:
* Elimar Riesebieter [2019-04-03 11:06 +0200]:
* Anton Ivanov [2019-04-03 09:43 +0100]:
Package: nis
Version: 3.17.1-3
Please reopen.
Advice is no replacement for a Depends in the package control file.
As shipped the package is still broken and at the reported severity -
breaking most of the system
A.
On 18/04/2019 14:48, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug
Package: systemd
Version: 247.3-6
Severity: serious
Justification: Policy 10.7
Dear Maintainer,
/usr/lib/tmpfiles.d/x11.conf should be a configuration file. Entries in it must
be disabled in order to run containers with accelerated X11 and DRI access.
As it is under lib, changes to it are over
On 12/09/2019 15:42, Anton Ivanov wrote:
On 12/09/2019 13:14, Ritesh Raj Sarraf wrote:
Hi,
I am not sure if this has been reported upstream but with libpcap 1.9,
user mode linux fails to build. The build failure happens with both,
5.2 and 4.19 LTS kernels.
A much detailed report is
Package: src:linux
Version: 5.2.9-2
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
NFSv4 caching is completely broken on SMP.
How to reproduce:
Option 1. clone openwrt, run while make clean && make -j `nproc` ; do true ;
done
It will break depending on number of
s possible to turn this facility
on or off using a command line option.
A simplistic wrapper for generating the BPF firmware for the raw
socket driver out of a tcpdump/libpcap filter expression can be
found at: https://github.com/kot-begemot-uk/uml_vector_utilities/
Signed-off-by: Anton Ivanov
--
On 01/10/2019 08:50, Johannes Berg wrote:
On Mon, 2019-09-30 at 14:19 +0100, Anton Ivanov wrote:
All vector drivers now allow a BPF program to be loaded and
associated with the RX socket in the host kernel.
1. The program can be loaded as an extra kernel command line
option to any of the
Hi all,
A patch to fix the build for these follows.
I will stick to my original suggestion - pcap should be obsoleted in favour of
vector raw + BPF firmware load. The latter will work on interfaces where gso/gro
is enabled. The original pcap will fail on that due to the 1500 bytes size limit
in t
Signed-off-by: Anton Ivanov
---
arch/um/drivers/Makefile | 8
scripts/link-vmlinux.sh | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/um/drivers/Makefile b/arch/um/drivers/Makefile
index 693319839f69..34355057ec85 100644
--- a/arch/um/drivers/Makefile
+++ b
On 16/10/2019 08:53, Anton Ivanov wrote:
Signed-off-by: Anton Ivanov
---
arch/um/drivers/Makefile | 8
scripts/link-vmlinux.sh | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/um/drivers/Makefile b/arch/um/drivers/Makefile
index 693319839f69..34355057ec85
libraries on the userspace side.
Signed-off-by: Anton Ivanov
---
arch/um/scripts/extra-libs.sh | 10 ++
scripts/link-vmlinux.sh | 4 +++-
2 files changed, 13 insertions(+), 1 deletion(-)
create mode 100644 arch/um/scripts/extra-libs.sh
diff --git a/arch/um/scripts/extra-libs.sh b/arch
Package: nis
Version: 3.17.1-3+b1
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
Startup scripts are completely broken. Something in the systemd
conversion/autogeneration.
The ypbind binary is never started, the script goes into "backgrounded" and
fails. From ther
Package: rpcbind
Version: 1.2.5-0.3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After an upgrade to buster rpcbind no longer receives any broadcast queries.
Unicast works.
This is verified via strace - it has occasional netlink messages, but any of
the broadcast
tr
That's not it.
Same story with 1.2.5-7 from unstable.
This is after NIS restart on the client on the NIS server:
root@jain:# tcpdump -nvvv -i enp7s0f1.502 udp and port 111
tcpdump: listening on enp7s0f1.502, link-type EN10MB (Ethernet), capture
size 262144 bytes
192.168.20.41.36268 > 19
I missed the actual receive line in the 1.2.5-7 apologies.
It alone DOES Not fix it though.
There is breakage in libwrap to accompany it.
Once the fix in 1.2.5-7 is in, rpcbind starts receiving (according to
strace) messages which is followed by interrogating addresses and
interfaces by netli
On 12/09/2019 13:14, Ritesh Raj Sarraf wrote:
Hi,
I am not sure if this has been reported upstream but with libpcap 1.9,
user mode linux fails to build. The build failure happens with both,
5.2 and 4.19 LTS kernels.
A much detailed report is available at:
https://bugs.debian.org/cgi-bin/bugr
Package: fam
Version: 2.7.0-6sarge1
Severity: serious
fam segfaults when running on a heavily loaded server. The machine in
question is an imap server running courier (with fam support) and an NFS
server as well (circa 100 users). When started as /usr/sbin/famd -T 0 it will
exit after a
few minu
I tried to run it under gdb without success. It gets a signal 33 after a
while which I think is actually a GDB artefact.
Any ideas on how to debug this will be appreciated.
--
Understanding is a three-edged sword:
your side, their side, and the truth. --Kosh Naranek
A. R. Ivanov
E-m
Thomas Girard wrote:
>Selon Anton Ivanov <[EMAIL PROTECTED]>:
>
>
>
>>I tried to run it under gdb without success. It gets a signal 33 after a
>>while which I think is actually a GDB artefact.
>>
>>Any ideas on how to debug this will be appreciated.
&g
Thomas Girard wrote:
>Selon Anton Ivanov <[EMAIL PROTECTED]>:
>
>
>
>>famd: NetConnection.c++:252: void NetConnection::flush(): Assertion `ret
>>== omsgList->len' failed.
>>
>>Program received signal SIGABRT, Aborted.
>>0xb7def83b in r
Package: libc6
Version: 2.3.2.ds1-21
Severity: critical
After the last update C3 Version 1
with a kernel 2.6 image will fail on boot with:
Inconsistency detected by ld.so: do_rel.h: 109 elf_dynamic_do_rel: Assertion
'(map->l_info[(34+0+(0x6ff - (0x6ff0)))] != ((void *0))' failed!
Tes
Daniel Jacobowitz wrote:
On Thu, May 12, 2005 at 11:39:23AM +, Anton Ivanov wrote:
Package: libc6
Version: 2.3.2.ds1-21
Severity: critical
After the last update C3 Version 1
with a kernel 2.6 image will fail on boot with:
Inconsistency detected by ld.so: do_rel.h: 109 elf_dynamic_do_rel
Package: autofs
Version: 4.1.4+debian-2.1
Followup-For: Bug #520095
I had the same problem on NFS root with Sarge and it still exists in Lenny.
Prior to Sarge the autofs init script was checking if the mountpoint dirs
exist and if not - creating them. Without this it is broken on NFS root
syst
On Sun, 2009-08-02 at 01:40 +0200, Jan Christoph Nordholz wrote:
> Hi Michael,
>
> > No idea. If I were knew, I'd attach a patch for this issue.
> > The code is quite.. funny and fragile, I tried to understand
> > it right before submitting a bugreport but that wasn't quite
> > successful.
> >
>
Package: quagga
Version: 0.98.3-7.2
Severity: serious
This is observed only on one of several of our firewall systems (not the
most loaded and most complex ones). They have 1000+ iptable rules
generated by scripts and after reloading them ripd goes south. The
process is still running but it does n
On 10/11/11 08:49, Jonathan Nieder wrote:
Anton Ivanov wrote:
I can try to patch it to build some time next week. However, looking at the
supported kernels file in the package it may be better to go straight for
1.0.24 which is current alsa stable.
Any news on that? (No problem if
On 10/11/11 09:32, Anton Ivanov wrote:
On 10/11/11 08:49, Jonathan Nieder wrote:
Anton Ivanov wrote:
I can try to patch it to build some time next week. However, looking
at the
supported kernels file in the package it may be better to go
straight for
1.0.24 which is current alsa stable
Package: warzone2100
Version: 3.1.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The new version is unplayable.
1. Units produced during a remote mission instead of being delivered to
the factory delivery area of the factory producing them are locked in a
rock so
Package: alsa-driver
Severity: serious
Justification: fails to build from source (but built successfully in the past)
I am still getting from time to time (not always) sound glitches similar
to the ones reported in: Bug#610859 so I decided to try building more
recent alsa from source. However it
Some digging points to this:
http://permalink.gmane.org/gmane.linux.kernel.commits.head/226657
as a likely culprit.
Brgds,
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 04/14/11 18:27, Elimar Riesebieter wrote:
* Anton Ivanov [110413 17:57 +0100]:
Package: alsa-driver
Which version?
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Elimar
Standard squeeze one.
1.0.23+dfsg-2
This
1c0bfeca27eac958fde215594b4ee3fa Mon Sep 17 00:00:00 2001
From: Anton Ivanov
Date: Sat, 8 Mar 2014 06:49:27 +
Subject: [PATCH 2/3] BUG: Memory corruption on startup
The reverse case of this race (you must msync before read) is
well known. This is the not so common one.
It can be trigg
On 09/03/14 21:35, Mattia Dongili wrote:
> On Sat, Mar 08, 2014 at 07:04:56AM +0000, Anton Ivanov wrote:
>> Package: user-mode-linux
>> Version: 3.2-2um-1+deb7u2+b1
>> Severity: grave
>> Tags: patch
>> Justification: causes non-serious data loss
>>
>>
On 09/03/14 21:35, Mattia Dongili wrote:
On Sat, Mar 08, 2014 at 07:04:56AM +, Anton Ivanov wrote:
Package: user-mode-linux
Version: 3.2-2um-1+deb7u2+b1
Severity: grave
Tags: patch
Justification: causes non-serious data loss
Dear Maintainer,
This bug is perennial. If we go through old
Package: python3-nose
Version: 1.3.7-9
Severity: serious
Tries to import imp which has been deprecated. Broken completely.
-- System Information:
Debian Release: 12.11
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux
54 matches
Mail list logo
