ubi-media.h 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505
  1. /*
  2. * Copyright (c) International Business Machines Corp., 2006
  3. *
  4. * SPDX-License-Identifier: GPL-2.0+
  5. *
  6. * Authors: Artem Bityutskiy (Битюцкий Артём)
  7. * Thomas Gleixner
  8. * Frank Haverkamp
  9. * Oliver Lohmann
  10. * Andreas Arnez
  11. */
  12. /*
  13. * This file defines the layout of UBI headers and all the other UBI on-flash
  14. * data structures.
  15. */
  16. #ifndef __UBI_MEDIA_H__
  17. #define __UBI_MEDIA_H__
  18. #include <asm/byteorder.h>
  19. /* The version of UBI images supported by this implementation */
  20. #define UBI_VERSION 1
  21. /* The highest erase counter value supported by this implementation */
  22. #define UBI_MAX_ERASECOUNTER 0x7FFFFFFF
  23. /* The initial CRC32 value used when calculating CRC checksums */
  24. #define UBI_CRC32_INIT 0xFFFFFFFFU
  25. /* Erase counter header magic number (ASCII "UBI#") */
  26. #define UBI_EC_HDR_MAGIC 0x55424923
  27. /* Volume identifier header magic number (ASCII "UBI!") */
  28. #define UBI_VID_HDR_MAGIC 0x55424921
  29. /*
  30. * Volume type constants used in the volume identifier header.
  31. *
  32. * @UBI_VID_DYNAMIC: dynamic volume
  33. * @UBI_VID_STATIC: static volume
  34. */
  35. enum {
  36. UBI_VID_DYNAMIC = 1,
  37. UBI_VID_STATIC = 2
  38. };
  39. /*
  40. * Volume flags used in the volume table record.
  41. *
  42. * @UBI_VTBL_AUTORESIZE_FLG: auto-resize this volume
  43. *
  44. * %UBI_VTBL_AUTORESIZE_FLG flag can be set only for one volume in the volume
  45. * table. UBI automatically re-sizes the volume which has this flag and makes
  46. * the volume to be of largest possible size. This means that if after the
  47. * initialization UBI finds out that there are available physical eraseblocks
  48. * present on the device, it automatically appends all of them to the volume
  49. * (the physical eraseblocks reserved for bad eraseblocks handling and other
  50. * reserved physical eraseblocks are not taken). So, if there is a volume with
  51. * the %UBI_VTBL_AUTORESIZE_FLG flag set, the amount of available logical
  52. * eraseblocks will be zero after UBI is loaded, because all of them will be
  53. * reserved for this volume. Note, the %UBI_VTBL_AUTORESIZE_FLG bit is cleared
  54. * after the volume had been initialized.
  55. *
  56. * The auto-resize feature is useful for device production purposes. For
  57. * example, different NAND flash chips may have different amount of initial bad
  58. * eraseblocks, depending of particular chip instance. Manufacturers of NAND
  59. * chips usually guarantee that the amount of initial bad eraseblocks does not
  60. * exceed certain percent, e.g. 2%. When one creates an UBI image which will be
  61. * flashed to the end devices in production, he does not know the exact amount
  62. * of good physical eraseblocks the NAND chip on the device will have, but this
  63. * number is required to calculate the volume sized and put them to the volume
  64. * table of the UBI image. In this case, one of the volumes (e.g., the one
  65. * which will store the root file system) is marked as "auto-resizable", and
  66. * UBI will adjust its size on the first boot if needed.
  67. *
  68. * Note, first UBI reserves some amount of physical eraseblocks for bad
  69. * eraseblock handling, and then re-sizes the volume, not vice-versa. This
  70. * means that the pool of reserved physical eraseblocks will always be present.
  71. */
  72. enum {
  73. UBI_VTBL_AUTORESIZE_FLG = 0x01,
  74. };
  75. /*
  76. * Compatibility constants used by internal volumes.
  77. *
  78. * @UBI_COMPAT_DELETE: delete this internal volume before anything is written
  79. * to the flash
  80. * @UBI_COMPAT_RO: attach this device in read-only mode
  81. * @UBI_COMPAT_PRESERVE: preserve this internal volume - do not touch its
  82. * physical eraseblocks, don't allow the wear-leveling
  83. * sub-system to move them
  84. * @UBI_COMPAT_REJECT: reject this UBI image
  85. */
  86. enum {
  87. UBI_COMPAT_DELETE = 1,
  88. UBI_COMPAT_RO = 2,
  89. UBI_COMPAT_PRESERVE = 4,
  90. UBI_COMPAT_REJECT = 5
  91. };
  92. /* Sizes of UBI headers */
  93. #define UBI_EC_HDR_SIZE sizeof(struct ubi_ec_hdr)
  94. #define UBI_VID_HDR_SIZE sizeof(struct ubi_vid_hdr)
  95. /* Sizes of UBI headers without the ending CRC */
  96. #define UBI_EC_HDR_SIZE_CRC (UBI_EC_HDR_SIZE - sizeof(__be32))
  97. #define UBI_VID_HDR_SIZE_CRC (UBI_VID_HDR_SIZE - sizeof(__be32))
  98. /**
  99. * struct ubi_ec_hdr - UBI erase counter header.
  100. * @magic: erase counter header magic number (%UBI_EC_HDR_MAGIC)
  101. * @version: version of UBI implementation which is supposed to accept this
  102. * UBI image
  103. * @padding1: reserved for future, zeroes
  104. * @ec: the erase counter
  105. * @vid_hdr_offset: where the VID header starts
  106. * @data_offset: where the user data start
  107. * @image_seq: image sequence number
  108. * @padding2: reserved for future, zeroes
  109. * @hdr_crc: erase counter header CRC checksum
  110. *
  111. * The erase counter header takes 64 bytes and has a plenty of unused space for
  112. * future usage. The unused fields are zeroed. The @version field is used to
  113. * indicate the version of UBI implementation which is supposed to be able to
  114. * work with this UBI image. If @version is greater than the current UBI
  115. * version, the image is rejected. This may be useful in future if something
  116. * is changed radically. This field is duplicated in the volume identifier
  117. * header.
  118. *
  119. * The @vid_hdr_offset and @data_offset fields contain the offset of the the
  120. * volume identifier header and user data, relative to the beginning of the
  121. * physical eraseblock. These values have to be the same for all physical
  122. * eraseblocks.
  123. *
  124. * The @image_seq field is used to validate a UBI image that has been prepared
  125. * for a UBI device. The @image_seq value can be any value, but it must be the
  126. * same on all eraseblocks. UBI will ensure that all new erase counter headers
  127. * also contain this value, and will check the value when attaching the flash.
  128. * One way to make use of @image_seq is to increase its value by one every time
  129. * an image is flashed over an existing image, then, if the flashing does not
  130. * complete, UBI will detect the error when attaching the media.
  131. */
  132. struct ubi_ec_hdr {
  133. __be32 magic;
  134. __u8 version;
  135. __u8 padding1[3];
  136. __be64 ec; /* Warning: the current limit is 31-bit anyway! */
  137. __be32 vid_hdr_offset;
  138. __be32 data_offset;
  139. __be32 image_seq;
  140. __u8 padding2[32];
  141. __be32 hdr_crc;
  142. } __packed;
  143. /**
  144. * struct ubi_vid_hdr - on-flash UBI volume identifier header.
  145. * @magic: volume identifier header magic number (%UBI_VID_HDR_MAGIC)
  146. * @version: UBI implementation version which is supposed to accept this UBI
  147. * image (%UBI_VERSION)
  148. * @vol_type: volume type (%UBI_VID_DYNAMIC or %UBI_VID_STATIC)
  149. * @copy_flag: if this logical eraseblock was copied from another physical
  150. * eraseblock (for wear-leveling reasons)
  151. * @compat: compatibility of this volume (%0, %UBI_COMPAT_DELETE,
  152. * %UBI_COMPAT_IGNORE, %UBI_COMPAT_PRESERVE, or %UBI_COMPAT_REJECT)
  153. * @vol_id: ID of this volume
  154. * @lnum: logical eraseblock number
  155. * @padding1: reserved for future, zeroes
  156. * @data_size: how many bytes of data this logical eraseblock contains
  157. * @used_ebs: total number of used logical eraseblocks in this volume
  158. * @data_pad: how many bytes at the end of this physical eraseblock are not
  159. * used
  160. * @data_crc: CRC checksum of the data stored in this logical eraseblock
  161. * @padding2: reserved for future, zeroes
  162. * @sqnum: sequence number
  163. * @padding3: reserved for future, zeroes
  164. * @hdr_crc: volume identifier header CRC checksum
  165. *
  166. * The @sqnum is the value of the global sequence counter at the time when this
  167. * VID header was created. The global sequence counter is incremented each time
  168. * UBI writes a new VID header to the flash, i.e. when it maps a logical
  169. * eraseblock to a new physical eraseblock. The global sequence counter is an
  170. * unsigned 64-bit integer and we assume it never overflows. The @sqnum
  171. * (sequence number) is used to distinguish between older and newer versions of
  172. * logical eraseblocks.
  173. *
  174. * There are 2 situations when there may be more than one physical eraseblock
  175. * corresponding to the same logical eraseblock, i.e., having the same @vol_id
  176. * and @lnum values in the volume identifier header. Suppose we have a logical
  177. * eraseblock L and it is mapped to the physical eraseblock P.
  178. *
  179. * 1. Because UBI may erase physical eraseblocks asynchronously, the following
  180. * situation is possible: L is asynchronously erased, so P is scheduled for
  181. * erasure, then L is written to,i.e. mapped to another physical eraseblock P1,
  182. * so P1 is written to, then an unclean reboot happens. Result - there are 2
  183. * physical eraseblocks P and P1 corresponding to the same logical eraseblock
  184. * L. But P1 has greater sequence number, so UBI picks P1 when it attaches the
  185. * flash.
  186. *
  187. * 2. From time to time UBI moves logical eraseblocks to other physical
  188. * eraseblocks for wear-leveling reasons. If, for example, UBI moves L from P
  189. * to P1, and an unclean reboot happens before P is physically erased, there
  190. * are two physical eraseblocks P and P1 corresponding to L and UBI has to
  191. * select one of them when the flash is attached. The @sqnum field says which
  192. * PEB is the original (obviously P will have lower @sqnum) and the copy. But
  193. * it is not enough to select the physical eraseblock with the higher sequence
  194. * number, because the unclean reboot could have happen in the middle of the
  195. * copying process, so the data in P is corrupted. It is also not enough to
  196. * just select the physical eraseblock with lower sequence number, because the
  197. * data there may be old (consider a case if more data was added to P1 after
  198. * the copying). Moreover, the unclean reboot may happen when the erasure of P
  199. * was just started, so it result in unstable P, which is "mostly" OK, but
  200. * still has unstable bits.
  201. *
  202. * UBI uses the @copy_flag field to indicate that this logical eraseblock is a
  203. * copy. UBI also calculates data CRC when the data is moved and stores it at
  204. * the @data_crc field of the copy (P1). So when UBI needs to pick one physical
  205. * eraseblock of two (P or P1), the @copy_flag of the newer one (P1) is
  206. * examined. If it is cleared, the situation* is simple and the newer one is
  207. * picked. If it is set, the data CRC of the copy (P1) is examined. If the CRC
  208. * checksum is correct, this physical eraseblock is selected (P1). Otherwise
  209. * the older one (P) is selected.
  210. *
  211. * There are 2 sorts of volumes in UBI: user volumes and internal volumes.
  212. * Internal volumes are not seen from outside and are used for various internal
  213. * UBI purposes. In this implementation there is only one internal volume - the
  214. * layout volume. Internal volumes are the main mechanism of UBI extensions.
  215. * For example, in future one may introduce a journal internal volume. Internal
  216. * volumes have their own reserved range of IDs.
  217. *
  218. * The @compat field is only used for internal volumes and contains the "degree
  219. * of their compatibility". It is always zero for user volumes. This field
  220. * provides a mechanism to introduce UBI extensions and to be still compatible
  221. * with older UBI binaries. For example, if someone introduced a journal in
  222. * future, he would probably use %UBI_COMPAT_DELETE compatibility for the
  223. * journal volume. And in this case, older UBI binaries, which know nothing
  224. * about the journal volume, would just delete this volume and work perfectly
  225. * fine. This is similar to what Ext2fs does when it is fed by an Ext3fs image
  226. * - it just ignores the Ext3fs journal.
  227. *
  228. * The @data_crc field contains the CRC checksum of the contents of the logical
  229. * eraseblock if this is a static volume. In case of dynamic volumes, it does
  230. * not contain the CRC checksum as a rule. The only exception is when the
  231. * data of the physical eraseblock was moved by the wear-leveling sub-system,
  232. * then the wear-leveling sub-system calculates the data CRC and stores it in
  233. * the @data_crc field. And of course, the @copy_flag is %in this case.
  234. *
  235. * The @data_size field is used only for static volumes because UBI has to know
  236. * how many bytes of data are stored in this eraseblock. For dynamic volumes,
  237. * this field usually contains zero. The only exception is when the data of the
  238. * physical eraseblock was moved to another physical eraseblock for
  239. * wear-leveling reasons. In this case, UBI calculates CRC checksum of the
  240. * contents and uses both @data_crc and @data_size fields. In this case, the
  241. * @data_size field contains data size.
  242. *
  243. * The @used_ebs field is used only for static volumes and indicates how many
  244. * eraseblocks the data of the volume takes. For dynamic volumes this field is
  245. * not used and always contains zero.
  246. *
  247. * The @data_pad is calculated when volumes are created using the alignment
  248. * parameter. So, effectively, the @data_pad field reduces the size of logical
  249. * eraseblocks of this volume. This is very handy when one uses block-oriented
  250. * software (say, cramfs) on top of the UBI volume.
  251. */
  252. struct ubi_vid_hdr {
  253. __be32 magic;
  254. __u8 version;
  255. __u8 vol_type;
  256. __u8 copy_flag;
  257. __u8 compat;
  258. __be32 vol_id;
  259. __be32 lnum;
  260. __u8 padding1[4];
  261. __be32 data_size;
  262. __be32 used_ebs;
  263. __be32 data_pad;
  264. __be32 data_crc;
  265. __u8 padding2[4];
  266. __be64 sqnum;
  267. __u8 padding3[12];
  268. __be32 hdr_crc;
  269. } __packed;
  270. /* Internal UBI volumes count */
  271. #define UBI_INT_VOL_COUNT 1
  272. /*
  273. * Starting ID of internal volumes: 0x7fffefff.
  274. * There is reserved room for 4096 internal volumes.
  275. */
  276. #define UBI_INTERNAL_VOL_START (0x7FFFFFFF - 4096)
  277. /* The layout volume contains the volume table */
  278. #define UBI_LAYOUT_VOLUME_ID UBI_INTERNAL_VOL_START
  279. #define UBI_LAYOUT_VOLUME_TYPE UBI_VID_DYNAMIC
  280. #define UBI_LAYOUT_VOLUME_ALIGN 1
  281. #define UBI_LAYOUT_VOLUME_EBS 2
  282. #define UBI_LAYOUT_VOLUME_NAME "layout volume"
  283. #define UBI_LAYOUT_VOLUME_COMPAT UBI_COMPAT_REJECT
  284. /* The maximum number of volumes per one UBI device */
  285. #define UBI_MAX_VOLUMES 128
  286. /* The maximum volume name length */
  287. #define UBI_VOL_NAME_MAX 127
  288. /* Size of the volume table record */
  289. #define UBI_VTBL_RECORD_SIZE sizeof(struct ubi_vtbl_record)
  290. /* Size of the volume table record without the ending CRC */
  291. #define UBI_VTBL_RECORD_SIZE_CRC (UBI_VTBL_RECORD_SIZE - sizeof(__be32))
  292. /**
  293. * struct ubi_vtbl_record - a record in the volume table.
  294. * @reserved_pebs: how many physical eraseblocks are reserved for this volume
  295. * @alignment: volume alignment
  296. * @data_pad: how many bytes are unused at the end of the each physical
  297. * eraseblock to satisfy the requested alignment
  298. * @vol_type: volume type (%UBI_DYNAMIC_VOLUME or %UBI_STATIC_VOLUME)
  299. * @upd_marker: if volume update was started but not finished
  300. * @name_len: volume name length
  301. * @name: the volume name
  302. * @flags: volume flags (%UBI_VTBL_AUTORESIZE_FLG)
  303. * @padding: reserved, zeroes
  304. * @crc: a CRC32 checksum of the record
  305. *
  306. * The volume table records are stored in the volume table, which is stored in
  307. * the layout volume. The layout volume consists of 2 logical eraseblock, each
  308. * of which contains a copy of the volume table (i.e., the volume table is
  309. * duplicated). The volume table is an array of &struct ubi_vtbl_record
  310. * objects indexed by the volume ID.
  311. *
  312. * If the size of the logical eraseblock is large enough to fit
  313. * %UBI_MAX_VOLUMES records, the volume table contains %UBI_MAX_VOLUMES
  314. * records. Otherwise, it contains as many records as it can fit (i.e., size of
  315. * logical eraseblock divided by sizeof(struct ubi_vtbl_record)).
  316. *
  317. * The @upd_marker flag is used to implement volume update. It is set to %1
  318. * before update and set to %0 after the update. So if the update operation was
  319. * interrupted, UBI knows that the volume is corrupted.
  320. *
  321. * The @alignment field is specified when the volume is created and cannot be
  322. * later changed. It may be useful, for example, when a block-oriented file
  323. * system works on top of UBI. The @data_pad field is calculated using the
  324. * logical eraseblock size and @alignment. The alignment must be multiple to the
  325. * minimal flash I/O unit. If @alignment is 1, all the available space of
  326. * the physical eraseblocks is used.
  327. *
  328. * Empty records contain all zeroes and the CRC checksum of those zeroes.
  329. */
  330. struct ubi_vtbl_record {
  331. __be32 reserved_pebs;
  332. __be32 alignment;
  333. __be32 data_pad;
  334. __u8 vol_type;
  335. __u8 upd_marker;
  336. __be16 name_len;
  337. #ifndef __UBOOT__
  338. __u8 name[UBI_VOL_NAME_MAX+1];
  339. #else
  340. char name[UBI_VOL_NAME_MAX+1];
  341. #endif
  342. __u8 flags;
  343. __u8 padding[23];
  344. __be32 crc;
  345. } __packed;
  346. /* UBI fastmap on-flash data structures */
  347. #define UBI_FM_SB_VOLUME_ID (UBI_LAYOUT_VOLUME_ID + 1)
  348. #define UBI_FM_DATA_VOLUME_ID (UBI_LAYOUT_VOLUME_ID + 2)
  349. /* fastmap on-flash data structure format version */
  350. #define UBI_FM_FMT_VERSION 1
  351. #define UBI_FM_SB_MAGIC 0x7B11D69F
  352. #define UBI_FM_HDR_MAGIC 0xD4B82EF7
  353. #define UBI_FM_VHDR_MAGIC 0xFA370ED1
  354. #define UBI_FM_POOL_MAGIC 0x67AF4D08
  355. #define UBI_FM_EBA_MAGIC 0xf0c040a8
  356. /* A fastmap supber block can be located between PEB 0 and
  357. * UBI_FM_MAX_START */
  358. #define UBI_FM_MAX_START 64
  359. /* A fastmap can use up to UBI_FM_MAX_BLOCKS PEBs */
  360. #define UBI_FM_MAX_BLOCKS 32
  361. /* 5% of the total number of PEBs have to be scanned while attaching
  362. * from a fastmap.
  363. * But the size of this pool is limited to be between UBI_FM_MIN_POOL_SIZE and
  364. * UBI_FM_MAX_POOL_SIZE */
  365. #define UBI_FM_MIN_POOL_SIZE 8
  366. #define UBI_FM_MAX_POOL_SIZE 256
  367. /**
  368. * struct ubi_fm_sb - UBI fastmap super block
  369. * @magic: fastmap super block magic number (%UBI_FM_SB_MAGIC)
  370. * @version: format version of this fastmap
  371. * @data_crc: CRC over the fastmap data
  372. * @used_blocks: number of PEBs used by this fastmap
  373. * @block_loc: an array containing the location of all PEBs of the fastmap
  374. * @block_ec: the erase counter of each used PEB
  375. * @sqnum: highest sequence number value at the time while taking the fastmap
  376. *
  377. */
  378. struct ubi_fm_sb {
  379. __be32 magic;
  380. __u8 version;
  381. __u8 padding1[3];
  382. __be32 data_crc;
  383. __be32 used_blocks;
  384. __be32 block_loc[UBI_FM_MAX_BLOCKS];
  385. __be32 block_ec[UBI_FM_MAX_BLOCKS];
  386. __be64 sqnum;
  387. __u8 padding2[32];
  388. } __packed;
  389. /**
  390. * struct ubi_fm_hdr - header of the fastmap data set
  391. * @magic: fastmap header magic number (%UBI_FM_HDR_MAGIC)
  392. * @free_peb_count: number of free PEBs known by this fastmap
  393. * @used_peb_count: number of used PEBs known by this fastmap
  394. * @scrub_peb_count: number of to be scrubbed PEBs known by this fastmap
  395. * @bad_peb_count: number of bad PEBs known by this fastmap
  396. * @erase_peb_count: number of bad PEBs which have to be erased
  397. * @vol_count: number of UBI volumes known by this fastmap
  398. */
  399. struct ubi_fm_hdr {
  400. __be32 magic;
  401. __be32 free_peb_count;
  402. __be32 used_peb_count;
  403. __be32 scrub_peb_count;
  404. __be32 bad_peb_count;
  405. __be32 erase_peb_count;
  406. __be32 vol_count;
  407. __u8 padding[4];
  408. } __packed;
  409. /* struct ubi_fm_hdr is followed by two struct ubi_fm_scan_pool */
  410. /**
  411. * struct ubi_fm_scan_pool - Fastmap pool PEBs to be scanned while attaching
  412. * @magic: pool magic numer (%UBI_FM_POOL_MAGIC)
  413. * @size: current pool size
  414. * @max_size: maximal pool size
  415. * @pebs: an array containing the location of all PEBs in this pool
  416. */
  417. struct ubi_fm_scan_pool {
  418. __be32 magic;
  419. __be16 size;
  420. __be16 max_size;
  421. __be32 pebs[UBI_FM_MAX_POOL_SIZE];
  422. __be32 padding[4];
  423. } __packed;
  424. /* ubi_fm_scan_pool is followed by nfree+nused struct ubi_fm_ec records */
  425. /**
  426. * struct ubi_fm_ec - stores the erase counter of a PEB
  427. * @pnum: PEB number
  428. * @ec: ec of this PEB
  429. */
  430. struct ubi_fm_ec {
  431. __be32 pnum;
  432. __be32 ec;
  433. } __packed;
  434. /**
  435. * struct ubi_fm_volhdr - Fastmap volume header
  436. * it identifies the start of an eba table
  437. * @magic: Fastmap volume header magic number (%UBI_FM_VHDR_MAGIC)
  438. * @vol_id: volume id of the fastmapped volume
  439. * @vol_type: type of the fastmapped volume
  440. * @data_pad: data_pad value of the fastmapped volume
  441. * @used_ebs: number of used LEBs within this volume
  442. * @last_eb_bytes: number of bytes used in the last LEB
  443. */
  444. struct ubi_fm_volhdr {
  445. __be32 magic;
  446. __be32 vol_id;
  447. __u8 vol_type;
  448. __u8 padding1[3];
  449. __be32 data_pad;
  450. __be32 used_ebs;
  451. __be32 last_eb_bytes;
  452. __u8 padding2[8];
  453. } __packed;
  454. /* struct ubi_fm_volhdr is followed by one struct ubi_fm_eba records */
  455. /**
  456. * struct ubi_fm_eba - denotes an association beween a PEB and LEB
  457. * @magic: EBA table magic number
  458. * @reserved_pebs: number of table entries
  459. * @pnum: PEB number of LEB (LEB is the index)
  460. */
  461. struct ubi_fm_eba {
  462. __be32 magic;
  463. __be32 reserved_pebs;
  464. __be32 pnum[0];
  465. } __packed;
  466. #endif /* !__UBI_MEDIA_H__ */