Re: Last call: removing the INT_MAX limit on max i/o size
* Konstantin Belousov kostik...@gmail.com [120217 17:54] wrote: This is a notification to allow you to comment on the patch before the commit. I will commit the latest version of the patch to remove the limitation of the maximal i/o size for read/write syscalls to INT_MAX in the beginning of the next week. The change is available at http://people.freebsd.org/~kib/misc/uio_resid.10.patch various versions of it were discussed with Bruce Evance and David Schultz. Patch does not enable SSIZE_MAX-sized i/o by default, hiding this under debug.iosize_max_clamp sysctl. Effectively, the patch becomes the pass to change various ints into ssize_t. I always wonder if it's worth defining a type for this, resid_t or something, therefor you could use some tricks to generate warnings when it's cast to a type that normally would not generate warnings but could cause some loss or issue otherwise. Probably not. -- - Alfred Perlstein .- VMOA #5191, 03 vmax, 92 gs500, 85 ch250, 07 zx10 .- FreeBSD committer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Last call: removing the INT_MAX limit on max i/o size
* Poul-Henning Kamp p...@phk.freebsd.dk [120218 00:34] wrote: In message 20120218074655.gf31...@elvis.mu.org, Alfred Perlstein writes: I always wonder if it's worth defining a type for this, resid_t or something, Wouldn't that naturally be size_t ? I think that makes sense. I was thinking along the lines of making sure that functions that take a resid_t aren't actually being passed the wrong ssize_t, but really that's probably too much fence and just would obfuscate things. -- - Alfred Perlstein .- VMOA #5191, 03 vmax, 92 gs500, 85 ch250, 07 zx10 .- FreeBSD committer ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Last call: removing the INT_MAX limit on max i/o size
In message 20120218074655.gf31...@elvis.mu.org, Alfred Perlstein writes: I always wonder if it's worth defining a type for this, resid_t or something, Wouldn't that naturally be size_t ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: devd based AUTOMOUNTER
Added a check if ntfs-3g is available, if not then mount_ntfs is used instead.
Added deleting of empty directories at ${MNTPREFIX}.
Added ${MNTPREFIX} to be set to /mnt or /media according to preference
#! /bin/sh
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
MNTPREFIX=/media
LOG=/var/log/automount.log
STATE=/var/run/automount.state
DATEFMT=%Y-%m-%d %H:%M:%S
__create_mount_point() { # /* 1=DEV */
MNT=${MNTPREFIX}/$( basename ${1} )
mkdir -p ${MNT}
}
__state_lock() {
while [ -f ${STATE}.lock ]; do sleep 0.5; done
: ${STATE}.lock
}
__state_unlock() {
rm ${STATE}.lock
}
__state_add() { # /* 1=DEV 2=PROVIDER 3=MNT */
__state_lock
grep -E ${3} ${STATE} 1 /dev/null 2 /dev/null {
__log ${1}:duplicated '${STATE}'
return 1
}
echo ${1} ${2} ${3} ${STATE}
__state_unlock
}
__state_remove() { # /* 1=MNT 2=STATE 3=LINE */
BSMNT=$( echo ${1} | sed 's/\//\\\//g' )
sed -i '' /${BSMNT}\$/d ${2}
}
__log() { # /* @=MESSAGE */
echo $( date +${DATEFMT} ) ${@} ${LOG}
}
case ${2} in
(attach)
for I in /dev/${1}*
do
case $( file -L -s ${I} | sed -E 's/label:\ \.*\//g' ) in
(*NTFS*)
dd ${I} count=1 2 /dev/null \
| strings \
| head -1 \
| grep -q NTFS {
__create_mount_point ${I}
which ntfs-3g 1 /dev/null 2 /dev/null {
ntfs-3g ${I} ${MNT} # /* sysutils/fusefs-ntfs */
} || {
mount_ntfs ${I} ${MNT}
}
__log ${I}:mount (ntfs)
}
;;
(*FAT*)
dd ${I} count=1 2 /dev/null \
| strings \
| grep -q FAT32 {
__create_mount_point ${I}
fsck_msdosfs -y ${I}
mount_msdosfs -o large -l -L pl_PL.ISO8859-2 -D cp852 ${I} ${MNT}
__log ${I}:mount (fat)
}
;;
(*ext2*)
__create_mount_point ${I}
fsck.ext2 -y ${I}
mount -t ext2fs ${I} ${MNT}
__log ${I}:mount (ext2)
;;
(*ext3*)
__create_mount_point ${I}
fsck.ext3 -y ${I}
mount -t ext2fs ${I} ${MNT}
__log ${I}:mount (ext3)
;;
(*ext4*)
__create_mount_point ${I}
fsck.ext4 -y ${I}
ext4fuse ${I} ${MNT} # /* sysutils/fusefs-ext4fuse */
__log ${I}:mount (ext4)
;;
(*Unix\ Fast\ File*)
__create_mount_point ${I}
fsck_ufs -y ${I}
mount ${I} ${MNT}
__log ${I}:mount (ufs)
;;
(*)
case $( dd ${I} count=1 2 /dev/null | strings | head -1 ) in
(EXFAT)
__create_mount_point ${I}
mount.exfat ${I} ${MNT} # /* sysutils/fusefs-exfat */
__log ${I}:mount (ufs)
;;
(*) continue ;;
esac
;;
esac
__state_add ${I} $( mount | grep -m 1 ${MNT} | awk '{printf $1}' ) \
${MNT} || continue
done
;;
(detach)
MOUNT=$( mount )
__state_lock
grep ${1} ${STATE} \
| while read DEV PROVIDER MNT
do
TARGET=$( echo ${MOUNT} | grep -E ^${PROVIDER} | awk '{print
$3}' )
[ -z ${TARGET} ] {
__state_remove ${MNT} ${STATE} ${LINE}
continue
}
umount -f ${TARGET}
unset TARGET
__state_remove ${MNT} ${STATE} ${LINE}
__log ${DEV}:umount
done
__state_unlock
__log /dev/${1}:detach
find ${MNTPREFIX} -type d -empty -delete
;;
esac
Not sure if you've looked at disktype in sysutils
but it may be useful to you.
I will get look into that, thanks ;)
Neat scripts!
Matt
Thanks mate.
Regards,
vermaden
--
...
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: devd based AUTOMOUNTER
On Saturday 18 February 2012 10:48:11 vermaden wrote:
Added a check if ntfs-3g is available, if not then mount_ntfs is used
instead. Added deleting of empty directories at ${MNTPREFIX}.
Added ${MNTPREFIX} to be set to /mnt or /media according to preference
#! /bin/sh
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
MNTPREFIX=/media
LOG=/var/log/automount.log
STATE=/var/run/automount.state
DATEFMT=%Y-%m-%d %H:%M:%S
__create_mount_point() { # /* 1=DEV */
MNT=${MNTPREFIX}/$( basename ${1} )
mkdir -p ${MNT}
}
__state_lock() {
while [ -f ${STATE}.lock ]; do sleep 0.5; done
: ${STATE}.lock
}
__state_unlock() {
rm ${STATE}.lock
}
__state_add() { # /* 1=DEV 2=PROVIDER 3=MNT */
__state_lock
grep -E ${3} ${STATE} 1 /dev/null 2 /dev/null {
__log ${1}:duplicated '${STATE}'
return 1
}
echo ${1} ${2} ${3} ${STATE}
__state_unlock
}
__state_remove() { # /* 1=MNT 2=STATE 3=LINE */
BSMNT=$( echo ${1} | sed 's/\//\\\//g' )
sed -i '' /${BSMNT}\$/d ${2}
}
__log() { # /* @=MESSAGE */
echo $( date +${DATEFMT} ) ${@} ${LOG}
}
case ${2} in
(attach)
for I in /dev/${1}*
do
case $( file -L -s ${I} | sed -E 's/label:\ \.*\//g' ) in
(*NTFS*)
dd ${I} count=1 2 /dev/null \
| strings \
| head -1 \
| grep -q NTFS {
__create_mount_point ${I}
which ntfs-3g 1 /dev/null 2 /dev/null {
ntfs-3g ${I} ${MNT} # /* sysutils/fusefs-ntfs */
} || {
mount_ntfs ${I} ${MNT}
}
__log ${I}:mount (ntfs)
}
;;
(*FAT*)
dd ${I} count=1 2 /dev/null \
| strings \
| grep -q FAT32 {
__create_mount_point ${I}
fsck_msdosfs -y ${I}
mount_msdosfs -o large -l -L pl_PL.ISO8859-2 -D cp852 ${I}
${MNT} __log ${I}:mount (fat)
}
;;
(*ext2*)
__create_mount_point ${I}
fsck.ext2 -y ${I}
mount -t ext2fs ${I} ${MNT}
__log ${I}:mount (ext2)
;;
(*ext3*)
__create_mount_point ${I}
fsck.ext3 -y ${I}
mount -t ext2fs ${I} ${MNT}
__log ${I}:mount (ext3)
;;
(*ext4*)
__create_mount_point ${I}
fsck.ext4 -y ${I}
ext4fuse ${I} ${MNT} # /* sysutils/fusefs-ext4fuse */
__log ${I}:mount (ext4)
;;
(*Unix\ Fast\ File*)
__create_mount_point ${I}
fsck_ufs -y ${I}
mount ${I} ${MNT}
__log ${I}:mount (ufs)
;;
(*)
case $( dd ${I} count=1 2 /dev/null | strings | head -1 ) in
(EXFAT)
__create_mount_point ${I}
mount.exfat ${I} ${MNT} # /* sysutils/fusefs-exfat */
__log ${I}:mount (ufs)
;;
(*) continue ;;
esac
;;
esac
__state_add ${I} $( mount | grep -m 1 ${MNT} | awk '{printf $1}'
) \ ${MNT} || continue
done
;;
(detach)
MOUNT=$( mount )
__state_lock
grep ${1} ${STATE} \
| while read DEV PROVIDER MNT
do
TARGET=$( echo ${MOUNT} | grep -E ^${PROVIDER} | awk '{print
$3}' ) [ -z ${TARGET} ] {
__state_remove ${MNT} ${STATE} ${LINE}
continue
}
umount -f ${TARGET}
unset TARGET
__state_remove ${MNT} ${STATE} ${LINE}
__log ${DEV}:umount
done
__state_unlock
__log /dev/${1}:detach
find ${MNTPREFIX} -type d -empty -delete
;;
esac
Not sure if you've looked at disktype in sysutils
but it may be useful to you.
Hi,
Should your script be written like an rc.d script, so that one can
enable/disable this automounting from /etc/rc.conf?
--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: devd based AUTOMOUNTER
On (18/02/2012 10:48), vermaden wrote:
Added a check if ntfs-3g is available, if not then mount_ntfs is used instead.
Added deleting of empty directories at ${MNTPREFIX}.
Added ${MNTPREFIX} to be set to /mnt or /media according to preference
#! /bin/sh
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
MNTPREFIX=/media
LOG=/var/log/automount.log
STATE=/var/run/automount.state
DATEFMT=%Y-%m-%d %H:%M:%S
__create_mount_point() { # /* 1=DEV */
MNT=${MNTPREFIX}/$( basename ${1} )
mkdir -p ${MNT}
}
__state_lock() {
while [ -f ${STATE}.lock ]; do sleep 0.5; done
: ${STATE}.lock
}
Why not keep it stateless, unmounting by hand would kill integrity.
Usage of `file` is a big security concern.
I think geom config and list of mounted file systems should be
sufficient for collecting information at runtime. Although it may not be
that easy for disks without partitioning.
I'm using a python script for mounting/unmounting removable disks,
but having similar tool written in sh would be great.
https://github.com/glk/mmount
Thanks,
Gleb.
__state_unlock() {
rm ${STATE}.lock
}
__state_add() { # /* 1=DEV 2=PROVIDER 3=MNT */
__state_lock
grep -E ${3} ${STATE} 1 /dev/null 2 /dev/null {
__log ${1}:duplicated '${STATE}'
return 1
}
echo ${1} ${2} ${3} ${STATE}
__state_unlock
}
__state_remove() { # /* 1=MNT 2=STATE 3=LINE */
BSMNT=$( echo ${1} | sed 's/\//\\\//g' )
sed -i '' /${BSMNT}\$/d ${2}
}
__log() { # /* @=MESSAGE */
echo $( date +${DATEFMT} ) ${@} ${LOG}
}
case ${2} in
(attach)
for I in /dev/${1}*
do
case $( file -L -s ${I} | sed -E 's/label:\ \.*\//g' ) in
(*NTFS*)
dd ${I} count=1 2 /dev/null \
| strings \
| head -1 \
| grep -q NTFS {
__create_mount_point ${I}
which ntfs-3g 1 /dev/null 2 /dev/null {
ntfs-3g ${I} ${MNT} # /* sysutils/fusefs-ntfs */
} || {
mount_ntfs ${I} ${MNT}
}
__log ${I}:mount (ntfs)
}
;;
(*FAT*)
dd ${I} count=1 2 /dev/null \
| strings \
| grep -q FAT32 {
__create_mount_point ${I}
fsck_msdosfs -y ${I}
mount_msdosfs -o large -l -L pl_PL.ISO8859-2 -D cp852 ${I}
${MNT}
__log ${I}:mount (fat)
}
;;
(*ext2*)
__create_mount_point ${I}
fsck.ext2 -y ${I}
mount -t ext2fs ${I} ${MNT}
__log ${I}:mount (ext2)
;;
(*ext3*)
__create_mount_point ${I}
fsck.ext3 -y ${I}
mount -t ext2fs ${I} ${MNT}
__log ${I}:mount (ext3)
;;
(*ext4*)
__create_mount_point ${I}
fsck.ext4 -y ${I}
ext4fuse ${I} ${MNT} # /* sysutils/fusefs-ext4fuse */
__log ${I}:mount (ext4)
;;
(*Unix\ Fast\ File*)
__create_mount_point ${I}
fsck_ufs -y ${I}
mount ${I} ${MNT}
__log ${I}:mount (ufs)
;;
(*)
case $( dd ${I} count=1 2 /dev/null | strings | head -1 ) in
(EXFAT)
__create_mount_point ${I}
mount.exfat ${I} ${MNT} # /* sysutils/fusefs-exfat */
__log ${I}:mount (ufs)
;;
(*) continue ;;
esac
;;
esac
__state_add ${I} $( mount | grep -m 1 ${MNT} | awk '{printf $1}' ) \
${MNT} || continue
done
;;
(detach)
MOUNT=$( mount )
__state_lock
grep ${1} ${STATE} \
| while read DEV PROVIDER MNT
do
TARGET=$( echo ${MOUNT} | grep -E ^${PROVIDER} | awk '{print
$3}' )
[ -z ${TARGET} ] {
__state_remove ${MNT} ${STATE} ${LINE}
continue
}
umount -f ${TARGET}
unset TARGET
__state_remove ${MNT} ${STATE} ${LINE}
__log ${DEV}:umount
done
__state_unlock
__log /dev/${1}:detach
find ${MNTPREFIX} -type d -empty -delete
;;
esac
Not sure if you've looked at disktype in sysutils
but it may be useful to you.
I will get look into that, thanks ;)
Neat scripts!
Matt
Thanks mate.
Regards,
vermaden
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Packages for Current ( 10.0 )
On Fri, Feb 17, 2012 at 12:04:45AM -0500, Mehmet Erol Sanliturk wrote: I would be very happy I can contribute anything to development of FreeBSD . We are always happy to have help :-) If there appears an agenda of testing problems and explicit instructions how to apply tests , me and other persons may apply them and report the results . Well, there really isn't. There are some regression tests for src, but we have never established a framework to run them all automatically. Perhaps this is something you might be interested in? In a message ( I do not remember its author's name ) it is said that there is no a farm of FreeBSD testing machines . I presume that's now for no? There are several sets. Here's how they are set up. - there is a src tinderbox which continually rebuilds the FreeBSD src tree, for various combinations of architectures and osreleases. (For src, the architectures can be cross-built.) These are intended to sanity-test that src is still buildable; in general the resulting binaries are not made available. - there is a clang buildbot whose purpose is to build FreeBSD src under clang continuously. - various people maintain ports tinderboxes. These are optimized for test-builds of one or at least a subset of the ports tree. In general the resulting binaries are not made available. - there is a new effort, Redports, to assemble a collection of ports tinderbox machines and make them available to interested people. We are actively working on this. - portmgr maintains the pointyhat cluster that do the package builds which are uploaded. These are optimized for building the entire ports tree in a secure fashion; the resulting binaries are made available. We are in the process of getting more machines online. - the pointyhat cluster is also used for -exp runs where portmgr regression-tests proposed changes to the overall ports tree to try to ensure as few regressions for large changes as possible. If we can generate such a testing ecological system , I think , FreeBSD development will benefit from it very much . I agree. But, for src, it's not something that I know much about, and will have to defer to others to comment. mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Problems with 9.0 PowerPC images from main ftp site
I decided to try burning an image from Index of ftp://ftp.freebsd.org/pub/FreeBSD/releases/powerpc/powerpc/ISO-IMAGES/9.0/ And here are the following errors: 1.) The usb image doesn't boot. From following Whitehorn and others on the FreeBSD PowerPC mailing list, one needs to have the bootloader dd'ed to a HFS formatted partition of 1MB. A README with basic instructions and/or references to forum and mailing list posts needs to be available for all non i386/amd64 systems. 2) The boot-only and disc-1 images stop at sc0: Unknown 16 virtual consoles, flags=0x300 Booting with -s or -v or a combination does nothing. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: x220 notes
On 02/12/12 12:29, Hannes Mehnert wrote: Hi, I recently got a X220 and installed -CURRENT (with kib's 13.1 patch) on it - let me add some notes on this thread. On 10/17/2011 03:53, Matt wrote: On 09/28/11 16:01, Kevin Oberman wrote: On Wed, Sep 28, 2011 at 12:32 PM, Garrett Cooperyaneg...@gmail.com wrote: On Wed, Sep 28, 2011 at 12:25 PM, Mattsendtom...@gmail.com wrote: On 09/28/11 11:52, Garrett Cooper wrote: On Wed, Sep 28, 2011 at 11:48 AM, Mattsendtom...@gmail.comwrote: acpi_ibm needs LEN0068 added to the list of ibm ids at the beginning of /usr/src/sys/dev/acpi_support/acpi_ibm.c...I'd write a patch but that machine is in a world of ports hurt right now :). With this many of the sysctls and leds work, still no brightness (w or wout intel DRI from Konstantin...thanks Konstantin!!) (there's a pr about that kern/164538) I'm not sure if I mentioned this in another post, but I can confirm that adjusting brightness in ibm_acpi for me results in corrupting the fan speed, which makes me think that addresses have changed, widths/extents have changed, or something else is different. For what it's worth, thinkpad-acpi in Linux does this just fine, although I haven't determined if it's through the EC or ACPI...I am thinking EC however. I have a feeling the answer to brightness (aside from KMS patch for X, which is seperate) might be comparing changelogs for thinkpad ec handlers on a platform that works like Linux...the code looks mostly similar...can anyone confirm if Open/NetBSD have issues with the backlight on these SandyBridge thinkpads? The brightness work fine on Linux, but not on OpenBSD(-CURRENT). But on OpenBSD xbacklight (which uses randr) works to set the brightness once in X. This unfortunately does not work on FreeBSD (receiving No outputs have backlight property when running xbacklight). Cheers, Hannes ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org I got 10-CURRENT installed on the x220 again. 1. Standard GENERIC kernel 2. Buildworld/installworld from today's CVS 3. No DRM/KMS patches or any other factors 4. Witness KDB disabled in loader.conf (otherwise panic on suspend). 5. setting hw.pci.do_power_suspend=0 wil prevent some AE_NO_METHOD errors where it tries to set PCI express ports to D2 (the ports themselves, I think...not the attached device) This is what I've found as I investigate the backlight/resume issue. I am not very good at understanding ASL, but here's what I see. 1. _WAK calls a number of display related methods 2. There are apparently brightness related calls here, as well as some other video related calls 3. Some of this behavior depends on /VIGD, whatever that is. 4. The brightness calls seem to connect over LPC to the embedded controller 5. Some of the brightness methods check OSI for WIN7 I will add that iasl finds 35 errors in this fine piece of lenovo work. However, none of the errors appear to be near _wak. I've attached an acpidump asl if it helps anyone who has a better eye for ASL and resume/brightness problems. I think we can control brightness at least with acpi_video, it attaches but not correctly...active=0...I haven't gone back over its source in comparison with ASL yet either. Probably acpi_ibm will work also, as the acpi methods seem to just call the embedded controller over the lpc bus? Unfortunately it seems something has changed with the ec, as some of the data becomes corrupt when acpi_ibm is loaded. Resume obviously works fine in Win7, works 80-95% of the time in Linux (seems like KMS fail when it doesn't resume on Linux), and it resumes fine on FreeBSD except no video. No bad messages in logs after resume. Matt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
