Databases
StackOverflow2013
Postsdbo
POShould a bad USB device be able to crash a bug free Linux kernel?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POShould a bad USB device be able to crash a bug free Linux kernel?
    primarykey
    data
    text
    <p>My question is rather broad, I know, but I have been wondering about this for a long time.</p> <p>A little background. I work in a Physics lab where all the lab computers are running Debian (mix of old version and Lenny) or more recently Ubuntu 10.4 LTS. We have written a lot of custom software to interface with experiment hardware and other computers.</p> <p>We have a lot of FPGA boards that are controlling various parts of the experiment, these are connected via USB to different computers. After upgrading a computer controlling an experiment we started seeing crashes/lockups of the computer running all the lasers. This used to be completely stable.</p> <p>My question is this: If the entire computer locks up because of an issue with a) Python/GTK software gui b) USB device driver or c) The actual device can this be blamed on the Linux kernel (or other levels of the OS)?</p> <p>Is it unfair to ask of the linux kernel not to panic even if I make mistakes in my implementation of software/hardware.</p> <p>My own guess: Any user level applications should never be able to crash the entire system since they should only have access to their own stuff.</p> <p>Any device driver becomes a part of the kernel itself and will therefore be able to crash it. Is my reasoning sound?</p> <p>Bonus question: IS there a way to insulate device and kernel somehow such that Linux will keep running happily no matter what stupid mistakes are made with the hardware. That would be very useful for two reasons: 1) debugging is easier with a running system, 2) For the purposes of the experiment we really need long uptimes and having only a part of the system crash is infinitely better than crashes in one part of the system propagating to the rest.</p> <p>Any links and reading material on this subject would be appreciated. Thank you.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKara
    1. USHansHarhoff
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POShould a bad USB device be able to crash a bug free Linux kernel?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POShould a bad USB device be able to crash a bug free Linux kernel?
      1. USHansHarhoff
      1. VTFavorite
    3. VO
      singulars
      1. POShould a bad USB device be able to crash a bug free Linux kernel?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm no expert in crashes, but I'd say that you are right in your guesses. About the bonus question, _logical_ errors (ie. bad protocol) should be coped by the kernel with no further problems; but _phisical_ errors (ie. shortcircuit, overcurrent, etc.) cannot be, in general, be managed by the kernel, and will provoke different levels of disaster.
      singulars
      1. POShould a bad USB device be able to crash a bug free Linux kernel?
      1. USrodrigo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload