Eric Lee / smarc-fsl-linux-kernel

12 Oct, 2006

1 commit

  • 39484e53b   [PATCH] 32-bit compatibility HDIO IOCTLs ... Browse Code »

    A couple of HDIO IOCTLs are not yet handled and a few others are marked
    as using a pointer rather than an unsigned long. The formers include:

    HDIO_GET_WCACHE, HDIO_GET_ACOUSTIC, HDIO_GET_ADDRESS and
    HDIO_GET_BUSSTATE. The latters are: HDIO_SET_MULTCOUNT,
    HDIO_SET_UNMASKINTR, HDIO_SET_KEEPSETTINGS, HDIO_SET_32BIT,
    HDIO_SET_NOWERR, HDIO_SET_DMA, HDIO_SET_PIO_MODE and HDIO_SET_NICE.

    Additionally 0x330 used to be HDIO_GETGEO_BIG and may be issued by 32-bit
    `hdparm' run on a 64-bit kernel making Linux complain loudly.

    This is a fix for these issues.

    Signed-off-by: Maciej W. Rozycki
    Cc: Alan Cox
    Acked-by: Arnd Bergmann
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Maciej W. Rozycki
     

01 Oct, 2006

9 commits

  • 54f67f631   [PATCH] Move ncpfs 32bit compat ioctl to ncpfs ... Browse Code »

    The ncp specific compat ioctls are clearly local to one file system, so the
    code can better live there.

    This version of the patch moves everything into the generic ioctl handler
    and uses it for both 32 and 64 bit calls.

    Signed-off-by: Arnd Bergmann
    Signed-off-by: Petr Vandrovec
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Petr Vandrovec
     
  • 9361401eb   [PATCH] BLOCK: Make it possible to disable the block layer [try #6] ... Browse Code »

    Make it possible to disable the block layer. Not all embedded devices require
    it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
    the block layer to be present.

    This patch does the following:

    (*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
    support.

    (*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls
    an item that uses the block layer. This includes:

    (*) Block I/O tracing.

    (*) Disk partition code.

    (*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.

    (*) The SCSI layer. As far as I can tell, even SCSI chardevs use the
    block layer to do scheduling. Some drivers that use SCSI facilities -
    such as USB storage - end up disabled indirectly from this.

    (*) Various block-based device drivers, such as IDE and the old CDROM
    drivers.

    (*) MTD blockdev handling and FTL.

    (*) JFFS - which uses set_bdev_super(), something it could avoid doing by
    taking a leaf out of JFFS2's book.

    (*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and
    linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,
    however, still used in places, and so is still available.

    (*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and
    parts of linux/fs.h.

    (*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.

    (*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.

    (*) set_page_dirty() doesn't call __set_page_dirty_buffers() if CONFIG_BLOCK
    is not enabled.

    (*) fs/no-block.c is created to hold out-of-line stubs and things that are
    required when CONFIG_BLOCK is not set:

    (*) Default blockdev file operations (to give error ENODEV on opening).

    (*) Makes some /proc changes:

    (*) /proc/devices does not list any blockdevs.

    (*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.

    (*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.

    (*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if
    given command other than Q_SYNC or if a special device is specified.

    (*) In init/do_mounts.c, no reference is made to the blockdev routines if
    CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.

    (*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return
    error ENOSYS by way of cond_syscall if so).

    (*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if
    CONFIG_BLOCK is not set, since they can't then happen.

    Signed-Off-By: David Howells
    Signed-off-by: Jens Axboe

    David Howells
     
  • 188f83dfe   [PATCH] BLOCK: Move the msdos device ioctl compat stuff to the msdos driver [try #6] ... Browse Code »

    Move the msdos device ioctl compat stuff from fs/compat_ioctl.c to the msdos
    driver so that the msdos header file doesn't need to be included.

    Signed-Off-By: David Howells
    Signed-off-by: Jens Axboe

    David Howells
     
  • 52a700c56   [PATCH] BLOCK: Move the Ext3 device ioctl compat stuff to the Ext3 driver [try #6] ... Browse Code »

    Move the Ext3 device ioctl compat stuff from fs/compat_ioctl.c to the Ext3
    driver so that the Ext3 header file doesn't need to be included.

    Signed-Off-By: David Howells
    Signed-off-by: Jens Axboe

    David Howells
     
  • e322ff07f   [PATCH] BLOCK: Move the Ext2 device ioctl compat stuff to the Ext2 driver [try #6] ... Browse Code »

    Move the Ext2 device ioctl compat stuff from fs/compat_ioctl.c to the Ext2
    driver so that the Ext2 header file doesn't need to be included.

    Signed-Off-By: David Howells
    Signed-off-by: Jens Axboe

    David Howells
     
  • 52b499c43   [PATCH] BLOCK: Move the ReiserFS device ioctl compat stuff to the ReiserFS driver [try #6] ... Browse Code »

    Move the ReiserFS device ioctl compat stuff from fs/compat_ioctl.c to the
    ReiserFS driver so that the ReiserFS header file doesn't need to be included.

    Signed-Off-By: David Howells
    Signed-off-by: Jens Axboe

    David Howells
     
  • 36695673b   [PATCH] BLOCK: Move common FS-specific ioctls to linux/fs.h [try #6] ... Browse Code »

    Move common FS-specific ioctls from linux/ext2_fs.h to linux/fs.h as FS_IOC_*
    and FS_IOC32_* and have the users of them use those as a base.

    Also move the GETFLAGS/SETFLAGS flags to linux/fs.h as FS_*_FL macros, and then
    have the other users use them as a base.

    Signed-Off-By: David Howells
    Signed-off-by: Jens Axboe

    David Howells
     
  • 863d5b822   [PATCH] BLOCK: Move the loop device ioctl compat stuff to the loop driver [try #6] ... Browse Code »

    Move the loop device ioctl compat stuff from fs/compat_ioctl.c to the loop
    driver so that the loop header file doesn't need to be included.

    Signed-Off-By: David Howells
    Signed-off-by: Jens Axboe

    David Howells
     
  • 07f3f05c1   [PATCH] BLOCK: Move extern declarations out of fs/*.c into header files [try #6] ... Browse Code »

    Create a new header file, fs/internal.h, for common definitions local to the
    sources in the fs/ directory.

    Move extern definitions that should be in header files from fs/*.c to
    fs/internal.h or other main header files where they span directories.

    Signed-Off-By: David Howells
    Signed-off-by: Jens Axboe

    David Howells
     

01 Jul, 2006

1 commit

27 Jun, 2006

2 commits

25 Jun, 2006

1 commit

  • 1b77c54ee   V4L/DVB (3809a): Remove compat stuff for DMX_GET_EVENT ... Browse Code »

    The ioctl were removed by:
    V4L/DVB (3727): Remove DMX_GET_EVENT and associated data structures
    due to the ioctl DMX_GET_EVENT has never been implemented, and also
    scrambling events can't be generated in a useful way by the hardware.

    This patch removes the corresponding entry at fs/compat_ioctl.c

    Signed-off-by: Andrew Morton
    Signed-off-by: Mauro Carvalho Chehab

    Andrew Morton
     

24 Mar, 2006

2 commits

09 Mar, 2006

1 commit

  • 1efa3c05f   [NET] compat ifconf: fix limits ... Browse Code »

    A recent change to compat. dev_ifconf() in fs/compat_ioctl.c
    causes ifconf data to be truncated 1 entry too early when copying it
    to userspace. The correct amount of data (length) is returned,
    but the final entry is empty (zero, not filled in).
    The for-loop 'i' check should use
    Signed-off-by: David S. Miller

    Randy Dunlap
     

27 Feb, 2006

1 commit

08 Feb, 2006

1 commit

13 Jan, 2006

1 commit

12 Jan, 2006

2 commits

11 Jan, 2006

2 commits

  • e6a6d2efc   [PATCH] sanitize building of fs/compat_ioctl.c ... Browse Code »

    Now that all these entries in the arch ioctl32.c files are gone [1], we can
    build fs/compat_ioctl.c as a normal object and kill tons of cruft. We need a
    special do_ioctl32_pointer handler for s390 so the compat_ptr call is done.
    This is not needed but harmless on all other architectures. Also remove some
    superflous includes in fs/compat_ioctl.c

    Tested on ppc64.

    [1] parisc still had it's PPP handler left, which is not fully correct
    for ppp and besides that ppp uses the generic SIOCPRIV ioctl so it'd
    kick in for all netdevice users. We can introduce a proper handler
    in one of the next patch series by adding a compat_ioctl method to
    struct net_device but for now let's just kill it - parisc doesn't
    compile in mainline anyway and I don't want this to block this
    patchset.

    Signed-off-by: Christoph Hellwig
    Cc: Matthew Wilcox
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Christoph Hellwig
     
  • ec3cad969   [PATCH] move rtc compat ioctl handling to fs/compat_ioctl.c ... Browse Code »

    This patch implements generic handling of RTC_IRQP_READ32, RTC_IRQP_SET32,
    RTC_EPOCH_READ32 and RTC_EPOCH_SET32 in fs/compat_ioctl.c. It's based on the
    x86_64 code which needed a little massaging to be endian-clean.

    parisc used COMPAT_IOCTL or generic w_long handlers for these whichce is wrong
    and can't work because the ioctls encode sizeof(unsigned long) in their ioctl
    number. parisc also duplicated COMPAT_IOCTL entries for other rtc ioctls
    which I remove in this patch, too.

    Signed-off-by: Christoph Hellwig
    Acked-by: Matthew Wilcox
    Acked-by: "David S. Miller"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Christoph Hellwig
     

10 Jan, 2006

1 commit

  • 0d0fbf815   V4L (926_2): Moves compat32 functions from fs to v4l subsystem ... Browse Code »

    This moves the 32 bit ioctl compatibility handlers for
    Video4Linux into a new file and adds explicit calls to them
    to each v4l device driver.

    Unfortunately, there does not seem to be any code handling
    the v4l2 ioctls, so quite often the code goes through two
    separate conversions, first from 32 bit v4l to 64 bit v4l,
    and from there to 64 bit v4l2. My patch does not change
    that, so there is still much room for improvement.

    Also, some drivers have additional ioctl numbers, for
    which the conversion should be handled internally to
    that driver.

    Signed-off-by: Arnd Bergmann
    Signed-off-by: Mauro Carvalho Chehab

    Arnd Bergmann
     

21 Nov, 2005

1 commit

  • 4909724b5   [COMPAT] net: SIOCGIFCONF data corruption ... Browse Code »

    From: Alexandra Kossovsky

    From http://bugzilla.kernel.org/show_bug.cgi?id=4746

    There is user data corruption when using ioctl(SIOCGIFCONF) in 32-bit
    application running amd64 kernel. I do not think that this problem is
    exploitable, but any data corruption may lead to security problems.
    Following code demonstrates the problem

    #include
    #include
    #include
    #include
    #include
    #include

    char buf[256];

    main()
    {
    int s = socket(AF_INET, SOCK_DGRAM, 0);
    struct ifconf req;
    int i;

    req.ifc_buf = buf;
    req.ifc_len = 41;

    printf("Result %d\n", ioctl(s, SIOCGIFCONF, &req));
    printf("Len %d\n", req.ifc_len);
    for (i = 41; i < 256; i++)
    if (buf[i] != 0)
    printf("Byte %d is corrupted\n", i);
    }

    Steps to reproduce:
    Compile the code above into 32-bit elf and run it. You'll get
    Result 0
    Len 32
    Byte 48 is corrupted
    Byte 52 is corrupted
    Byte 53 is corrupted
    Byte 54 is corrupted
    Byte 55 is corrupted

    Signed-off-by: Andrew Morton
    Signed-off-by: David S. Miller

    Alexandra Kossovsky
     

19 Nov, 2005

1 commit

18 Nov, 2005

1 commit

16 Nov, 2005

1 commit

09 Nov, 2005

2 commits

07 Nov, 2005

1 commit

  • f99d49adf   [PATCH] kfree cleanup: fs ... Browse Code »

    This is the fs/ part of the big kfree cleanup patch.

    Remove pointless checks for NULL prior to calling kfree() in fs/.

    Signed-off-by: Jesper Juhl
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jesper Juhl
     

31 Oct, 2005

1 commit

  • 9c0cbd54c   [PATCH] TIOC* compat ioctl handling ... Browse Code »

    TIOCSTART and TIOCSTOP are defined in asm/ioctls.h and asm/termios.h by
    various architectures but not actually implemented anywhere but in the IRIX
    compatibility layer, so remove their COMPATIBLE_IOCTL from parisc, ppc64
    and sparc64.

    Move the TIOCSLTC COMPATIBLE_IOCTL to common code, guided by an ifdef to
    only show up on architectures that support it (same as the code handling it
    in tty_ioctl.c), aswell as it's brother TIOCGLTC that wasn't handled so
    far.

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Christoph Hellwig
     

29 Oct, 2005

1 commit

  • c36fc889b   [PATCH] usb: Patch for USBDEVFS_IOCTL from 32-bit programs ... Browse Code »

    Dell supplied me with the following test:

    #include
    #include
    #include
    #include
    #include

    main(int argc,char*argv[])
    {
    struct usbdevfs_hub_portinfo hubPortInfo = {0};
    struct usbdevfs_ioctl command = {0};
    command.ifno = 0;
    command.ioctl_code = USBDEVFS_HUB_PORTINFO;
    command.data = (void*)&hubPortInfo;
    int fd, ret;
    if(argc != 2) {
    fprintf(stderr,"Usage: %s /proc/bus/usb//\n",argv[0]);
    fprintf(stderr,"Example: %s /proc/bus/usb/001/001\n",argv[0]);
    exit(1);
    }
    errno = 0;
    fd = open(argv[1],O_RDWR);
    if(fd < 0) {
    perror("open failed:");
    exit(errno);
    }
    errno = 0;
    ret = ioctl(fd,USBDEVFS_IOCTL,&command);
    printf("IOCTL return status:%d\n",ret);
    if(ret
    Signed-off-by: Greg Kroah-Hartman

    Pete Zaitcev
     

10 Sep, 2005

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds