Re: [HEADS UP] posix_fallocate support removed from ZFS, lld affected
On Mon, Nov 06, 2017 at 11:43:42AM -0700, Ed Maste wrote: > On 6 November 2017 at 10:56, Ian Lepore wrote: > > > > Oh, right. lld != ld. > > Indeed, but this will be a problem for the arm64 package builds if > they use ZFS and an 11.x userland on a new kernel. We probably need to > bring the lld change in as an errata. Or make ZFS return (lie) success for p_osrel < bumped osrel. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADS UP] posix_fallocate support removed from ZFS, lld affected
On 6 November 2017 at 10:56, Ian Lepore wrote: > > Oh, right. lld != ld. Indeed, but this will be a problem for the arm64 package builds if they use ZFS and an 11.x userland on a new kernel. We probably need to bring the lld change in as an errata. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADS UP] posix_fallocate support removed from ZFS, lld affected
On Mon, 2017-11-06 at 12:49 -0500, Allan Jude wrote: > On 2017-11-06 12:26, Ian Lepore wrote: > > > > On Mon, 2017-11-06 at 17:40 +0200, Andriy Gapon wrote: > > > > > > From UPDATING: > > > The naive and non-compliant support of posix_fallocate(2) in ZFS > > > has been removed as of r325320. The system call now returns EINVAL > > > when used on a ZFS file. Although the new behavior complies with the > > > standard, some consumers are not prepared to cope with it. > > > One known victim is lld prior to r325420. > > > > > It just popped into my head... does this mean that kernels running > > r325320+ on systems using ZFS will be unable to host build jails for > > earlier versions / branches because lld will fail in the jail? > > > > I think that will be a big problem for the ports team's package > > building process, and for anyone using poudriere. > > > > -- Ian > > > lld is not the default on amd64 yet. So only people who have set the > src.conf knob, or are building a platform like aarch64 that uses lld by > default, would be impacted. > Oh, right. lld != ld. -- Ian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADS UP] posix_fallocate support removed from ZFS, lld affected
On 2017-11-06 12:26, Ian Lepore wrote: > On Mon, 2017-11-06 at 17:40 +0200, Andriy Gapon wrote: >> From UPDATING: >> The naive and non-compliant support of posix_fallocate(2) in ZFS >> has been removed as of r325320. The system call now returns EINVAL >> when used on a ZFS file. Although the new behavior complies with the >> standard, some consumers are not prepared to cope with it. >> One known victim is lld prior to r325420. >> > > It just popped into my head... does this mean that kernels running > r325320+ on systems using ZFS will be unable to host build jails for > earlier versions / branches because lld will fail in the jail? > > I think that will be a big problem for the ports team's package > building process, and for anyone using poudriere. > > -- Ian > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > lld is not the default on amd64 yet. So only people who have set the src.conf knob, or are building a platform like aarch64 that uses lld by default, would be impacted. -- Allan Jude ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADS UP] posix_fallocate support removed from ZFS, lld affected
On Mon, 2017-11-06 at 17:40 +0200, Andriy Gapon wrote: > From UPDATING: > The naive and non-compliant support of posix_fallocate(2) in ZFS > has been removed as of r325320. The system call now returns EINVAL > when used on a ZFS file. Although the new behavior complies with the > standard, some consumers are not prepared to cope with it. > One known victim is lld prior to r325420. > It just popped into my head... does this mean that kernels running r325320+ on systems using ZFS will be unable to host build jails for earlier versions / branches because lld will fail in the jail? I think that will be a big problem for the ports team's package building process, and for anyone using poudriere. -- Ian ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[HEADS UP] posix_fallocate support removed from ZFS, lld affected
>From UPDATING: The naive and non-compliant support of posix_fallocate(2) in ZFS has been removed as of r325320. The system call now returns EINVAL when used on a ZFS file. Although the new behavior complies with the standard, some consumers are not prepared to cope with it. One known victim is lld prior to r325420. >From https://svnweb.freebsd.org/changeset/base/325320 The generic (naive) implementation of posix_fallocate cannot provide the standard mandated guarantee that overwrites would never fail due to the lack of free space. The fundamental reason is the copy-on-write architecture of ZFS. Other features like compression and deduplication can also increase the size difference between the (pre-)allocated dummy content and the future content. So, until ZFS can properly implement the feature it's better to report that it is unsupported rather than providing an ersatz implementation. Please note that EINVAL is used to report that the underlying file system does not support the operation (POSIX.1-2008). illumos and ZoL seem to do the same. lld is affected by the change. That means that any world builds where lld is used are affected as well (if ZFS is involved, of course). One example is the arm64 build (typically a cross build from amd64). The lld issue is fixed in head as of r325420. But other branches are still affected (if you are building them on a head kernel). Other posix_fallocate consumers could be affected too. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: pcsc-lite hangs up after unplugging an USB card reader
On 11/06/17 13:11, Roberto Fernandez Cueto wrote: Roberto Fernandez-Cueto schrieb am 06.11.2017 13:11 _ On Mon, Nov 06, 2017 at 12:55:20PM +0100, Hans Petter Selasky wrote: On 11/06/17 09:27, Roberto Fernandez Cueto wrote: Roberto Fernandez-Cueto schrieb am 06.11.2017 09:27 _ Hi people, the original person who wrote this email has left our company so I will retake it from here. Hi Roberto, Have you read through this thread in the mailing list archives? --HPS Hi Hans, I have recently read the thread and I am trying to get all the information I can before digging more into the matter. It is a complex matter and I just one to try every single possible solution and be advised from the experts in the matter. Thanks in advance, Roberto Hi, In FreeBSD there is a special function that the application can use to check if the USB device is still present: libusb_check_connected() Checking this function regularly and then closing the USB handles might fix the problem you are experiencing. At least for debugging, try to print the value from this function in a separated thread, and check if there are any differences when you experience the hang. Try to use GDB to collect all backtraces for apps using the USB handle. --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: pcsc-lite hangs up after unplugging an USB card reader
Roberto Fernandez-Cueto schrieb am 06.11.2017 13:11 _ On Mon, Nov 06, 2017 at 12:55:20PM +0100, Hans Petter Selasky wrote: > On 11/06/17 09:27, Roberto Fernandez Cueto wrote: > > Roberto Fernandez-Cueto schrieb am 06.11.2017 09:27 > > _ > > > > Hi people, > > > > the original person who wrote this email has left our company so I will > > retake it from here. > > > > Hi Roberto, > > Have you read through this thread in the mailing list archives? > > --HPS Hi Hans, I have recently read the thread and I am trying to get all the information I can before digging more into the matter. It is a complex matter and I just one to try every single possible solution and be advised from the experts in the matter. Thanks in advance, Roberto BALLY WULFF Games & Entertainment GmbH, Maybachufer 48-51, 12045 Berlin, Postanschrift: Postfach 44 01 57, 12001 Berlin Tel.: 030-620 02-0 FAX: 030-620 02-200, Geschaeftsfuehrer: Thomas Niehenke, Lars Rogge, Wolfram Seiffert, Thomas Wendt, Amtsgericht Berlin-Charlottenburg HRB 139020 B, UST-IdNr. DE815328376 _ Dieses E-Mail ist nur fuer den Empfaenger bestimmt, an den es gerichtet ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungs- aeusserung ist die des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung von Bally Wulff Games & Entertainment GmbH dar. Sind Sie nicht der Empfaenger, so haben Sie diese E-Mail irrtuemlich erhalten und jegliche Verwendung, Veroeffentlichung, Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder Bally Wulff Games & Entertainment GmbH noch der Absender uebernehmen die Haftung fuer Viren. Es obliegt Ihrer Verantwortung, die E-Mail und deren Anhaenge auf Viren zu pruefen. Anhaenge: _ Versand am 06.11.2017 13:11 von Fernandez-Cueto Roberto ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: pcsc-lite hangs up after unplugging an USB card reader
On 11/06/17 09:27, Roberto Fernandez Cueto wrote: Roberto Fernandez-Cueto schrieb am 06.11.2017 09:27 _ Hi people, the original person who wrote this email has left our company so I will retake it from here. Hi Roberto, Have you read through this thread in the mailing list archives? --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: pcsc-lite hangs up after unplugging an USB card reader
Roberto Fernandez-Cueto schrieb am 06.11.2017 09:27
_
Hi people,
the original person who wrote this email has left our company so I will
retake it from here.
On Fri, Nov 03, 2017 at 08:38:09PM +0100, Ludovic Rousseau wrote:
> Hello,
>
> Le 01/11/2017 ?? 12:05, Jairo Montes Gonz??lez a ??crit??:
> > Jairo Montes schrieb am 01.11.2017 11:04
> > _
> >
> > The output from "procstat -ak" is attached to this email.
> >
> >
> > As you might see, I'm trying to debug it, but this is my first time using
> >
> > the GDB debugger, so I'm a bit lost with it's usage and I believe I'm not
> >
> > doing a good job with it. All I've found so far is that it keeps looping
> >
> > in somewhere and does not return correctly.
> >
> >
> > I forgot to mention in my first email that I added the lines to
> >
> > /etc/devd.conf that the pcsc-lite installation tells you to add for USB
> >
> > cardreaders. I also added /usr/local/etc/devd/pcscd.conf, attached here
> >
> > too, just in case it produces any kind of conflict.
>
> pcsc-lite has its own polling method.
> You should not need to use the /etc/devd.conf file
>
It doesn't matter, the problem occurs whether we put the following lines
in devd.conf(5) or not. The configuration has been stripped to the
important lines.
notify xxx {
...
action "/usr/local/sbin/pcscd -H";
}
> I must add that I do not remember when I tested pcsc-lite with FreeBSD.
>
> Bye,
>
> --
> Dr. Ludovic Rousseau
So far, the main problem has been occurring with some card readers and
more often when several USB card readers are attached to the machine.
We have realized that pcscd(8) tries to end the threads created for the
card reader and, ofter with two card readers, it does not get out of the
critical section.
It seems like a deadlock to us, but we cannot confirm it because we do
not understand completely pcscs-lite.
We ask for some place to start looking at, because we have been dealing
with the problem blindly until now.
Thank you in advance,
--
Roberto Fernandez Cueto
System developer
Bally Wulff Games & Entertainment GmbH
BALLY WULFF Games & Entertainment GmbH, Maybachufer 48-51, 12045 Berlin,
Postanschrift: Postfach 44 01 57, 12001 Berlin Tel.: 030-620 02-0 FAX: 030-620
02-200, Geschaeftsfuehrer: Thomas Niehenke, Lars Rogge, Wolfram Seiffert,
Thomas Wendt, Amtsgericht Berlin-Charlottenburg HRB 139020 B, UST-IdNr.
DE815328376
_
Dieses E-Mail ist nur fuer den Empfaenger bestimmt, an den es gerichtet
ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes
Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungs-
aeusserung ist die des Autors und stellt nicht notwendigerweise die
Ansicht oder Meinung von Bally Wulff Games & Entertainment GmbH dar.
Sind Sie nicht der Empfaenger, so haben Sie diese E-Mail irrtuemlich
erhalten und jegliche Verwendung, Veroeffentlichung, Weiterleitung,
Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt.
Weder Bally Wulff Games & Entertainment GmbH noch der Absender
uebernehmen die Haftung fuer Viren. Es obliegt Ihrer Verantwortung,
die E-Mail und deren Anhaenge auf Viren zu pruefen.
Anhaenge:
_
Versand am 06.11.2017 09:27 von Fernandez-Cueto Roberto
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
