1. 14 2月, 2014 32 次提交
  2. 13 2月, 2014 1 次提交
  3. 10 2月, 2014 1 次提交
    • A
      fix a kmap leak in virtio_console · c9efe511
      Al Viro 提交于
      While we are at it, don't do kmap() under kmap_atomic(), *especially*
      for a page we'd allocated with GFP_KERNEL.  It's spelled "page_address",
      and had that been more than that, we'd have a real trouble - kmap_high()
      can block, and doing that while holding kmap_atomic() is a Bad Idea(tm).
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      c9efe511
  4. 08 2月, 2014 4 次提交
    • R
      watchdog: dw_wdt: Add dependency on HAS_IOMEM · 1ccfe6f9
      Richard Weinberger 提交于
      On archs like S390 or um this driver cannot build nor work.
      Make it depend on HAS_IOMEM to bypass build failures.
      
      drivers/built-in.o: In function `dw_wdt_drv_probe':
      drivers/watchdog/dw_wdt.c:302: undefined reference to `devm_ioremap_resource'
      Signed-off-by: NRichard Weinberger <richard@nod.at>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      1ccfe6f9
    • H
      tty: Set correct tty name in 'active' sysfs attribute · d8a5dc30
      Hannes Reinecke 提交于
      The 'active' sysfs attribute should refer to the currently active tty
      devices the console is running on, not the currently active console.
      
      The console structure doesn't refer to any device in sysfs, only the tty
      the console is running on has.  So we need to print out the tty names in
      'active', not the console names.
      
      This resolves an issue on s390 platforms in determining the correct
      console device to use.
      
      Cc: Lennart Poettering <lennart@poettering.net>
      Cc: Kay Sievers <kay@vrfy.org>
      Cc: Jiri Slaby <jslaby@suse.cz>
      Cc: David Herrmann <dh.herrmann@gmail.com>
      Signed-off-by: NWerner Fink <werner@suse.de>
      Signed-off-by: NHannes Reinecke <hare@suse.de>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      d8a5dc30
    • L
      tty: n_gsm: Fix for modems with brk in modem status control · 3ac06b90
      Lars Poeschel 提交于
      3GPP TS 07.10 states in section 5.4.6.3.7:
      "The length byte contains the value 2 or 3 ... depending on the break
      signal." The break byte is optional and if it is sent, the length is
      3. In fact the driver was not able to work with modems that send this
      break byte in their modem status control message. If the modem just
      sends the break byte if it is really set, then weird things might
      happen.
      The code for deconding the modem status to the internal linux
      presentation in gsm_process_modem has already a big comment about
      this 2 or 3 byte length thing and it is already able to decode the
      brk, but the code calling the gsm_process_modem function in
      gsm_control_modem does not encode it and hand it over the right way.
      This patch fixes this.
      Without this fix if the modem sends the brk byte in it's modem status
      control message the driver will hang when opening a muxed channel.
      Signed-off-by: NLars Poeschel <poeschel@lemonage.de>
      Cc: stable <stable@vger.kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      3ac06b90
    • P
      drivers/tty/hvc: don't use module_init in non-modular hyp. console code · 4fedd0bf
      Paul Gortmaker 提交于
      The HVC_OPAL/RTAS/UDBG/XEN options are all bool, and hence their support
      is either present or absent.  It will never be modular, so using
      module_init as an alias for __initcall is rather misleading.
      
      Fix this up now, so that we can relocate module_init from
      init.h into module.h in the future.  If we don't do this, we'd
      have to add module.h to obviously non-modular code, and that
      would be a worse thing.
      
      Note that direct use of __initcall is discouraged, vs. one
      of the priority categorized subgroups.  As __initcall gets
      mapped onto device_initcall, our use of device_initcall
      directly in this change means that the runtime impact is
      zero -- it will remain at level 6 in initcall ordering.
      
      Also the __exitcall functions have been outright deleted since
      they are only ever of interest to UML, and UML will never be
      using any of this code.
      
      Cc: Richard Weinberger <richard@nod.at>
      Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Acked-by: NDavid Vrabel <david.vrabel@citrix.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4fedd0bf
  5. 07 2月, 2014 1 次提交
  6. 06 2月, 2014 1 次提交